Process Mapping as Implementation Foundation
Process mapping must precede documentation. The fundamental mistake in rushed ISO 9001 implementations is writing procedures before understanding what processes actually exist and how they interact. You should document what exists, not what you wish existed. Premature documentation creates compliance-only QMSs where the procedures do not match reality and staff cannot follow them. A thorough process mapping phase produces process maps, turtle diagrams, and interaction matrices that become the foundation for all subsequent documentation. Before anyone writes a procedure, everyone must agree on how the process works.
Identifying QMS Processes
ISO 9001 requires a process approach to quality management. Your QMS consists of interconnected processes that together deliver your products and services and maintain the management system itself. The standard way to organize this is into three categories: Core processes (also called operational or realization processes) that directly deliver products/services; Support processes that enable the core processes; and Management processes that provide governance. Start with questions: What processes directly produce our products or deliver our services? What supporting capabilities do they require? What governance activities oversee the QMS? Map the answers, and you have the complete process system.
Core / Support / Management Process Categories
| Process Type | Purpose | Examples | ISO 9001 Clauses Covered |
|---|---|---|---|
| Core | Deliver products/services to customers | Sales, Design/Development, Production, Service Delivery, After-Sales Support | Clauses 8.2, 8.3, 8.4, 8.5, 8.6 |
| Support | Enable core processes | HR, IT, Finance, Facilities, Procurement | Clauses 7.1, 7.2, 8.4 |
| Management | Govern and improve the QMS | Quality Planning, Internal Audit, Management Review, Improvement | Clauses 5, 6, 9, 10 |
The Turtle Diagram
The Turtle Diagram format shows a single process with: Inputs (what comes in), Outputs (what goes out), Who (people and competence required), What (resources and equipment), How (procedures and methods), Measures (KPIs and performance indicators). Turtle diagrams work because they force complete thinking about each process. When you cannot articulate what a process measures, you know the process is not yet well understood. When you cannot name the people responsible, you have an ownership gap. Turtle diagrams are also audit-friendly: a certification auditor can look at a turtle diagram, understand the process, ask specific questions, and verify that the documented reality matches what staff say actually happens.
Process Interaction Map and Matrix
The Process Interaction Map shows how processes connect: which process outputs become inputs to which other processes. This mapping reveals handoffs between departments, dependencies that create risk if one process fails, and information flows that must be controlled. The Process Interaction Matrix is a table showing all processes on both axes, with cells marked where process X outputs feed process Y inputs. This matrix satisfies ISO 9001 Clause 4.4 requirement to demonstrate how QMS processes interact. When filled in carefully, the matrix also reveals islands of disconnected processes, which indicate scope or design issues.
Process Documentation Levels
| Documentation Level | When to Use | Format | Audit Value |
|---|---|---|---|
| Process Map | All QMS processes | Flow diagram or table | Shows process system architecture |
| Procedure | Processes where absence of documentation creates risk | Written procedure or flow chart | Shows process how-to |
| Work Instruction | Specific tasks requiring precise execution | Step-by-step instruction | Shows task-level control |
| Form/Record | Evidence of process execution | Template | Evidence of conformance |
Not every QMS process requires a detailed written procedure. ISO 9001:2015 allows you to determine the level of documentation needed based on risk. A core manufacturing process requires detailed procedures; a weekly planning meeting may require only a checklist. The correct approach is: map every process with a turtle diagram; write procedures for processes where lack of documentation creates risk of non-conformance; use forms and records to capture evidence of execution. This produces a lean, auditable QMS rather than a documentation burden.
Process Owner Assignment
Every QMS process must have a named owner — typically a manager or team leader who has responsibility for that process working correctly. The process owner is accountable for: the process works as documented; staff are trained to execute the process; the process is measured and monitored; improvements are implemented when performance falls short. In small organizations, one person may own multiple processes. In larger organizations, process ownership crosses departmental lines (the sales process owner may be responsible for sales, order entry, and credit check — spanning three departments). Clear process ownership is what makes ISO 9001 effective as a management tool, rather than just a documentation archive.
| KEY IDEA | Process mapping reveals gaps, overlaps, and undocumented dependencies that organizations did not know existed before starting ISO 9001. This discovery phase is one of the highest-value activities in QMS implementation — not because it produces documents, but because it produces organizational self-knowledge about how work actually flows. |
| IMPORTANT | Document what actually happens in practice, not what should happen in an ideal world. An ISO 9001 auditor will interview staff and observe operations to verify that documented processes reflect reality. If your procedures describe a world that does not exist in your organization, you will generate major nonconformities. Document the current state first; improve it through the QMS over time. |
| BITLION INSIGHT | Indonesian organizations implementing ISO 9001 for the first time consistently underestimate the process mapping phase. Allow 6–8 weeks for a thorough mapping exercise, including workshops with each process team to document inputs, outputs, controls, and KPIs. Process maps produced by the QMS Lead without process owner involvement rarely survive the Stage 2 audit intact. |