Practice knowledge base
Process Mapping
Process Mapping visualizes the workflow from input to outcome, showing the stages, approvals, responsible roles, and points of loss.
Documentation sections
What it is
Process Mapping is a description of a process in the form of a diagram: steps, inputs, outputs, roles, decisions, handoffs between teams, and control points. This practice helps eliminate different interpretations of how the work should actually happen. It is especially useful when a process exists in the heads of individual people, which leads to delays, duplication, or disputed areas of responsibility.
When it helps
- Teams understand the sequence of steps and approval rules differently.
- Work often gets stuck between departments without a clear owner of the next action.
- You need to identify bottlenecks, unnecessary checks, or repetitive manual operations.
- The organization is preparing a process change, automation, or the implementation of a new system.
How to start
- 1 Choose one specific process with a clear beginning and end, such as handling a request or onboarding a client.
- 2 Bring together participants in key roles and document the actual flow of work, not the desired version.
- 3 Mark the inputs, outputs, decisions, handoffs of responsibility, waiting times, and tools used at each step.
- 4 Identify delays, duplication, unclear owners, and steps with no management value.
- 5 Agree on the target map, the process owner, and the immediate changes, along with a measurable review deadline.
Expected effect
Teams get a common language for discussing the process and can more quickly see where time, quality, and accountability are lost. Managers can make decisions about redistributing roles, simplifying approvals, and automating work based on the actual picture of how the work gets done.
Common pitfalls
- Mapping the ideal process instead of the actual one and missing the real causes of delays.
- Stopping at the diagram without assigning a process owner, setting improvement deadlines, or reviewing the result.
- Making the map too detailed and turning it into a document that no one uses.
- Not involving adjacent teams, even though the biggest losses happen precisely in the handoffs between them.
Further reading
- Geary A. Rummler, Alan P. Brache — Improving Performance: How to Manage the White Space on the Organization Chart.
- Michael Hammer, James Champy — Reengineering the Corporation.
- Object Management Group — Business Process Model and Notation (BPMN) specification.
FAQ
Do you need a special notation such as BPMN?
For a first pass, a simple diagram with steps, decisions, roles, and handoffs is usually enough. BPMN is useful when the process needs to be formally described for automation or cross-system integration.
Who should maintain the process map?
It is best to assign a process owner who is responsible for keeping the map up to date and managing changes. The information itself should be collected with the participation of the people who actually do the work at different stages.
How do you know whether the process map was useful?
The practice is useful if it leads to concrete decisions afterward: unnecessary steps are removed, owners are assigned, waiting times are reduced, or requirements for automation are defined.