4 Quality Management
Learn how quality management connects planning, process control, and evidence-based improvement to consistently meet customer and other requirements.
and its activities
Quality means consistently meeting relevant customer and other requirements, not merely producing an item that passes final inspection. coordinates goal setting, design and control, checking results, and improvement. A connects these activities across an organization, from understanding requirements to delivering a product or service and responding to feedback.
Three related activities contribute to this work:
: Determine the requirements, objectives, processes, and resources needed to achieve quality.
: Build confidence that processes are designed and followed effectively. Training staff and standardizing a procedure can help prevent errors.
: Measure or inspect outputs to determine whether they meet requirements. For example, a sample of finished items can be checked for defects.
Inspection can detect defects, but it cannot by itself prevent them. Strong also addresses the processes that produce results and uses evidence to improve them.
control and variation
A transforms inputs—such as materials, information, and labor—into outputs for a customer. control means defining how work should be done, monitoring important results, and responding when performance changes. Organizations may track measures such as defect rate, service time, rework, or customer complaints.
Results naturally vary. comes from the ordinary operation of a , while signals an unusual change, such as a damaged tool, a software fault, or a sudden change in materials. uses data collected over time to help distinguish these patterns.
A plots a measure over time using a center line and upper and lower calculated from behavior. A point outside those limits, or a nonrandom pattern within them, can signal that the needs investigation. describe behavior; define acceptable results for a product or service, so the two are not the same.
For example, a café can track the time from order placement to pickup. If times rise steadily after a new ordering system is introduced, managers investigate the workflow and system rather than assuming each slow order is an isolated employee error. They check the cause, make a targeted adjustment, and continue monitoring the measure.
in practice
is the ongoing effort to make products, services, and processes more effective. Changes may be small and frequent or larger and transformative. The provides a practical structure:
Plan: Define the problem, examine evidence and likely causes, and choose a change and a measure of success.
Do: Test the change, preferably on a limited scale.
Check: Compare results with the baseline and the intended outcome.
Act: Adopt the change if it works, revise it if it does not, and repeat the cycle.
For example, if a clinic finds that patients often wait because forms are incomplete, it can test a pre-visit reminder, measure completion rates and waiting times, and adjust the based on the results. A useful improvement targets the underlying , not just the visible symptom.
Effective improvement depends on clear responsibilities, employee involvement, relevant measures, and evidence-based decisions. A view also highlights how one department’s work affects another, helping prevent a local fix from creating problems elsewhere.
How the parts work together
plans for quality, assures that processes are capable of meeting requirements, controls outputs, and improves the system over time. control uses consistent methods and data to detect meaningful variation. applies evidence-based changes, often through PDCA, and checks whether those changes actually produce better results.