How to map your company's processes step by step
Process mapping is the practice of visually representing the sequence of activities, decisions, and handoffs that make up a business process. If you cannot see the process, you cannot improve it.
Most companies run on processes that exist only in people's heads. When you map them, you expose bottlenecks, redundancies, and points of failure that were invisible before.
Why map your processes
Mapping is not an academic exercise. It produces direct, measurable benefits:
- Clarity — everyone sees the same picture, eliminating "I thought you were handling that" moments.
- Onboarding speed — new hires understand how work flows without shadowing someone for weeks. See our employee onboarding guide for more on this.
- Error reduction — visible decision points reduce the chance of skipping steps or making the wrong call.
- Continuous improvement — you cannot optimize what you have not defined.
- Compliance — auditors and certifications (ISO, SOC 2) require documented processes.
If your organization already has SOPs, mapping adds the visual layer that SOPs lack. If you do not have SOPs yet, start with what is an SOP before diving into mapping.
Three methods for mapping processes
1. Flowcharts
The simplest and most widely understood method. A flowchart uses standard symbols (rectangles for actions, diamonds for decisions, ovals for start/end) connected by arrows.
Best for: simple to moderate processes with clear decision points. If you want to go deeper on this method, see our dedicated guide on how to create a process flowchart.
2. BPMN (Business Process Model and Notation)
BPMN is the international standard for process modeling. It adds swim lanes (who does what), events, gateways, and message flows. More precise than a flowchart, but requires training to read and create.
Best for: cross-department processes, processes that will be automated, or organizations pursuing formal certifications.
3. Narrative (step-by-step text)
A numbered list describing each step in sequence. No special tools needed — just a document. This is essentially what an SOP is. See how to document processes for a detailed walkthrough.
Best for: straightforward processes owned by a single person or team where a visual diagram would add complexity without adding clarity.
Method comparison
| Criteria | Flowchart | BPMN | Narrative |
|---|---|---|---|
| Learning curve | Low | High | None |
| Visual clarity | High | Very high | Low |
| Cross-team handoffs | Partial | Excellent | Poor |
| Tool requirements | Basic diagramming | Specialized tool | Text editor |
| Maintenance effort | Medium | High | Low |
Most teams get the best results by combining narrative documentation (SOPs) with flowcharts for complex or cross-functional processes.
Step-by-step: how to map a process
Step 1 — Define the scope
Pick one process. Define where it starts and where it ends. A clear boundary prevents scope creep.
Example: "Customer refund request — from the moment the customer submits the request to the moment the refund is confirmed in the system."
Step 2 — Identify the people involved
List every role (not person) that participates. Include handoff points where responsibility shifts from one role to another. These handoffs are where most errors occur.
Step 3 — Document the current state (as-is)
Walk through the process as it actually happens today, not how it should happen. Interview the people who do the work. Watch them do it if possible.
Common discovery: the real process has steps, workarounds, and exceptions that no one ever wrote down.
Step 4 — Capture decisions and exceptions
At every decision point, record the criteria and the possible paths. What happens when the customer does not have a receipt? What happens when the refund amount exceeds a threshold? These branches are where standardization breaks down.
Step 5 — Draw the map
Choose your method (flowchart, BPMN, or narrative) and create the first draft. Keep it at the right level of detail — enough for someone unfamiliar with the process to follow, not so much that it becomes unreadable.
Step 6 — Validate with stakeholders
Show the map to the people who actually execute the process. Ask: "Is this what you do?" Fix discrepancies. This step is non-negotiable — a map that does not match reality is worse than no map at all.
Step 7 — Design the future state (to-be)
Now that you see the current process clearly, identify improvements: remove redundant steps, automate manual handoffs, clarify decision criteria. Create a second map reflecting the improved process.
Step 8 — Publish and maintain
Store the map where your team can find it. Link it to related SOPs and work instructions. Set a review cadence — quarterly is a good starting point.
Common mistakes
Mapping everything at once. Start with high-impact processes: the ones that are broken, frequently executed, or involve many people. A process standardization approach helps you prioritize.
Mapping the ideal instead of the real. If you document how the process should work instead of how it actually works, your map will be fiction. Start with as-is, then improve.
Over-detailing. A map with 80 steps for a process that takes 10 minutes is not useful. Use layers: a high-level overview map, then detailed sub-process maps where needed.
No ownership. Every mapped process needs an owner — someone responsible for keeping it accurate. Without an owner, maps decay within months.
Ignoring exceptions. The happy path is easy to map. The value is in mapping what happens when things go wrong.
Tools for process mapping
You do not need expensive software to start. Here is a practical tier list:
| Tier | Tools | Cost |
|---|---|---|
| Free | Miro (free plan), Lucidchart (free tier), Google Drawings | $0 |
| Mid-range | Lucidchart (paid), Microsoft Visio, draw.io | $5-15/mo |
| Enterprise | Signavio, ARIS, Bizagi | $50+/mo |
For the documentation side — the SOPs, work instructions, and step-by-step guides that accompany your maps — tools like Instruo let you capture processes as you perform them, turning screen recordings into structured documentation automatically.
From maps to living documentation
A process map is a snapshot. Processes change. The real challenge is keeping documentation current as your company evolves.
The most effective approach combines visual maps for understanding the big picture with step-by-step guides for execution. When you pair process mapping with a documentation tool that updates as your processes change, you eliminate the gap between how work is documented and how work is done.
Ready to turn your processes into clear, maintainable documentation? Start with Instruo for free and capture your first process in minutes.