In one line: Draw how work actually moves, step by step and person by person. The picture reveals waste, hand-offs and missing ownership that nobody can see from inside a single step.
Core idea
Every organization runs on processes, but few people see a whole process end to end. A process map makes it visible, so that a group can agree on how work really flows, clarify who is responsible for what, and spot redundancy and waste. A technical note from the University of Virginia’s Darden School [1] describes four common map types and when to use them.
How it works
| Map type | Shows | Best for |
|---|---|---|
| Process flowchart | steps, decisions and their sequence | documenting a simple process; finding loops and dead ends |
| Swim-lane flowchart | the same steps arranged in lanes by person, role or department | making hand-offs and ownership visible |
| SIPOC | Suppliers, Inputs, Process (high level), Outputs, Customers | scoping a process before mapping it in detail |
| Value stream map | material and information flow, with times and inventory | finding waste and delay (see Value Stream Mapping) |
When to map:
- People don’t share a common understanding of a process.
- The process is complicated, inefficient, or failing its customers.
- A process is being changed or automated.
- New people need to learn it.
How to map:
- Choose the process and its boundaries.
- Gather the people who do the work, not only their managers.
- Map the current process as it really is, not as the procedure says.
- Look for delays, rework loops, unclear decisions and hand-offs.
- Design the improved process and agree who owns each step.
In practice
A quick-and-dirty map of almost anything, such as getting a design through review, onboarding a new engineer, or making breakfast, reveals the same patterns. In engineering design flows, swim lanes typically expose rework loops between design and process or manufacturing engineering (a design fails a rule check and goes back to an earlier step), and waits on approvals that no one is measuring. Once those loops are on paper, they can be shortened, for example by bringing checks earlier or running steps in parallel.
Questions to ask yourself
- Can I draw my team’s main process end to end, including the hand-offs to other groups?
- Where in that process does work loop back, and why?
- Who owns the whole process, rather than just their own step?
Connections
- Specialized version: Value Stream Mapping. Improvement methods: Lean, Six Sigma.
- Engineering cousin: Functional Flow Block Diagram. Ownership: RACI Charting.
- Capabilities exercised: Connecting Across Disciplines, Inquiry, Communicating and Advocacy.