Earning ISO certification without adding complexity

The challenge 

ISO certification is often approached as a paperwork exercise: procedures get written to satisfy an audit, whether or not they reflect how the work actually gets done. That gap between what's on paper and what happens on site creates exactly the outcome ISO is meant to prevent — complexity nobody uses, and standards that erode the moment the auditor leaves. This company wanted a different outcome: certification the teams could actually recognise in their own daily work, not another layer of procedures built on top of it.

Where we focused 

We were brought in to lead the full path to certification — preparing the process, supporting the certification and surveillance stages. Throughout, the focus stayed on keeping the system grounded in daily reality rather than built above it. Standards were designed to be functional first — understandable by everyone, and useful to the business and to teams in their daily work, not documents that only exist for audit day.

Certification itself was pursued pragmatically. Rather than shaping procedures around what an auditor might expect, we documented what the teams actually do — nothing more. Process improvement stayed close to the ground too: ownership sat with the people who run each process, the 2024 process teams, not with a function set apart from daily work.

What changed 

• ISO certification was obtained the K.I.S.S. way — built on standards the teams actually use, not paperwork layered on top of daily work.

• The certification audit was completed successfully.

• The first surveillance audit was also passed — showing the standards held up under continued scrutiny, not just at initial certification.

• The cost of building and maintaining the ISO system dropped by roughly a factor of 3, a direct result of designing it around real practice instead of audit-driven paperwork