The Process Approach in ISO 9001: How to Build a Process Map

When a company begins QMS implementation, one of the most difficult topics in practice is not documents and not even the audit — it is the process approach itself. In theory, nearly everyone agrees that “we need to describe the processes.” But as soon as the discussion turns to a process map, the usual questions appear: what exactly should count as a process, how many processes should there be, do we need to identify everything, how should cross-functional links be shown, and why is any of this necessary at all?

The problem is that many organisations still think in terms of departments rather than processes. Production thinks about production, purchasing thinks about purchasing, sales thinks about sales. As a result, the company sees separate functions, but does not clearly see the overall flow of value creation for the customer. Without that, the quality management system quickly becomes formal.

That is exactly why the process approach in ISO 9001 is not just a requirement to “draw a diagram.” It is a shift to a different way of managing: from disconnected functions to interrelated processes with inputs, outputs, owners, indicators, risks, and improvement points. In that logic, a process map is not decoration for an audit, but a tool that helps the organisation see its system as a whole.

The process approach is a way of managing an organisation through understanding and controlling its processes, rather than only through its organisational structure.

A process can be explained simply: it is a sequence of interconnected activities that transforms inputs into outputs and creates a result for an internal or external customer.

For example:

The main idea is that each process should be viewed not in isolation, but as part of an overall value creation chain.

This leads to three important conclusions.

First: a process is usually broader than a single department.

Second: a process matters not only because of what is done inside it, but because of the result it delivers at the output.

Third: the quality of the result depends not on one individual “hero,” but on how well the process is designed and managed.

A process map is a visual representation of those processes and their interactions. It helps answer questions such as:

In ISO 9001, the process approach is one of the basic principles of the whole system.

Clause 4.4 is especially important here. It requires the organisation to determine the processes needed for the quality management system and apply them throughout the organisation.

In practice, this means the company must determine:

So the standard requires much more than simply “having processes.” It requires understanding how they are structured and how they are managed.

It is also important that the requirements of the standard do not explicitly say, “the organisation must have a separate process map in diagram form.” But if a company genuinely wants to show the sequence and interaction of its processes, a process map is one of the clearest and most practical ways to do that.

That is why, in practice, a process map almost always becomes part of a sound QMS implementation.

At first glance, it may seem that a process map is useful only for certification. In reality, its main value is managerial.

A good process map helps to:

Very often, the process map is the first thing that shows management that a problem does not sit “inside one department,” but at the interface between several processes.

For example, a missed delivery date may not be a production problem in isolation, but the result of weak links between sales, planning, purchasing, and production. As long as the organisation thinks in departments, that is hard to see. Once it starts thinking in processes, the picture becomes much clearer.

In practice, it is better not to start with a beautiful diagram. Start with a few simple steps.

It is better to begin not with the organisational chart, but with the question: how exactly does the company create value?

For example:

This already gives a good basis for understanding the key processes.

This is one of the most practical ways to structure the map.

Core processes are those that directly create value for the customer.

For example: sales, design, production, service delivery, logistics.

Management processes are those that direct and evaluate the system.

For example: strategic planning, setting objectives, management review, internal audits, risk management.

Support processes are those that enable the core ones to function.

For example: human resources, IT, metrology, document control, purchasing, infrastructure maintenance.

The key point is not to argue about the “correct” classification as an end in itself. The goal is not terminology, but a clearer understanding of the system.

This is the critical step. A process map is not just a list. It is a way to understand interactions.

You need to see:

For example:

This is where the shift to real process thinking begins.

Each key process should have an owner. This is not necessarily the person who performs every task in the process, but the person accountable for the result of the process, its stability, and its development.

Without an owner, a process almost always remains “nobody’s responsibility.”

One of the most common mistakes is trying to show every detail, every department, every document, and every subprocess at once.

The first process map should be understandable. It should show the system at a high level, not turn into an unreadable wall chart.

It is usually better to create a simple top-level map first and then, if needed, break individual processes down in more detail later.

Drawing the map is not enough. That is only the first step.

The real shift to process thinking begins when the company starts regularly asking questions such as:

That is the point at which the process map stops being “a document for the auditor” and becomes a working management model.

Process thinking is especially important at interfaces. In many companies, employees know their own function very well, but understand poorly what happens before and after them. This creates typical problems:

When an organisation learns to look at the whole chain, the quality of decisions usually improves significantly.

Imagine a manufacturing company implementing ISO 9001.

First, it identifies its core processes:

Then it adds support processes:

And management processes:

After that, the company builds a map showing how an order moves through the system, what information is transferred between processes, where the control points are, where records are needed, and where problems most often arise.

The map then starts to be used in practical ways:

As a result, the map helps not only with the audit, but with understanding the organisation itself much better.

One of the most common mistakes is drawing the process map based on the organisational chart rather than on the real flow of work.

Another is trying to include too much detail too soon. The result is a diagram that is unreadable and useless.

A third is assuming the process map is only needed for certification and can be ignored afterwards.

A fourth is failing to define interactions between processes. In that case, the map becomes only a list of boxes with no management value.

A fifth is not linking the process map with real owners, indicators, risks, and audits.

A sixth is failing to update the map when things change. If the processes change but the map does not, it quickly loses its meaning.

Start at the top level. Do not try to describe every subprocess from the beginning.

Look at the company through the customer’s eyes: where does value creation begin, and through which processes does the result pass?

Use the process map not as decoration, but as a working tool. A good map should help people discuss real issues, not just sit in a presentation.

It is also very useful to connect the map with:

One more important point: the process map should be understandable not only to the quality manager, but also to department managers. If they do not recognise their real work in it, the map has probably been created too formally.

The process approach in ISO 9001 is not a requirement to “draw a diagram for the sake of a diagram.” It is a shift from thinking in departments to thinking in value flows, process interactions, and system-wide management.

A process map is one of the most practical tools for making that shift. It helps the organisation see:

For a company building a quality management system, the process map is an excellent starting point for more mature management. It makes QMS implementation clearer, strengthens the internal audit, supports compliance with the requirements of the standard, and creates a foundation for real rather than formal process improvement.

So the main result of the process approach is not the map itself, but the fact that the organisation begins to think as a system.