Skip to main content

Process mapping guide

How business analysts document and improve processes

A process map is a visual diagram of the steps, decisions, and people involved in completing a business process — the foundation of any improvement or transformation project.

What is process mapping?

A process map is a visual diagram of the steps, decisions, and people involved in completing a business process. BAs use process maps to understand how things work today (As-Is) and design how they should work tomorrow (To-Be).

Why process mapping matters

Most inefficiencies are invisible until you map the process. It is the foundation of any process improvement or digital transformation project.

Loops

Repeated steps that indicate rework or missing clarity

Handoffs

Delays most commonly happen at the point of handoff

Approvals

Often bottlenecks — ask whether each approval is necessary

Manual work

Candidates for automation or tooling improvement

Process map types

Choose the format that matches the complexity and audience of the process you are documenting.

Basic flowchart

Linear sequence of steps. Best for simple processes.

Swim lane diagram

Multiple lanes showing who does each step (departments, roles, systems). Best for cross-team processes.

BPMN (Business Process Model and Notation)

Standardized notation for complex processes. Required for enterprise-level documentation.

How to create a process map (step by step)

Follow these steps in order. Scoping first prevents the most common mistake: a map that tries to show everything and ends up showing nothing clearly.

1

Scope it

What is the start event? What is the end event? What is IN scope?

2

Interview stakeholders

Ask ‘Walk me through exactly what you do, step by step.’ Observe actual work if possible — people often describe the ideal process, not the real one.

3

First draft

Map what you heard. Show it back to stakeholders for corrections.

4

Validate

Walk through the map with someone who runs the process. Find the gaps.

5

Identify waste

Look for loops (repeated steps), handoffs (delays happen here), approvals (often bottlenecks), manual work (automation opportunities).

Common process mapping symbols

These symbols are shared across flowchart and BPMN standards. Learning them lets you read any process map you encounter in a BA role.

RectangleAn activity or task
DiamondA decision point (Yes/No branch)
Oval / CircleStart or end event
ArrowDirection of flow
CylinderData store or system

Tools

Lucidchart appears most often in BA job descriptions. draw.io and BPMN.io are free and sufficient for building your portfolio.

Lucidchartmost common in BA roles
Mirofree tier available
draw.iofree
Microsoft Visioenterprise
BPMN.iofree, BPMN-specific

For your BA portfolio

Map a real process you know from your previous career or a fictional one (e.g., “Customer Onboarding at a fictional SaaS company”). Include both As-Is and To-Be diagrams. This is one of the most valuable portfolio artifacts for BA roles — it demonstrates that you can translate messy reality into clear, structured documentation.

Next steps

Build BA fundamentals in the Business Analyst track

Process mapping is one of several core skills covered in the Business Analyst track. Learn to document requirements, facilitate workshops, and deliver analysis that drives decisions.

Explore the Business Analyst track