Key Takeaways
- A process map is a visual representation of what a company does to deliver value to its customers, and of how those activities connect. It reads left to right: it starts with what the customer needs and ends with what they receive.
- ISO 9001 requires determining processes, their inputs, outputs, sequence, and interaction, but it doesn't require a map format. ISO's auditing guidance says so explicitly.
- A process can take weeks even when the actual work takes minutes. Michael Hammer documented in 1990 an application that spent 22 days in process and received 17 minutes of actual work (Harvard Business Review).
- Labor productivity in Colombia is USD 18.9 per hour worked, compared with USD 68.1 in the OECD (Private Council on Competitiveness, National Competitiveness Report 2025-2026, with ILO data). Part of that gap lives in processes nobody has looked at closely.
- The process map is the step before automating or applying AI. Automating a process nobody has drawn only makes it messy faster.
Most process maps are made to pass an audit and end up in a folder. They're drawn once, printed for the auditor's visit, and nobody looks at them again until the next certificate renewal.
That's a shame, because done well it's the cheapest tool a company has to understand where its time and money go. This guide explains what a process map is, what it should include, how it differs from a flowchart, and how to build one step by step so it helps you decide what to improve, what to automate, and where technology is worth it. It's part of our guide to digital transformation for businesses.
What is a process map?
A process map is a diagram that shows, on a single page, a company's main processes and how they relate to turn a customer need into a delivered product or service. It doesn't show tasks or people; it shows blocks of work and the order in which they connect.
A process, according to the ISO 9000 definition cited in ISO's auditing guidance on processes, is a set of interrelated or interacting activities that use inputs to deliver an intended result. Selling, producing, shipping, invoicing, and collecting are processes. The map puts them together so you can see the whole company.
In Colombia the term is especially well known because public entities work by processes under the Integrated Planning and Management Model (MIPG). The process management guide from the Administrative Department of Public Service defines it as the graphic representation of how the organization operates to understand and meet the needs of its stakeholders. The same logic applies to a private company.
What is a process map for?
A process map lets you see the company as a system rather than as an org chart. The org chart shows who reports to whom. The map shows how work flows from the moment an order comes in until the customer is satisfied, and that flow almost always crosses several departments.
In practice, a good map helps a manager with four decisions:
- Where the bottleneck is. When you draw the full flow, the points where work piles up waiting for an approval or a piece of data become visible.
- What adds value to nobody. Repeated steps, reports nobody reads, and data typed into two systems come to light.
- What's worth automating or supporting with AI. You can only decide about a process you already understand. We explain it in business process automation: when you need AI and when you don't.
- Who is accountable for each result. Many problems live in the space between two departments, where nobody owns the full result.
Michael Hammer showed it with an example that still holds. In his 1990 Harvard Business Review article, Reengineering Work: Don't Automate, Obliterate, he described an application that spent 22 days in process and received just 17 minutes of actual work. The rest was waiting. Without a map, that dead time is invisible.
Which types of processes go on a process map?
A process map sorts processes into three groups, and Colombia's public sector adds a fourth. The classification isn't a formal requirement, but it helps you read the company at a glance.
| Process type | What it includes | Examples in a mid-sized company |
|---|---|---|
| Strategic | Those that set direction and the rules of the game | Strategic planning, long-term commercial management, quality management |
| Core, operational, or key | Those that produce and deliver what the customer pays for | Sales, production or service delivery, shipping, after-sales service |
| Support | Those that make the core processes possible | Purchasing, HR, accounting, IT, maintenance |
| Evaluation (public sector) | Those that measure and control performance | Internal control, audit, indicator tracking |
The most common layout puts strategic processes at the top, support processes at the bottom, and core processes in the middle, left to right. The customer need goes on the left and the satisfied customer on the right. It's the pattern used in the Colombian public sector guide and in most quality management systems.
How does a process map differ from a process characterization and a flowchart?
They differ in level of detail. The map shows the whole company on one page, the characterization describes one process, and the flowchart shows step by step how it's done. They're three levels of the same work, and mixing them up is why many maps end up unreadable.
| Level | Tool | What it answers | Example |
|---|---|---|---|
| Level 0 | Process map | What does the company do and how do its processes connect? | One page with 8 to 15 processes |
| Level 1 | Process characterization (or SIPOC) | Who supplies what, what goes in, what comes out, for whom, who's accountable, and how it's measured? | One sheet per process |
| Level 2 | Flowchart or BPMN | What are the exact steps, who does them, and where are decisions made? | Step by step for "invoice an order" |
SIPOC is a quick way to characterize a process: suppliers, inputs, process, outputs, and customers. For level 2, the most widely used standard is BPMN, which the OMG describes as the de facto standard for business process diagrams, clear enough for business users and precise enough to be translated into software.
How to build your company's process map, step by step
This is the order we recommend. It works the same for a company seeking ISO 9001 certification as for one that just wants to understand where its time goes.
1. Start with the customer
Write down what the customer needs when they arrive and what they receive when the company finishes its work. Those two ends are the start and finish of the map. If the company has several types of customers with very different needs, like distributors and end consumers, it may need a core line for each one.
2. List what the company actually does
Bring together the people who do the work, not just the managers, and ask them what they do from the moment an order comes in until it's paid. Write everything on cards or sticky notes, without ordering it yet. What management thinks happens and what really happens are usually two different things, and the map has to show the second.
3. Group activities into processes and classify them
Group the activities that pursue the same result and give each group a name that starts with a verb: "sell," "produce," "ship." Then classify each process as strategic, core, or support. For a mid-sized company, a map of 8 to 15 processes is usually manageable. If you have 40, you're mixing processes with tasks.
4. Draw the map on a single page
Put the customer need on the left, the satisfied customer on the right, core processes in the middle in the order they happen, strategic processes above, and support processes below. Draw arrows only where there's a real handoff between processes. If it doesn't fit on one page, it has too much detail.
5. Characterize the processes that matter most
For core processes, fill in a sheet with suppliers, inputs, main activities, outputs, customers, owner, and indicator. This is what ISO 9001 asks for in clause 4.4: determine each process's inputs and outputs, its sequence and interaction, who is responsible, and the criteria to measure it. You don't need to characterize all of them in the first month.
6. Go into detail only where it hurts
Pick the two or three processes where the most time or money is lost and draw their flowchart as it's done today, not as it should be done. Measure how long each step takes and how much time the work spends waiting. That's where Hammer's 22 days with 17 minutes of work show up.
7. Use the map to decide
With the critical processes drawn, decide what to eliminate, what to simplify, what to automate, and where to use AI, in that order. To see how to prioritize, read how to implement artificial intelligence in a business. And come back to the map whenever something important changes in operations, because an outdated map is worse than no map.
Common mistakes when making a process map
Most maps that don't work fail for the same reasons, and almost all of them have to do with why the map was made.
| Mistake | What happens | How to avoid it |
|---|---|---|
| Drawing the process as it should be | The map doesn't show the real problems | Build it with the people who do the work and draw the "as is" |
| Doing it only from management | The exceptions and shortcuts people use are missing | Workshops with people from each department |
| Confusing the map with the org chart | Departments show up instead of processes | Name each process with a verb and its result |
| Putting too much detail in level 0 | Nobody understands it | One page for the map; detail goes in the sheets and flowcharts |
| Doing it only for the audit | It stays in a folder and nothing changes | Use it to decide improvements and review it every year |
| Automating without redesigning | Technology copies the same problems, faster | Simplify first, automate later |
The last mistake is the most expensive, and Hammer described it more than three decades ago with a line that became a classic: stop "paving the cow paths," that is, stop embedding processes nobody reviewed into software.
Which tools can you use to make a process map?
You can make a process map with paper and sticky notes, and for the first workshop that's best, because everyone can move the cards. To produce a clean version there are free tools or tools with free plans:
| Tool | What it's for | Free plan |
|---|---|---|
| draw.io (diagrams.net) | All kinds of diagrams, including maps and flowcharts | Free and open source, no sign-up; includes a feature to generate diagrams with AI |
| Bizagi Modeler | Modeling processes with BPMN notation and simulating them | Free individual version |
| Lucidchart | Collaborative diagrams with AI-assisted generation | Free plan with limits |
| Miro | Collaborative whiteboard for remote workshops | Free plan with 3 editable boards |
The AI features in these tools can draw the diagram from a description, which saves time when producing the clean version. What no AI can do is tell you how your process really works. That comes from the people who do it every day.
Real case: starting with the process, in numbers
In August 2026 we worked with eighteen companies in Ciudad Juárez at Innova Lab V3.0: cement producers, maquilas, metalworking shops, retailers, and a bakery chain. Before talking about any technology, each company had to describe its process in one sentence with numbers: when this happens, today we do that, it takes us this long and costs us this much.
That sentence is a process map reduced to its essentials. It forces you to identify where the process starts, what happens in the middle, how long it takes, and what it costs. With that clarity, in three days the companies left with working prototypes: a metalworking plant, a purchase order analyzer for the traceability it had been tracking by hand; a cement company, a system that assigns each order to the nearest distribution point; a tire distributor, an inventory analyzer that replaced hours of work in Excel.
None of those solutions would have happened without first understanding the process, and they were built by the same people who live it, as we explain in what employee-driven digital innovation is. Read how the workshop in Ciudad Juárez went.
At Suricata Labs we use our own process mapping method in our diagnostics, which lets us go from the map to a prioritized list of what to optimize, what to automate, and where to use AI.
Frequently asked questions about process maps
Is a process map the same as a flowchart?
No. A process map shows all of a company's processes and how they connect, on a single page. A flowchart shows step by step how a single process is done, with its decisions and owners. You make the map first and then draw the flows of the processes that matter most.
What is a process characterization?
A characterization is the sheet that describes a process: its objective, owner, suppliers, inputs, activities, outputs, customers, and indicators. It's the intermediate level between the map and the flowchart, and in Colombia it's a common requirement in the public sector and in quality management systems.
Does ISO 9001 require a process map?
It doesn't require a map as such. ISO 9001 requires determining processes, their inputs and outputs, and their sequence and interaction, and ISO's auditing guidance clarifies that the standard doesn't specify the format; a process map is one of the accepted ways to document it. The sixth edition, ISO 9001:2026, was scheduled for publication in September 2026, so it's worth reviewing the changes if your company is certified.
How long does it take to make a company's process map?
The overall map can come out of one or two workshops with the right people. What takes longer is characterizing the processes and drawing the detail of the critical ones, and that's best done in stages, starting with the processes where the most time or money is lost.
Can you make a process map with artificial intelligence?
AI can help draw and organize it: tools like draw.io or Lucidchart generate diagrams from a written description. But the information about how the process works has to come from the people who do it. An AI you describe the ideal process to will draw the ideal process, not the real one.
A map that gets used is worth more than one that's well drawn
The best process map isn't the prettiest or the most detailed, but the one the company uses to make decisions. If after drawing it you know the three processes where the most time is lost and what you'll do about each one, it did its job.
If you want to build your company's process map and walk away with a prioritized list of improvements, at Suricata Labs we do it with your team, using our diagnostic method.
See how we work with companies | Schedule a conversation
Read also: Business process automation: when you need AI and when you don't
Last updated: September 23, 2026
