The Process Approach to Quality Management

# Why the process matters Most people imagine quality management as checklists and a team catching mistakes at the end. That approach misses the bigger point: quality is produced by how work travels through an organization. When steps, ownership, and expectations are misaligned, customers feel the consequence downstream.

# The real unit of management: the handoff Quality problems often live in the space between teams. Departments can optimize local targets while creating gaps across the flow. Examples: purchasing hitting cost targets but choosing unreliable vendors, marketing promising delivery times without checking capacity, or support collecting complaints without closing the loop to operations. Managing performance as connected work, not isolated tasks, aligns actions with the single continuous journey the customer experiences.

# What to map: inputs and outputs On paper, processes look simple: inputs go in, work happens, outputs come out. In reality, inputs include customer information, deadlines, design requirements, supplier commitments, and employee skill. Outputs can be approvals, decisions, product deliverables, or handoffs to other teams. Honest process mapping surfaces repeated issues: assumed requirements, shared but unclear ownership, reliance on memory, and metrics that track activity instead of quality.

# Measures that follow the flow Collecting lots of data is common, but the wrong metrics hide causes. A process approach asks different questions: How long does work wait between steps? Where are errors introduced? Which inputs most often cause rework? Which stage shows the largest variation? Metrics tied to these questions point to causes and guide targeted fixes instead of generating more reports.

# Consistency beats heroics Workplaces often reward last-minute fixes and heroic recovery. Those rescues can hide weak processes. The goal should be to design work so ordinary people on ordinary days produce dependable results. Consistent processes make training easier, reduce surprises, scale operations, and limit regulatory risk where procedures and control matter for safety and compliance.

# Where standard models fit

# Practical starting points Begin with a clear, honest map of a small but important workflow. Identify each input, the explicit owner of each step, and the expected output. Track waiting time and error sources between steps. Replace assumptions with documented requirements and standard methods. When the workflow is visible, capacity constraints, variation, and recurring causes become easier to address.

# The managerial shift