How to Map a Process: Step-by-Step Guide

Pick any process in your organization and turn it into a clear, shareable diagram in one sitting. Here is how.

Step 1: Pick one process and define its boundaries

The most common mistake is trying to map everything at once. Define:

1. Trigger — what kicks off the process?
2. Outcome — what does "done" look like?
3. Roles — who is involved?

Good scope: "How we onboard a new employee, from offer acceptance to first day setup."
Too broad: "How HR works."

Step 2: Talk to the people who do the work

Do not map from memory or policy documents. Ask the people on the ground:

• "Walk me through what happens when [trigger]. What do you do first?"
• "Then what? Who gets it next?"
• "What can go wrong at this step?"
• "Is there anything you do that is not in the official procedure?"

That last question is the most important. The gap between official and real is where the insights live.

Step 3: Draw the happy path

The ideal scenario — everything goes right:

Offer accepted → Send welcome email → Prepare contract → Sign contract → Set up laptop → Set up accounts → Assign buddy → Orientation → Done

Do not worry about exceptions yet.

Step 4: Add decisions, parallel work, and roles

• Decisions — where does the process branch?
• Parallel work — IT sets up the laptop while the manager assigns a buddy
• Roles — put tasks in the right lane
• Handoffs — where work moves between people

If you are using BPMN, parallel gateways (+) show concurrent work, exclusive gateways (X) show decisions, and lanes show responsibilities.

Step 5: Validate with everyone involved

Show the map to every person who touches the process:

• "Does this match what actually happens?"
• "Am I missing any steps?"
• "Where does this break down most often?"

This almost always reveals surprises.

Step 6: Look for improvements

With a validated map, patterns become visible:

• Bottlenecks — everything waits on one person
• Redundancies — same data entered in two systems
• Unnecessary handoffs — work bouncing between people
• Missing error handling — what happens when things go wrong?
• Automation opportunities — manual steps a system could handle

Practical tips

• Keep it on one page — if it doesn't fit, you're too detailed
• Use verb-noun labels — "Review application", not "Application"
• Map current state first — as-is before to-be
• Date your maps — processes change, undated maps can't be trusted

---

Read the full guide with interactive BPMN diagrams: How to Map a Process