Management Systems That Are Certified but Do Not Work

In projects that start with certification as the goal, the priority is often to prepare answers to the questions the auditor will ask. Procedures are written in the order of the standard's clauses, and forms are designed to meet the requirements. The resulting structure passes the audit but does not match the organisation's day-to-day workflow. Employees carry on doing the work the way they know, while records are completed in bulk as the audit approaches.

When each new standard brings its own forms and record-keeping arrangements, the same information is written into different documents over and over again. As the record-keeping burden grows, employees begin to see records not as part of the work but as an obstacle to it, and the reliability of the records declines. When the quality department alone is seen as the owner of the system, the other departments position themselves as the audited party, and corrective actions become a list tracked by the quality department rather than by process owners.

A management system that works, by contrast, shows itself in day-to-day operations. Process owners know and interpret their own indicators, decisions taken in management review meetings are discussed together with their results at the next meeting, records are kept at the moment the work is done, and internal audits are carried out not only to look for nonconformities but to identify opportunities for improvement. This picture says far more than a certificate hanging on the wall.

A lasting system starts from the organisation's real processes rather than from the clauses of the standard. Once it is understood on site how the work is actually done, the expectations of the standards fit naturally into that flow, a single record is enough wherever several standards ask for the same information, and responsibility passes to process owners. In a system built this way, the certificate becomes a natural outcome of a structure that works.