The seven quality-management principles are customer focus, leadership, engagement of people, the process approach, improvement, evidence-based decision making and relationship management. They provide a foundation for quality management, rather than seven separate certificates or a substitute for ISO 9001 requirements.
Use them as prompts for a practical review. Choose one delivery process, ask where the principles appear in its decisions and identify a change worth testing. The examples below are hypothetical and illustrate working methods, not additional mandatory clauses.
1. Customer focus: define what a useful outcome means
Capture what the customer needs in a form that delivery teams can use. A promise such as fast service is ambiguous until the parties understand the response, completion and acceptance expectations. Check whether internal measures reflect that outcome or simply count activity.
Hypothetical example: a laboratory reports that samples are processed quickly, yet customers complain about unusable reports. It examines completeness and clarity as well as turnaround. The improvement question shifts from producing more reports to delivering results that customers can use.
Use complaints, repeat requests and direct feedback to test your assumptions. Record the action taken and check the effect. A survey score without a response process provides information but does not close the feedback loop.
2. Leadership: make priorities and trade-offs visible
Leaders influence quality through the decisions they fund, the exceptions they accept and the behaviour they reward. A quality policy has limited value if operating targets consistently encourage staff to ignore acceptance checks or hide unsuitable outputs.
Make priorities clear when delivery, cost and quality conflict. Decide who can approve an exception and what evidence is needed. Give process owners the authority and resources to resolve recurring issues, rather than making them responsible for results they cannot influence.
Management discussion should produce decisions and follow-up. Review whether promised resources arrived and whether a previously escalated issue remains open. Attendance at a meeting is easier to demonstrate than effective leadership, but it is not the same thing.
3. Engagement of people: use the knowledge closest to the work
Ask the people performing the process where instructions are unclear, where information arrives late and which workarounds have become routine. They often see a mismatch before a dashboard makes it visible.
Provide the knowledge, tools and feedback needed for the role. A course attendance record can show participation, but a practical check may be needed to understand whether someone can perform a critical task. Choose that check to fit the work rather than applying one assessment format to every role.
Create a route for raising concerns without making every report an admission of personal failure. Then respond to the concern. A suggestion process that never explains what happened to submissions can discourage the participation it was designed to encourage.
4. Process approach: inspect the handovers
Describe how inputs become an accepted output and how each activity depends on others. Identify the owner, relevant information, resources and decisions. Department names alone rarely reveal where delivery can fail.
Hypothetical example: a repair business receives technically correct work orders that omit the customer’s agreed return date. Planning and service teams jointly change the intake record and test the handover. The improvement comes from the interaction between processes, not from asking each department to work harder in isolation.
Check what happens when an input is incomplete or a condition changes. A process map should help staff decide what to do, including when to stop and escalate; it should not merely illustrate the ideal path.
5. Improvement: test whether the change solved the problem
Distinguish correcting an immediate output from changing the process that produced it. Replacing one incorrect item may satisfy the affected customer while leaving the cause available to create the next failure.
Define the problem with evidence, examine plausible causes and select a change. Decide beforehand how you will check the result and identify unintended effects. A shorter cycle time may be unhelpful if it increases rework or transfers a burden to another team.
Keep successful changes usable. Update the relevant instruction, system or learning material and explain the reason. Improvement is easier to sustain when the revised method is part of normal work rather than an extra task dependent on one enthusiastic individual.
6. Evidence-based decisions: understand what a measure can tell you
Choose measures that answer a decision question. Define the data source, population, calculation and limitations. If teams count the same event differently, an impressive comparison may conceal inconsistent data.
Look at context and trends, and investigate exceptions. A low complaint count may mean that customers are satisfied, or that the reporting route is difficult to use. Combine appropriate quantitative evidence with observation and informed judgement.
Record assumptions when evidence is incomplete. Decide what additional information would change the conclusion and whether obtaining it is proportionate. Evidence-based decision making does not mean waiting indefinitely for perfect data; it means being honest about the basis and limits of the decision.
7. Relationship management: clarify shared expectations
Identify the relationships that affect delivery, including suppliers and outsourced processes. Agree responsibilities, acceptance criteria, communication routes and how changes will be handled. A low purchase price is not the complete measure of a relationship’s value.
Discuss recurring issues with evidence about their effect on the process. A supplier may meet its stated lead time while delivering information too late for your planning needs. Clarifying the interface can be more useful than repeatedly escalating the same complaint.
Use the principles together in a scoped quality-management review. Customer needs, leadership decisions, capable people and dependable relationships should connect to the process and its results.
Reference basis
- ISO, Quality management principles: The foundation for success.
- ISO, Quality management principles public booklet.
- ISO 9001:2026 public overview.
Questions and answers
Are the seven principles a complete ISO 9001 checklist?
No. They are a foundation for quality management. An organisation seeking conformity or certification must assess the applicable ISO 9001 requirements and its actual system.
Which principle should a small business start with?
Choose a real delivery problem and use the relevant principles together. An unclear customer requirement may also reveal a leadership decision, a process handover and a supplier relationship that need attention.
Does evidence-based decision making require expensive analytics software?
No particular software is prescribed by the principle. Start with a clear question, reliable records and an appropriate method. More data does not necessarily produce a better decision.
How can we tell whether people are engaged in quality work?
Look for informed participation, concerns being raised and acted on, and staff able to explain the purpose of relevant checks. Attendance at a presentation alone is a limited measure.
Do these principles guarantee a fixed improvement in revenue or cost?
No. Define outcomes and measure changes in your own organisation. Avoid attributing every improvement to a principle or certificate without examining other contributing factors.
Choose one process and make quality easier to demonstrate
Bring a recurring delivery problem and the evidence currently available. Discuss a practical quality-management review focused on useful decisions and measurable improvements.