Business Process Mapping
Build and validate a current-state business process map. Define boundaries, reveal activities, sequence the flow, add decisions, expose roles and handoffs, and identify improvement opportunities without sacrificing clarity on mobile devices.
Map the Current State Before You Improve It.
Business process mapping makes work visible. It helps analysts and stakeholders agree on process boundaries, activities, sequence, decisions, roles, handoffs and improvement opportunities before redesign begins.
- Define an explicit START and END.
- Use clear verb–noun activity names.
- Show decision conditions and branch outcomes explicitly.
- Use swimlanes to show responsibility and cross-role handoffs.
- Validate the current-state map before proposing a future-state design.
Business Process Mapping — Step by Step
Eight locked stages build a current-state refund process from context and boundaries through activities, decisions, roles, validation and improvement.
Understand the Process Context
Customer Refund Request — Current State
Reveal the process context before building the map.
Process Activity and Decision Register
The register records activities, decisions, roles and process purpose in a mobile-readable card format.
Test a Simplified Future-State Design
Experiment Mode is isolated from the guided map. Select improvements to see how the structural process metrics change.
Quick Knowledge Check
Core Mapping Conventions
START / END
Explicit process boundaries. Every process map must show where the mapped process begins and where it finishes.
Activity
A unit of work. Use a clear verb–noun label such as “Verify order details.”
Decision
A condition that creates alternative paths. Label branch outcomes explicitly, such as Yes and No.
Swimlane / Handoff
Swimlanes identify responsibility. A handoff occurs when work moves from one role or function to another.