What are the seven quality management principles?
The seven quality management principles are customer focus, leadership, engagement of people, process approach, improvement, evidence-based decision making and relationship management. Together they offer a way to reason about reliable work: understand the result people need, organise the work that delivers it, and learn when reality differs from expectations.
ISO identifies these principles as the conceptual foundation of its quality management family. They are useful even when an organisation does not seek certification. They are not seven additional clauses to audit independently, a prescribed management method, or a guarantee that a business will succeed. ISO 9001 contains requirements for a quality management system. A principle helps explain a managerial purpose; the applicable requirement provides the criterion for conformity.
This guide uses original practical explanations and hypothetical examples. Its checklists are suggested ways to think and work, rather than instructions copied from a standard. ISO’s public overview identifies ISO 9001:2026 as the current edition, published on 16 September 2026. For a certification decision, use the applicable standard and agreed audit criteria alongside this conceptual guidance.
Customer focus: begin with the outcome someone needs
Customer focus means keeping the customer’s intended use and requirements visible when making decisions. An organisation can complete its internal tasks perfectly and still deliver something the customer cannot use. An accurate report arriving after a decision deadline illustrates that gap.
Start by separating what a customer explicitly ordered from what needs clarification. Who will use the output? Under what conditions? Which characteristics determine acceptance? A purchasing contact, an operator and a recipient of the final service may describe different needs. Resolve these differences before a promise becomes a delivery obligation.
A hypothetical equipment supplier might discover that customers care more about predictable installation dates than about rapid shipment from the factory. Optimising dispatch speed alone could therefore create a misleading picture of success. The supplier would need to understand the installation handover as well.
Customer focus in quality management examines how to translate this thinking into decisions, including how to handle customer requests that conflict with safety, capability or agreed scope.
Leadership: make priorities credible through decisions
Leadership gives the organisation a direction for quality and creates the conditions in which people can pursue it. People learn what matters from resource allocation, responses to bad news and the treatment of competing priorities. A slogan about quality cannot resolve a production schedule that allows no time for necessary checks.
Consider a hypothetical manager deciding whether to release an order with an unresolved acceptance concern. Leadership involves making the decision consistent with the organisation’s commitments, providing a route to resolve the concern, and explaining why the deadline cannot erase the issue. The decision shapes future behaviour more strongly than a poster.
Leadership can be exercised at different levels, although this does not remove the responsibilities assigned to top management by applicable requirements. Team leaders can clarify daily priorities; senior leaders must address conflicts that teams cannot resolve with their own authority.
A useful test is whether employees can describe what happens when output, cost and quality objectives collide. If the answer depends on which manager is present, the organisation has an alignment problem.
Engagement of people: enable informed contribution
Engagement involves people understanding their contribution, having suitable capability, and being able to influence work within clear boundaries. Attendance at training or an improvement meeting is only a small part of the picture. Someone can attend every session yet remain unable to question an ambiguous instruction.
Ask what employees need in order to do good work. They may require practical instruction, accessible information, functioning equipment, time to discuss exceptions or authority to stop a questionable handover. An invitation to contribute has little value when nobody responds to what is raised.
In a hypothetical contact centre, experienced staff may know why callers repeatedly contact the organisation. Involving them in redesigning the information sent to customers can reveal a problem that average call time conceals. Test the proposed change with newer staff too, because an expert’s workaround may depend on knowledge others do not have.
People engagement should not become a way to assign system failures to employee attitude. Look first at the conditions surrounding performance. Motivation cannot compensate indefinitely for conflicting instructions or missing resources.
Process approach: understand connections between activities
The process approach treats work as connected activities that transform inputs into outputs. The important question is how the whole route produces the intended result. A departmental view alone can hide delays, rework and uncertainty at the boundaries between teams.
For a hypothetical repair business, the route might include receiving a request, diagnosing the fault, approving the estimate, obtaining parts, repairing the item and returning it. Each step depends on information or material from another step. A diagnosis with no clear parts specification can disrupt purchasing even if the technician’s local task appears complete.
A useful process description explains the starting point, intended result, responsibility, necessary resources, decision criteria and interfaces. It need not be an elaborate diagram. Choose a format that helps people operate and improve the work.
The companion guide to the process approach in quality management explains how to identify meaningful boundaries and avoid improving one activity at the expense of another.
Improvement: change performance deliberately
Improvement means increasing the organisation’s ability to achieve useful results. It can involve preventing recurrence of a problem, simplifying work, strengthening a control or developing a better service. Completing an action is different from demonstrating that performance improved.
Define the problem or opportunity before choosing a solution. Describe the current condition, the outcome sought, what evidence would show progress, and what other outcomes must remain acceptable. A trial is often useful where uncertainty is significant, but no particular improvement tool follows automatically from the principle.
A hypothetical warehouse changes its picking layout to reduce errors. A shorter walking distance is encouraging, but the intended quality result is fewer wrong items reaching customers. Check both accuracy and unintended consequences, such as congestion or damaged packaging.
Improvement as a quality management principle provides a practical decision sequence for choosing changes and reviewing whether they worked. Improvement should become a learning habit rather than a queue of projects that never reach an effectiveness review.
Evidence-based decision making: make uncertainty visible
Evidence-based decisions use relevant information, evaluate its reliability and distinguish observation from interpretation. Evidence can include measured results, records, direct observation and informed qualitative feedback. A number is not automatically reliable because it appears on a dashboard.
Before comparing results, check definitions, coverage, timing and collection methods. A falling complaint count might reflect better service, fewer customers, a difficult reporting channel or incomplete records. The same number can support several explanations until other evidence narrows them.
A hypothetical distributor sees more damaged deliveries. Comparing packaging batches, handling routes, photographs and delivery volumes may provide a better basis for action than blaming the carrier after one vivid incident. Expert judgement remains useful, particularly when evidence is incomplete, but its assumptions should be explicit.
The guide to evidence-based decision making explains how to assess data quality and make proportionate decisions without waiting for impossible certainty.
Relationship management: govern important dependencies
Relationship management recognises that quality depends partly on other parties. Suppliers, service partners and other relevant relationships can affect availability, information, continuity and the customer’s experience. Treating every supplier identically can waste attention on low consequence purchases while overlooking a fragile critical dependency.
Identify which relationships matter to intended results and why. Consider the effect of failure, substitutability, technical dependence and the time needed to recover. Then agree communication, expectations and review arrangements proportionate to those conditions.
A hypothetical laboratory relying on an external courier may need a clear response to delayed collection because sample condition changes over time. A price negotiation alone cannot establish reliable service. Equally, a friendly relationship does not replace checking actual performance.
Relationship management in quality management examines this balance between cooperation and accountable oversight, including how to respond when a partner’s repeated failures threaten delivery.
How the principles work together
The principles reinforce one another. A customer need supplies direction, leadership makes it a real priority, people contribute practical knowledge, processes turn intentions into work, evidence reveals what happened, improvement changes capability, and relationships support the wider delivery chain.
| Decision | Questions from more than one principle |
|---|---|
| Accept a shorter delivery promise | Does the customer need it, can the process achieve it, and can partners support it? |
| Automate an inspection | What failure matters, what evidence supports the method, and can people manage exceptions? |
| Select a new supplier | What capability is needed, how will performance be checked, and what is the recovery route? |
| Close an improvement | Did the result improve, do employees understand the new method, and is the gain sustainable? |
These questions help avoid isolated initiatives. For example, improving employee participation without dealing with unresponsive management can create disappointment. Measuring more indicators without clarifying customer outcomes can produce activity without direction.
A practical starting review
Choose one important delivery route rather than launching seven separate programmes. Follow a recent real order, case or request from agreement to final use. Speak with the people who perform the work and inspect a small but purposeful sample of records. Ask where a customer promise becomes an operational instruction and where uncertainty accumulates.
Use the following prompts to identify a manageable first action:
- Can we describe the customer’s needed outcome and acceptance conditions?
- Are priorities and escalation decisions consistent across teams?
- Can people raise concerns and obtain a useful response?
- Are handovers clear enough for the next person to act?
- Do our measures represent the result and reveal important variation?
- Do we review whether changes work after implementation?
- Do important partners understand the dependencies we place on them?
Select an issue with a meaningful consequence, an owner able to influence it and evidence that can support a review. Record a baseline before changing the work. Agree who can authorise the change, when to inspect its effects and what would justify stopping or revising it.
Using principles without inventing requirements
A business may use process maps, customer interviews, supplier reviews or experiments to express these principles. The right method depends on its work and applicable obligations. The existence of a useful method does not make that method mandatory under ISO 9001.
When assessing conformity, connect a concern to an actual requirement and evidence. When developing the business, use the principles to ask broader questions about effectiveness and future capability. Keeping these purposes clear allows the principles to support sound judgement without turning every preferred practice into an audit finding.