The improvement mindset

In plain words

Clause 10.1 opens the final chapter with a simple widening of view: improving means more than fixing errors. The standard names three directions — make products and services better, correct or prevent undesired effects, and raise the performance of the QMS itself. Together they are the answer to why one runs a management system at all: not to administer a state, but to get better.

The chapter then splits into two halves. The reactive — something went wrong, we go after the cause (10.2) — and the forward-looking — we get continually better, even without an occasion (10.3). 10.1 holds both together and makes clear that improvement also includes the opportunity: the new line of business, the better margin, the more satisfied customer — not only the mishap put right.

For a small company this is no new mandatory exercise but the stance that carries everything before it. Whoever sets objectives (6.2), considers risks and opportunities (6.1), measures and evaluates (9.1) and takes the management review seriously (9.3) is already improving — 10.1 only gives it the name.

Why this requirement exists

Without the explicit duty to improve, a QMS would be a standstill system: built once, confirmed yearly, never better. The clause prevents exactly that. It says a management system has a direction — forward — and that customer requirements and customer satisfaction are the measure of that direction.

The emphasis on the three directions has a practical reason: companies that understand “improvement” only as complaint handling overlook half of it. Whoever never asks what they could proactively do better waits for the problems to find them. 10.1 raises the opportunity to the same height as the error.

What good looks like

Improvement is visible in the operation, not just claimed in the manual: there is a recognisable stream of improvements — out of complaints and audits (the reactive half), out of ideas, customer wishes and observations (the forward-looking). They need not be big; they must be real and tracked. The management review (9.3) is the place where the overview forms: what did we set in motion, what worked, what comes next?

You recognise good by the fact that both halves are alive. A company that only reacts to errors has a well-kept corrective-action list and not a single self-chosen improvement — that shows in the audit. Conversely, a house full of ideas without cause-work on the real problems is just as incomplete.

What changes as you grow: From around 50 people the improvement stream gets light structure — an idea or suggestion path, a fixed point in area meetings. From 100–250 people, where it carries, methods like Kaizen, metric-driven improvement programmes or a continual-improvement officer arrive. The core stays the same at every size: look forward, not only react backward.

The minimum to pass

• It is recognisable that improvement is happening — a stream of actions, not an empty declaration.
• Both directions are represented: reactive (correcting causes, 10.2) and forward-looking (10.3).
• Improvements are aligned to customer requirements and satisfaction, not an end in themselves.
• The overview lives in the management review — that is where improvements are set in motion and followed up.

What an auditor asks for

• Two or three concrete improvements from the last year — one from each direction, with a result.
• The link to customer satisfaction (9.1): did an improvement really move something for the customer?
• The treatment of improvement opportunities in the management review (9.3.2/9.3.3).
• In conversation: can leadership name a self-chosen improvement — not only a complaint put right?

Common traps

• Improvement = complaints only. The most common shortening: a full corrective-action book, not a single proactive idea. The standard names three directions expressly, not one.
• The declaration without a stream. “We continually improve” in the manual, but no example you can show. A sentence is not an improvement.
• The idea without follow-up. Good suggestions that die in the meeting. Without an owner and a date the opportunity is as dead as the untended risk register (6.1).
• Improvement without a customer link. What is internally convenient gets optimised, not what the customer notices. 10.1 names customer requirements and satisfaction as the measure.

Worked example

At Berger Präzisionsteile GmbH both halves run visibly. The reactive: out of the blocked milled lot (8.7) and the internal audit (9.2) came corrective actions with verified effectiveness — the stream that comes out of problems. The forward-looking: out of the opportunity “assembly work” (6.1), via the pilot order, came a new line of business — nobody had fixed an error here, someone had seized a possibility. Exactly this second kind is what most small shops lack, and Frau Berger can name it in the audit without looking it up.

The overview forms in the June management review (9.3): improvement opportunities are a fixed agenda item. Beside the closed setup-sheet matter stands the question of what the next self-chosen undertaking is — this year, to lift assembly work cleanly into the scope (4.3). Improving means, at Berger: put the errors honestly right and not leave the opportunities lying.

← All ISO 9001 topics · To the knowledge hub