Why is mapping at the heart of ISO 9001 ?
The process approach is a fundamental requirement of the ISO 9001:2015 standard, formalized in clause 4.4. It involves identifying, managing, and continuously improving all of an organization's processes and their interactions, rather than managing departments or functions in isolation, as noted by the AFNOR Group. This requirement reflects a simple conviction : the quality perceived by the customer never depends on a single department, but on the coherent sequence of multiple processes.
The three macro-process families
Almost all mapping methodologies agree on a classification into three families, which can be found both at AFNOR and in specialized business organization literature.
Core processes
These are the processes that constitute the company's core business: they describe the realization of the product or service, from the customer order to delivery. These are the processes that directly create the value perceived by the customer.
Management processes
Also known as steering processes, they define the company's strategic and organizational direction. They are fueled by all the information gathered from other processes and serve as the basis for management decisions.
Support processes
They provide the resources (human, material, or financial) necessary for the proper functioning of other processes, without directly participating in value creation: human resources, financial management, information systems, and procurement.
According to Eiphedeix Conseil, a well-constructed map ideally includes between 15 and 20 macro-processes ; a useful benchmark to avoid two common pitfalls: a map that is too general and fails to reflect actual activity, or conversely, one that is so detailed it becomes unreadable.
The link between process mapping and the PDCA cycle
This is an often underestimated point. The very structure of the ISO 9001:2015 standard is organized around the PDCA logic. According to the AFNOR analysis, chapters 4 through 6 of the standard correspond to the Plan phase, chapters 7 and 8 to the Do phase, chapter 9 to the Check phase, and chapter 10 to the Act phase.
Process mapping is therefore not an isolated exercise : it is directly integrated into this continuous improvement logic, which we detailed in our article on the QHSE action plan.
How to build your process map, step by step ?
The most effective method is to start at the broadest level before drilling down into the details :
- Identify the macro-processes for realization, management, and support specific to the business activity
- Break down each macro-process into main processes, and then into sub-processes if necessary
- Formalize interactions between processes : inputs, outputs, and data transferred from one process to another
- Appoint a process owner for each process, responsible for its monitoring and improvement
- Document and keep the mapping up to date, as a static map quickly loses all operational utility
The most common mistakes
Two mistakes occur particularly often when building an ISO 9001 map. One is a map modeled on the organizational chart rather than on actual activity flows, and the other is a map that is never updated after its initial creation. It must evolve with the organization, otherwise it risks becoming an audit document disconnected from the reality on the ground.
How does QHSE software facilitate ISO 9001 mapping ?
Representing interactions between processes, associating each process with its risks, indicators, and owner, and then keeping this map up to date as the organization evolves: this is exactly what is structured by the Symalean ISO 9001 Quality module, which directly links the mapping to non-conformities, audits, and the quality action plan.
