One of the most common mistakes companies make when pursuing ISO certification is jumping into documentation without first defining their scope through proper process identification. Without a clear process map, organizations end up building a management system with no real foundation – writing procedures for the wrong things while missing what actually matters.

The Root of the Problem: Undefined Scope

When companies fail to identify their processes upfront, they lose clarity on what their management system should cover. They write and write, but without a map guiding the effort, they don’t know what to focus on. The result is documentation that doesn’t reflect how the business actually operates.

A well-defined process map – one that clearly distinguishes core processes from support processes – gives companies a direct view of how their business runs and what is generating value. More importantly, it draws a clear line: if a process is on the map, the management system governs it. If it isn’t, it doesn’t need to be included. That alone removes a huge source of confusion during implementation.

A Real-World Example

At one early client engagement, the company had already produced a large volume of procedures and work instructions before bringing in outside help. When asked to map out their core and support processes, critical gaps became immediately visible – procedures existed for secondary activities, while foundational processes had nothing written for them at all. They had been decorating rooms in a house that hadn’t been built yet.

Build the Foundation First

Think of ISO implementation like constructing a house. You can plan the furniture, the décor, and the layout of each room – but none of that matters until the foundation and the architectural drawings are in place. Process identification is that foundation. Once companies can see their processes clearly, they know exactly what needs procedures, work instructions, objectives, and risk assessments – and what doesn’t.

This structured approach narrows the scope of implementation significantly, replacing guesswork with a concrete framework that teams can confidently build on.

Quick Summary

• Define Scope First: Process identification must come before any documentation work begins.
• Core vs. Support Processes: A clear process map distinguishes what drives the business from what supports it.
• Scope Clarity: If it’s on the process map, it belongs in the management system – if it’s not, it doesn’t.
• Avoid Misdirected Effort: Writing procedures without a process map leads to documentation gaps in the areas that matter most.
• Foundation First: Like building a house, structure and planning must precede all other implementation steps.