The method helps clarify workflows, data, causes, and improvements concretely. It identifies patterns, causes, bottlenecks, or constraints and derives actions. The result is captured as a process map, handoff list, and improvement backlog.
Process Mapping
Turns workflows, data, causes, and improvements into a tangible result by setting process boundaries, collecting steps, and deriving a target process.
How does the process actually run, who does what, where do waiting times and handoffs occur, and where are improvement opportunities?
The team follows the steps: set process boundaries, collect steps, mark roles and handoffs, identify issues, and derive the target process. Each step is captured visibly. At the end, a process map, handoff list, and improvement backlog are available so decisions, tests, or actions can follow directly.
Visual orientation
Method sketch for a quick mental model.
Flow
- 1Set process boundaries
- 2Collect steps
- 3Mark roles and handoffs
- 4Identify issues
- 5Derive the target process
The runsheet guides execution with 5 phases, timeboxes, 5 pitfalls, and clear stop criteria.
Open runsheetIdeal for
- Operations improvement
- Service blueprint preparation
- Compliance work
Not good for
- Product strategy
- Deep domain modeling alone
Deep dive
Process Mapping follows a clear working logic: set process boundaries, collect steps, mark roles and handoffs, identify issues, and derive the target process. This turns the method into a visible thinking process instead of only a discussion. Participants move step by step from raw material, observations, or options toward a shared structure. As a result, a process map, handoff list, and improvement backlog are available for decisions, learning, and planning.
Prepare a clear guiding question, the right information, and a visible workspace. Plan for 1-3 h with 3-10 people and use the format in a facilitated workshop. The facilitation needs structure and preparation; short timeboxes, visible intermediate results, and a parking lot for open questions are helpful.
Process Mapping Working TemplateCompact working template for Process Mapping with process boundaries, handoffs, bottlenecks, and improvements.canvas
process-mapping-working-template.md
Compact working template for Process Mapping with process boundaries, handoffs, bottlenecks, and improvements.
Process Mapping Working Template
Goal
Make the flow, handoffs, bottlenecks, and improvement opportunities visible.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Working area
- Process boundaries:
- Main steps:
- Roles and handoffs:
- Delays and bottlenecks:
- Improvement ideas:
Output artifacts
- Process map:
- Handoff list:
- Improvement backlog:
Open questions
- ...
Next step
Owner, date, and success signal.
When to choose differently
Short decision aid for existing alternatives.
Statt Process Mapping, wenn du einen End-to-End-Fluss mit Wartezeiten und Verschwendung vermessen willst.
Similar methods
All methodsTurns workflows, data, causes, and improvements into a tangible result by defining the problem, capturing the current state, and defining follow-up actions.
Turns workflows, data, causes, and improvements into a tangible result by selecting a process, going to the place of work, and recording improvements.
Turns workflows, data, causes, and improvements into a tangible result by clarifying the system goal, identifying the bottleneck, and repeating the cycle after expansion.
Turns workflows, data, causes, and improvements into a tangible result by clarifying scope and goal, observing the current process, and setting the new standard and follow-up.
Turns workflows, data, causes, and improvements into a tangible result by collecting the current standard, observing actual work, and updating and training the standard.
Turns workflows, data, causes, and improvements into a tangible result by clarifying the process and value definition, observing or mapping the flow, and deriving improvements.