Process Mapping visually describes how work actually flows through steps, decisions, handoffs, information, people, systems, and controls.
Definition
Process Mapping is the practice of documenting process flow in a visual form. Maps can show high-level steps, detailed tasks, decisions, handoffs, rework loops, waits, systems, roles, data, and control points.
The purpose is to make the real process visible so teams can understand current performance and improve it.
History
Process mapping has roots in industrial engineering, workflow analysis, quality management, and systems design. Lean, Six Sigma, and business process improvement use maps to reveal variation, waste, defects, and unclear ownership.
When to Use
Use Process Mapping at the start of improvement projects, before root cause analysis, when onboarding process owners, during control-plan design, and whenever people disagree about how work actually happens.
Step-by-Step
- Define process boundaries, customer, supplier, and purpose.
- Choose map type: SIPOC, swimlane, flowchart, value stream map, or detailed task map.
- Observe the process and involve people who do the work.
- Capture steps, decisions, handoffs, inputs, outputs, and delays.
- Validate the map at the gemba or with process evidence.
- Mark pain points, waste, rework, risks, and controls.
- Use the map to prioritize analysis or improvement.
- Update the map after process changes.
Examples
- Manufacturing: A flowchart shows inspection loops and material movement.
- Service: A swimlane map exposes handoffs between sales, operations, and billing.
- Healthcare: A patient-flow map identifies waiting and duplicate documentation.
Common Pitfalls
- Mapping what the procedure says instead of what happens.
- Too much detail too early.
- No clear start and end points.
- Excluding frontline workers.
- Failing to show rework and waiting.
- Creating a map but not using it for decisions.