A machine shop loses a long-standing customer because every quote takes three days — while the competitor responds in four hours. The internal process has always been that way, and nobody has ever questioned it.
A trading company introduces new business management software and, six months later, realizes that staff have built a parallel workflow in Excel because it "works better than the system."
Three different scenarios, one common denominator: processes that exist but have never been described. When a process lives only in the heads of the people who run it, nobody can observe it, measure it or improve it.
Business process mapping is the structured — usually visual — representation of the activities, information flows and decisions that together produce an output. The ISO 9001:2015 standard treats it as the prerequisite for any quality management system [1]. The BPMN 2.0 notation provides the technical language to describe it unambiguously [2].
ISTAT data (2025) show that fewer than half of small and medium-sized businesses in Italy use integrated business management software — 48.8%, compared with 85.9% of large companies [3]. The Bank of Italy lists the systematic collection and use of information to monitor and improve the production process among the management practices associated with higher productivity [4].
This article describes a practical four-step method for mapping a company's processes, with the essential BPMN symbols, the priority criteria — which processes to map first — and the common mistakes to avoid. The goal is to make the method usable even in companies without a dedicated process manager role.
What "mapping a process" means and why it is not the same as writing it down
If a process exists but no two colleagues describe it the same way, who really owns it? A process does not belong to whoever runs it: it belongs to whoever can replicate it.
Many business owners think their processes are "mapped" because they have written a procedure in a Word file. But writing and mapping are different activities: writing narrates, mapping structures. This section offers a working definition of mapping — what it must contain, in what form and at what level of detail — and distinguishes the concept from the three terms it is most often confused with: procedure, flowchart, automation.
It is worth setting three boundaries that, in day-to-day practice in smaller companies, often remain implicit:
Mapping vs procedure — mapping describes the process as it currently is: what happens, in what order, who does what, where decisions are made. The standard operating procedure (SOP) instructs the person doing the work: how to carry out each step, with which tools, to what quality standard. Mapping comes before the procedure; without mapping, the procedure risks describing how things should be, not how they actually are. For more on operating procedures, the cluster on standard operating procedures (SOPs) covers the next level.
Mapping vs flowchart — a flowchart is a graphic tool. Mapping is the activity of reconstructing and representing processes, which can use different tools: flowcharts, BPMN, swimlanes, value stream mapping. A diagram is the result of mapping, not the mapping itself. The cluster on the business flowchart describes the graphic format in detail.
Mapping vs automation — mapping is a prerequisite for automation, not a synonym for it. Automating an unmapped process means freezing its inefficiencies into software: the result is faster chaos, not a better process. The cluster on business process automation starts from the same premise.
A working definition of process mapping must answer four questions: which activities make up the process? In what sequence do they take place? Who carries them out? What information or materials move from one activity to the next? When all four questions have a visual, verifiable answer, the process is mapped.
Why map business processes: measurable benefits and real limits
What is the real cost, today, of an unmapped process that three people carry out in three different ways? The cost never shows up on a delivery note or a payslip. It shows up in the time the business owner spends solving problems that should never have existed.
The Bank of Italy, studying about 3,200 Italian companies with at least twenty employees, documents that the adoption of structured management practices goes hand in hand with higher productivity, while stating that the analysis is purely descriptive [4]; among the practices measured is how the company reacts to a process problem — whether it simply fixes it or acts so that it does not happen again. The OECD, for its part, places Italian micro-enterprises about 30% below the productivity of their European counterparts [5]. But turning this evidence into operational benefits for a company requires specifics: which concrete advantages you can expect, over what time frame and with what investment of time.
The five most frequently observed benefits:
1. Operational continuity — when a process is documented, anyone can carry it out, even when the person who usually does it is absent. The departure of a key team member stops being an operational emergency.
2. Fewer errors — a process described in a structured way reduces variability in execution. Errors that stem from "interpretations" of the process decrease.
3. Faster onboarding — a new team member who has process maps reaches operational autonomy faster than someone who learns only by informally shadowing colleagues.
4. A basis for improvement — a map is the starting point for any optimization. You cannot improve what you have not first observed and described.
5. A prerequisite for automation — no process can be automated effectively without first understanding its real structure. The map is the handover document between human work and the digital tool.
The three cases in which mapping can be an investment out of proportion to the return:
Contexts with high structural variability — creative processes, highly customized consulting work, management of unique, non-repeatable projects. In these contexts, mapping captures an exception, not a rule.
Processes that are too recent — a process introduced less than three months ago is still evolving. Mapping it at this stage can produce a document that is obsolete before it is distributed. No public survey establishes when it becomes worthwhile to document a process: the three-month threshold is a rule of thumb from organizational practice, not a measured figure.
Processes being phased out — if the decision has already been made to abolish or fully automate a process within six months, the mapping investment makes sense only if the map serves the automation.
Which processes to map first: a priority criterion based on frequency and criticality
If you could map only one process this quarter, which one would most reduce the time the business owner spends putting out fires? It is almost never the most complex process. It is almost always the most frequent one.
A company has dozens of processes. Mapping them all is neither sustainable nor useful: most of the value is concentrated in a small subset. This section proposes a priority matrix — frequency of execution × criticality for the customer × repeatability — that helps you identify the five to seven processes to start with.
The matrix is built on three axes:
Frequency of execution — how often is the process triggered? High frequency (daily or several times a week) means a large return on the mapping investment. Low frequency (monthly or quarterly) can still justify mapping if criticality is high.
Criticality for the customer — does an error in this process have a direct impact on the customer experience? Order fulfillment, complaint handling and sales communication processes have high criticality. Internal administrative processes tend to have lower criticality.
Repeatability — is the process carried out in a comparable way every time, or is every execution different? High variance between executions is a direct signal that mapping will reduce real disorder.
Processes that score high on all three axes are ideal candidates for the first map. Typical examples in Italian companies: standard order fulfillment, customer complaint handling, customer onboarding, monthly cash closing, recurring production cycle.
The empirical validation criterion: the process that, once mapped well, returns observable signals (less time, fewer errors, fewer questions escalated to the top) within eight to twelve weeks is the right process to start with.
The four-step method: observe, represent, validate, standardize
Who should draw the map: the department manager or the person who runs the process every day? The most common answer in companies is the first. The correct answer, in almost every case observed, is the second.
The proposed method consists of four sequential steps. First: observe the process as it is carried out today, not as it should be. Second: represent it graphically with a standard notation. Third: validate the map with the people who actually carry it out, not with those who should carry it out in theory. Fourth: standardize and make the current version visible. Each step has defined timing, tools and outputs.
Step 1 — Observe
The goal of this step is to capture the real process, not the ideal one. The most effective method is shadowing: working alongside the person who carries out the activity during a real execution, observing every step without interrupting or correcting. Alternatively, you run a structured interview: "What do you do first? Then what? What happens if...?" The output of this step is a raw list of activities in the order in which they actually take place.
A common mistake is to start from how the process "should be according to management." The process as documented by management is often an idealized version that does not match daily practice. The map must portray what happens, not what you would like to happen.
Step 2 — Represent
The observed process is translated into a graphic representation using a standard notation. For most companies, the minimum set of BPMN symbols (described in the next section) or a simplified swimlane are the most practical choices. At this stage the map is rough: the goal is to have a visual version to take into validation, not a final document.
The reference standard is the BPMN 2.0 notation from the Object Management Group [2]: an international standard adopted in the leading process mapping software and in university training in industrial and management engineering.
Step 3 — Validate
The rough map is put in front of the people who carry out the process. The guiding question is: "Is this really how it works?" Discrepancies between the map and actual practice always emerge at this stage — and they are valuable. Every correction flagged by the people doing the work improves the map's accuracy. Validation takes thirty to sixty minutes for a process of medium complexity.
A second level of validation, optional but useful, is a walk-through with the manager: a reading of the final map to check consistency with the process objectives and with organizational constraints.
Step 4 — Standardize
The validated map is published in the document management system with a version number and a date. The process is now visible to everyone who carries it out or interacts with it. Versioning is the signal that the document is alive: when the process changes, the map is updated.
The output of this step is also the starting point for formalizing it into standard operating procedures (SOPs), which turn the mapped process into step-by-step executable instructions.
The essential BPMN symbols: how much is enough, how much is too much
If a map can be read only by the person who drew it, is it really useful? A process map is an alignment tool: if it does not align people, it is just the consultant's personal drawing.
The BPMN 2.0 notation includes more than a hundred symbols [2]. Using all of them in a small or mid-sized company is counterproductive: the map becomes unreadable for the people who have to follow it. The minimum set of symbols needed to map 90% of a typical company's processes consists of seven elements.
| Symbol | Name | Use |
|---|---|---|
| Rounded rectangle | Activity / Task | An action performed by an actor |
| Diamond | Decision gateway | A point where the flow splits based on a condition |
| Empty circle | Start event | The point where the process is triggered |
| Circle with double border | End event | The point where the process ends |
| Solid arrow | Sequence flow | The connection between two elements |
| Dashed arrow | Message flow | Information or a document passing between two processes or actors |
| Horizontal rectangle (swimlane) | Lane / Pool | The boundary separating the activities of different actors |
The readability rule is practical: if a symbol needs a legend to be understood by someone who did not draw it, it is a candidate for removal. A process map is an alignment tool, not an academic exercise.
Mapping tools: from paper and sticky notes to professional software
Will process mapping software really solve the problem, or will it turn it into a software adoption problem? In the companies observed, the second outcome is documented more often than the first.
The ISTAT survey (2025) finds that fewer than half of small and medium-sized businesses in Italy have integrated business management software, compared with 85.9% of large companies [3]. This is not necessarily an obstacle: for a first mapping, paper and sticky notes are often more effective than any software. This section proposes a three-level scale of tools, with guidance on when to move from one level to the next.
Level 1 — Manual tools: paper, whiteboard, sticky notes. Ideal for the observation phase and for the first representation. The advantage is speed and flexibility: moving a sticky note is faster than redrawing an element in software. The limit is sharing: a paper map is not easy to distribute to a remote team.
Level 2 — Basic digital tools: Miro, Lucidchart, Draw.io (free). They let you draw diagrams with the standard symbols, share them in real time and maintain them over time. The learning curve is low. Moving up from Level 1 to Level 2 is justified when you need to share the map with people in different locations or when you want to keep a versioned archive.
Level 3 — Professional tools: Bizagi, Signavio, Camunda. They combine BPMN modeling with process management, flow simulation and connection to information systems. Moving up to Level 3 is justified when you want to link the map to workflow automation or when your portfolio of processes exceeds a level of complexity that requires dedicated governance.
The criterion for moving up is not the size of the company: it is the maturity of existing documentation and the concrete problem you want to solve. More sophisticated tools require more time for adoption and training: the investment is justified only if the benefit clearly outweighs the cost.
The link with business process automation is direct: the move from a basic digital tool to a professional platform often coincides with the decision to automate some processes. Mapping is the prerequisite; workflow automation is the next phase.
How to keep the map alive: review, versioning, ownership
How many process maps sitting in company drawers are more than two years old? Most of them. And that is the main reason why "mapping" has a bad reputation in Italy.
The average life cycle of a process map in a small or mid-sized company without a maintenance system is less than twelve months. Without a review ritual, the map quickly becomes a picture of how things were a year ago. This section describes the three mechanisms that make the map a living document: an identified owner for each process, a periodic review ritual and a simple versioning system.
Process owner — every mapped process must have a named owner: a person (or a role) with explicit responsibility for maintaining the map. The owner is not necessarily the person who carries out the process, but the one who is organizationally accountable for it. Without an owner, the review does not happen by default.
Review cadences — the frequency depends on the stability of the process:
- Stable, low-variability processes: annual review, scheduled as a recurring activity in the calendar.
- Critical, high-variability processes: review every six months.
- Triggers for immediate updates: a change of IT system, a significant regulatory change, an organizational change affecting the roles in the process, a recurring error that reveals an unmapped step.
Versioning — the minimum system is a standard naming convention for the file or page: vX.Y — [date], with a changelog at the top of the document describing in one line what changed from the previous version. This way you always know which version is current without having to consult previous ones.
Without these three elements, the mapping investment is lost within twelve to eighteen months. The link with continuous improvement is structural: improvement cycles rely on maps as their starting point; without up-to-date maps, improvement has no baseline to measure from.
Common mapping mistakes and how to spot them in time
Does the map you just drew represent the process as it really is, or as you would have liked it to be? In most first attempts, the second answer is closer to the truth.
Mapping badly is worse than not mapping. A wrong map freezes inefficiency in place, gives the illusion of control and weakens the drive to improve. The recurring mistakes observed in mapping projects in Italian companies are eight.
| Mistake | Warning sign | Practical fix |
|---|---|---|
| Complete but unreadable BPMN | The map uses symbols that need a legend to be understood | Cut down to the seven essential symbols |
| Ideal map instead of real map | The process drawn does not match what the people doing the work actually do | Carry out Step 1 (observation) before drawing |
| Only the manager involved | The people doing the work do not recognize themselves in the map | Interview and observe the people who do the work every day |
| No validation with the people doing the work | The map is distributed without the Step 3 walk-through | Hold the validation session before publication |
| No named owner | The map is not updated when the process changes | Assign an owner before publication |
| Excessive level of detail | The map has dozens of steps for a process that takes five minutes | Map at the right level of granularity for the intended audience |
| Map never published | The file sits on one person's desktop | Publish it in the shared document management system with appropriate visibility |
| No review cadence | The last modification date is more than a year old | Put the review in the calendar as a recurring activity |
Limits and conditions of applicability
The four-step method suits repetitive processes with measurable outcomes: order fulfillment, complaint handling, production cycle, customer onboarding. For these processes, mapping returns observable signals within eight to twelve weeks.
Contexts in which mapping is a less suitable tool include: creative processes (design, research, original content production) where variance is intentional and standardization degrades quality; complex, highly customized sales, where every negotiation is structurally different; unique, non-repeatable projects, where a playbook or coordination rules are preferable to a fixed sequence of steps.
The Bank of Italy survey on management practices [4] covers companies with at least twenty employees, and the authors state that the link with productivity is descriptive, not causal; the OECD data [5] compare size classes across countries. Applying these findings to very small businesses with fewer than ten employees calls for caution: in very small companies, informal documentation can be enough up to a sector-specific threshold of team size and complexity.
In addition, mapping does not solve an organizational problem: it makes it visible. The map is the starting point of the intervention, not the intervention itself. Anyone who expects mapping to produce improvements without operational follow-up (procedure, training, process redesign) will find the method disappointing.
FAQ
How long does it take to map a process? For a process of medium complexity (five to ten steps, two or three roles involved), the four-step method takes less than ten hours spread over two weeks: three to four hours for observation, two hours for representation, one hour for validation, one hour for standardization and publication.
Is it necessary to use BPMN notation? No. The seven essential symbols cover 90% of the processes in a typical company, but even a swimlane drawn with simple shapes produces a useful map. BPMN notation is preferable when the map must be integrated with workflow automation software or shared with partners who use the same notation.
Who should be involved in mapping? The minimum cycle includes: the people who carry out the process (for observation and validation) and the process owner (for standardization and publication). For processes involving several departments, it helps to include one representative from each department in the validation session.
How do you know whether the map is correct? The practical test is a simulation: someone who does not usually carry out the process tries to follow the map. If they can complete the process without asking for help, the map is accurate enough.
Operational summary
Your first map in ten working days: (1) choose the pilot process with the frequency × criticality × repeatability matrix; (2) identify who carries it out and schedule one hour of observation or interview; (3) draw the map with the seven essential symbols; (4) hold the validation session with the people who do the work; (5) publish it in the document management system with version and date; (6) name an owner; (7) schedule the first review.
Signs that mapping is working: the people who carry out the process consult the map on their own; new hires take less time to become autonomous; discussions about "who does what" become rarer and shorter.
Conclusion
Mapping a process does not solve a problem: it makes it visible. It is a subtle but decisive difference.
As long as a process lives only in daily practice, the person who carries it out is its only keeper. Whoever inherits it reinvents it. Whoever pays for it — customer or company — suffers its variance without being able to intervene. Mapping it is the first act of collective ownership: from that moment on, the process stops being private and becomes an asset of the organization.
The initial investment is modest. A well-chosen process, mapped with the four-step method and validated with the people who carry it out, takes less than ten hours of work spread over two weeks. The most frequent return — observed in Italian companies — is a perceived reduction in execution times within the first two to three months, with variability that depends on the organization's starting maturity.
The most common risk is not mapping badly. It is mapping and then not updating. A map that is never revisited becomes, within twelve months, a false representation of reality — and feeds organizational cynicism toward every subsequent attempt to bring structure.
To turn mapping into action, the next step is to formalize standard operating procedures (SOPs), which translate the mapped process into executable instructions. The broader context is described in business systemization, of which process mapping is the second operational pillar.
An unmapped process is a process the company does not yet own. Mapping is the first step of an ownership that, when done well, you no longer notice — because things simply work.
Sources and references
[1] ISO, "ISO 9001:2015 — Sistemi di gestione per la qualità", International Organization for Standardization, 2015. Available at: https://www.iso.org/standard/62085.html
[2] Object Management Group, "Business Process Model and Notation (BPMN) 2.0", OMG, 2011. Available at: https://www.omg.org/spec/BPMN/2.0/
[3] ISTAT, "Imprese e ICT — Anno 2025", Italian National Institute of Statistics, 2025. Available at: https://www.istat.it/comunicato-stampa/imprese-e-ict-anno-2025/
[4] Baltrunaite, A., Formai, S., Linarello, A., Mocetti, S., "Proprietà, governance, management e performance delle imprese", Bank of Italy, Questioni di Economia e Finanza no. 678, March 2022. Invind 2019 survey of about 3,200 manufacturing and service companies with at least 20 employees; the section on monitoring covers the collection and use of information to monitor and improve the production process and how the company reacts to process problems. Structured management practices are positively associated with productivity, with an analysis the authors describe as purely descriptive. Available at: https://www.bancaditalia.it/pubblicazioni/qef/2022-0678/QEF_678_22.pdf
[5] OECD, "Economic Surveys: Italy 2024", OECD, January 2024. Italian micro-enterprises are about 30% less productive than their European counterparts, while large Italian companies are on average more productive than their European equivalents. Available at: https://www.oecd.org/content/dam/oecd/en/publications/reports/2024/01/oecd-economic-surveys-italy-2024_18011b9d/78add673-en.pdf