Business Process Mapping Guide: As-Is, To-Be, Methods & Examples

Business process mapping is the discipline of drawing out how work actually flows through an organisation, so you can see where it breaks, where it wastes effort, and how it should look once improved. This guide covers what process mapping is, the crucial difference between as-is and to-be maps, a step-by-step method, the main notation types, and worked examples, drawing on experience advising FTSE-listed, PE-backed and public sector organisations.

What is business process mapping?

A process map is a visual representation of a business process: the sequence of activities, the decision points, and the inputs and outputs involved in delivering a product or service. Unlike a rough flowchart, an effective process map also captures who does each step, how long it takes, and what it depends on. That makes it the foundation for improvement, automation, compliance and transformation work.

As-is versus to-be process mapping

The distinction most people are searching for is between two states of the same process.

• As-is process mapping documents the process as it runs today, warts and all. Its value is honesty: it exposes the workarounds, duplication and bottlenecks that people have stopped noticing.
• To-be process mapping designs the improved future state: the process as it should run once waste is removed, controls are added and technology or automation is applied.

Good transformation work moves deliberately from one to the other. You map the as-is to understand reality, agree the to-be as the target, and use the gap between them to plan the change.

How to create a process map: step by step

1. Define scope and boundaries. Agree where the process starts and ends, and what is out of scope.
2. Identify the participants. List the roles, teams and systems involved.
3. Capture the steps in sequence. Walk the process with the people who run it, not just their managers.
4. Add decision points and exceptions. Real processes branch; capture the "what ifs".
5. Validate with stakeholders. Confirm the map reflects reality before you rely on it.
6. Analyse and design the to-be. Mark bottlenecks, handoffs and controls, then design the improved state.

Process mapping notations and techniques

• Basic flowchart - simple boxes and arrows, ideal for a first pass or a straightforward process.
• Swimlane (cross-functional) diagram - shows who owns each step across teams, excellent for exposing handoffs and accountability gaps.
• BPMN (Business Process Model and Notation) - a formal standard for complex processes that need precision and shared understanding across analysts.
• Value stream mapping - focuses on flow and waste, drawn from lean, useful when the goal is efficiency and cycle-time reduction.

A worked example

Consider a customer onboarding process. The as-is map might reveal that an approval bounces between three teams and a compliance check is repeated twice because no one trusts the first. The to-be map removes the duplicate check, assigns a single owner, and automates the approval routing. The gap between the two maps becomes the improvement backlog, with an evidenced business case attached.

Common mistakes to avoid

• Mapping how the process is supposed to work rather than how it actually works.
• Adding so much detail the map becomes unreadable.
• Stopping at the as-is and never designing the to-be.
• Mapping in a room without the people who do the work.

Where process mapping fits in transformation

Process mapping is rarely the goal in itself; it is the groundwork for change. Clear as-is and to-be maps underpin automation, cost reduction, compliance and system implementation. For organisations running larger change, it feeds directly into business and digital transformation planning and benefits realisation.

Frequently asked questions

What is the difference between as-is and to-be process mapping?

As-is mapping records the process as it runs today; to-be mapping designs the improved future state. The gap between them defines the change required.

What is a business process mapping methodology?

A structured approach: define scope, identify participants, capture steps and decisions, validate with stakeholders, then analyse the as-is and design the to-be.

What notation should I use for process mapping?

Use a basic flowchart for simple processes, a swimlane diagram to show cross-team ownership, and BPMN for complex processes that need a formal, shared standard.