Many companies spend months preparing for ISO certification: written procedures, forms, records and quick training before the auditor's visit. The certificate arrives, is framed at reception, and the work slowly drifts back to how it was. Before the next surveillance audit, the preparation starts all over again.
This is not a problem with the standard itself. It is a problem with treating it as a documentation project rather than a way of running the work.
Three reasons for the gap
Procedures were written to satisfy the auditor: when the quality team writes procedures alone, they come out in formal language that does not resemble the real work, and the people doing the work ignore them.
Quality belongs to one department: if the quality manager is the only one tracking indicators, complaints and corrective actions, the message to everyone else is clear: this is not your business.
Middle management is absent: supervisors and section heads decide what actually happens every day. If they are not convinced by the system and trained to use it, it never reaches the front line.
Building a culture, not a file
- Write procedures with the people who carry them out: a one-page procedure written by the team beats ten pages nobody reads.
- Put indicators into the weekly meeting: returns, complaints or error rates are discussed in the department meeting, not in a quarterly report.
- Train supervisors in problem-solving: simple tools such as root-cause analysis and the plan-do-check-act cycle should be mastered by supervisors, not only the quality manager.
- Reward whoever surfaces a problem: if reporting an error brings blame, the error disappears from the records and stays in the work.
Apply it: a culture test in one walk-through
Walk through a department and ask three employees:
- What is the most important quality indicator in your work, and what is it this month?
- What was the last quality problem, and what changed afterwards?
- If you see a mistake in a colleague's work, what do you do?
If the answers are hesitant or inconsistent, the certificate exists but the culture has not been built yet.
The certificate proves the system exists. Culture is when the system works with nobody watching. The distance between them is covered by supervisors and section heads, not by files.