What Is Process Mapping in Business Analysis?
Process mapping is the practice of visually documenting the steps of a business process — who does what, in what order, and using what inputs and outputs — to make it easier to understand, analyze, and improve how the process actually works. In business analysis, process maps are a core tool for identifying inefficiencies, gaps, and opportunities for improvement before designing a new system or workflow.
Quick facts
- A process map typically uses standardized shapes (like flowchart symbols) to represent steps, decisions, and handoffs between people or systems.
- Process mapping is usually done for the "current state" first, before designing a "future state" improved version.
- This connects to How to Run a Requirements Gathering Workshop, since workshops are a common way to gather the information needed to build an accurate process map.
Common types of process maps
| Type | Best for |
|---|---|
| Flowchart | Simple, linear processes with clear sequential steps |
| Swimlane diagram | Processes involving multiple people, teams, or systems, showing handoffs clearly |
| Value stream map | Identifying waste and delay across an end-to-end process, often used in operational efficiency work |
| SIPOC (Suppliers, Inputs, Process, Outputs, Customers) | High-level overview before diving into detailed process steps |
Why process mapping matters in business analysis
A business process that exists only as tribal knowledge — understood differently by different people involved in it — is difficult to analyze or improve, because there's no shared, accurate reference point. Process mapping makes the process explicit and visible, which surfaces inefficiencies (unnecessary steps, unclear handoffs, bottlenecks) that are often invisible to people who only see their own part of the process. It also gives stakeholders and technical teams a shared, unambiguous reference when designing improvements or a new system to support the process.
How process mapping is typically done
A business analyst usually starts by mapping the current state — how the process actually works today, based on direct observation, interviews, and existing documentation, not just how it's supposed to work on paper. This current-state map often reveals surprising gaps between the documented and actual process. From there, the BA works with stakeholders to design a future state map — the improved version of the process, informed by the inefficiencies and gaps identified in the current state analysis.
A worked example
A business analyst is asked to improve a company's expense reimbursement process. Mapping the current state reveals: an employee submits a paper form → a manager manually reviews and signs it → the form is physically walked to finance → finance manually enters it into the accounting system → a check is issued. This visual map immediately surfaces several inefficiencies: the manual walk to finance, duplicate manual data entry, and a paper-based approval step. The future-state map replaces this with a digital submission and approval workflow, cutting the process from an average of 12 days to under 3.
Common mistakes with process mapping
- Mapping the process as it's supposed to work, rather than how it actually works, missing the real inefficiencies that only show up in practice.
- Skipping direct observation or stakeholder interviews, relying only on existing documentation that may be outdated or inaccurate.
- Jumping straight to a future-state map without a thorough, accurate current-state map first, risking a redesign that misses real root causes.
- Making the map too detailed or too high-level for its purpose — an overly granular map can obscure the big picture, while an overly simplified one can hide important detail.
FAQ
What tools are commonly used for process mapping? Common tools include Lucidchart, Microsoft Visio, Miro, and even simple whiteboards for early-stage mapping — the specific tool matters less than the discipline of accurately capturing the real process.
How detailed should a process map be? It depends on the purpose — a high-level map is useful for stakeholder alignment on the big picture, while a detailed map is necessary when the goal is identifying specific inefficiencies or designing a precise new workflow.
Who should be involved in creating a process map? Ideally, the people who actually perform the process day to day, not just their managers — direct participants often reveal real-world workarounds and inefficiencies that wouldn't appear in a management-level description.
Is process mapping only used for business analysis? No — it's also widely used in operations, Six Sigma and Lean process improvement, and quality management, though business analysts commonly use it specifically as a foundation for defining requirements for a new system or workflow.