Apply the principles to a real decision or delivery route
The most useful way to apply the seven quality management principles is to examine an important piece of work and use the principles together. Choose a delivery route, recurring problem or consequential decision. Establish what outcome matters, how the work functions and what change would make a practical difference.
The seven quality management principles provide the conceptual questions. The sequence below is a suggested implementation method, not a prescribed ISO 9001 procedure. Adapt it to your organisation’s size, work and existing management arrangements.
Step 1: choose a bounded starting point
Select something important enough to justify attention and narrow enough to understand. From accepted service request to confirmed resolution is more workable than improve the whole business. State why the route matters: customer impact, recurring rework, uncertainty or a relevant opportunity.
Identify an owner with enough authority to coordinate across the affected activities. Include people who perform the work and people who receive its output. A team containing only managers may overlook practical exceptions and informal workarounds.
Agree what the first review will produce. A useful output could be a verified process description, a clearly defined problem and one improvement proposal. Avoid promising immediate business-wide transformation before understanding the work.
Step 2: clarify the needed outcome
Use customer focus to determine what acceptable delivery means. Review actual agreements, recent cases and feedback. Identify unresolved assumptions about intended use, timing, accuracy or communication.
Separate an agreed requirement from a preference and from an internal habit. For example, a customer may need an answer by a decision deadline, while the organisation habitually produces a lengthy report. The deadline and usable answer may matter more than the familiar format.
Record any limits on the promise, including capability and applicable obligations. A strong customer focus leads to credible commitments, not unconditional acceptance of every request.
Step 3: follow the work and its dependencies
Walk through recent representative cases. Identify the trigger, important activities, decision points and handovers. Ask what each receiving person needs to act correctly and what happens when information is missing.
Use leadership and engagement questions during this review. Are priorities consistent? Can people pause and escalate uncertain work? Do they have the capability and resources their responsibilities require?
Include external dependencies. A service partner or specialist supplier may determine whether the organisation can meet its promise. Review the relevant communication and acceptance arrangements, not just the purchase price.
Step 4: build a useful evidence picture
Choose evidence related to the intended outcome and the suspected weaknesses. Combine measures with observation and case review where helpful. Define counts, denominators, time periods and exclusions before comparing performance.
| Review question | Possible evidence |
|---|---|
| Did we understand the promise? | Accepted orders and clarification records |
| Did handovers work? | Incomplete inputs and repeated enquiries |
| Were decisions timely? | Escalation cases and their outcomes |
| Did the output serve the customer? | Acceptance, repeat contact and relevant feedback |
| Did a partner dependency hold? | Delivery exceptions and response times |
These are options, not a required collection. Select evidence that informs a decision and avoid building a dashboard simply because information is available.
Step 5: select and test one improvement
Prioritise a change by consequence, likely benefit, effort and uncertainty. Assign an owner, agree the authority needed to change the work and identify any risks the trial could introduce. Decide how to reverse or adjust the trial if it performs poorly.
The guide to improvement as a quality management principle explains why the effectiveness review should be planned before implementation. Specify what result would support adoption and which other outcomes must remain acceptable.
Communicate the trial to everyone affected, including those handling downstream work. A local experiment can unintentionally change their inputs or workload. Keep the scope manageable enough to learn something credible.
Hypothetical example: a focused first month
A hypothetical consultancy chooses the route from accepted brief to first customer review. It finds that project teams repeatedly clarify the same scope questions after work has started. Customers experience delay while consultants experience rework.
The team reviews recent briefs, involves project staff and agrees a short acceptance conversation covering the intended decision, audience and unresolved assumptions. A project lead trials the conversation on suitable new work. The review considers later scope clarifications, customer understanding and time spent preparing the brief.
This hypothetical example illustrates a bounded application of several principles. Its timing is illustrative, not a claim that every organisation can implement its management system within a month.
Step 6: review, adopt and extend carefully
At the agreed review, compare the evidence with the intended result. Explain limitations, including changes in volume or case mix. Decide whether to adopt, modify, continue testing or stop the change.
If adopted, update relevant working information and responsibilities. Share the learning with other teams, but check their conditions before copying the solution. The same visible problem can have a different cause elsewhere.
Use existing management meetings where they support timely decisions. The purpose of applying the principles is better coordination and delivery, so build the review into ordinary work rather than creating seven separate administrative programmes.