Guides
Process mapping: a practical guide
Process mapping means drawing how work actually flows from a trigger to an outcome: the steps, who does each one, the decisions and the hand-offs. A map makes the process visible so a team can agree on it, train people on it and improve it.
Why teams map processes
A process that lives in people's heads works until someone is absent, a new person joins, or a customer complains. Mapping it gives the team a shared picture. The most common reasons are:
- Onboarding and training: a new colleague understands the job in minutes.
- Alignment: sales, operations and finance often describe the same process differently. The map forces one version.
- Improvement: delays, rework and unclear responsibilities become visible. See improving a process with a flowchart.
- Compliance and quality: audits and certifications usually require documented procedures.
- Automation: before automating, you need to know exactly what happens, including the exceptions.
Choose the level of detail
Start from the question you want to answer.
- High level: five to ten boxes that show the main stages, for example "Order, Pay, Ship, Invoice". Useful for executives and for scoping.
- Detailed flowchart: every step and decision of one stage. Useful for the people who do the work.
- Swimlane map: the detailed flow, organised by owner, to show hand-offs. This is the most useful format for cross-team processes; see swimlane diagrams.
If the process will be executed by a workflow engine, you may need a formal notation. Flowchart vs BPMN explains when that is worth it.
How to run a mapping session
- Pick one process with a clear start and end. "Customer onboarding from signed contract to first invoice" rather than "Sales".
- Invite the people who do the work, not only their managers. Two to five people is enough.
- Walk through a real recent case instead of the theoretical procedure.
- List the steps, then the decisions, then the owners. The method is the same as in how to make a flowchart.
- Mark the pain points directly on the map: waits, rework loops, double entry, unclear approvals.
- Share the map and ask for corrections within a few days, while the details are fresh.
Start from what already exists
Most companies already have written procedures, emails or tickets that describe their processes. Turning a written procedure into a map is often faster than starting from a blank page: see converting an SOP into a flowchart. An AI flowchart generator can draw the first version from that text, so the session is spent correcting the map rather than drawing it.
A worked example
The customer onboarding flowchart shows a complete map with three owners, a loop for missing information and an automated identity check, from the first description to the final diagram.
Keep the map alive
A map is only useful if it matches reality. Store it where the team works (a wiki, a README, a shared drive), name an owner, and review it when the process changes. Keeping maps as text, for example as Mermaid code, makes changes easy to track over time.
In this guide
Each article goes deeper into one part of the topic.
- Swimlane diagrams: what they are and how to make oneA swimlane diagram is a flowchart divided into lanes, one for each actor: a person, a team or a system. Every step sits in the lane of whoever performs it, so you can see at a glance who does what and where work passes from one owner to another.
- Flowchart vs process map vs BPMNUse a flowchart to explain a procedure to people, a process map to analyse how a business process works across teams, and BPMN when the diagram must follow a formal standard, typically to be executed by a workflow engine or exchanged between modelling tools.
- How to turn a written procedure (SOP) into a flowchartTo turn an SOP into a flowchart, extract the trigger and outcome, rewrite each instruction as one step with an owner, turn every "if" into a decision with labelled branches, and add the exceptions the document leaves implicit. Then check the chart against a real case.
- Customer onboarding flowchart: a worked exampleA typical customer onboarding flowchart has four owners (customer, sales, back office, system), a loop that sends incomplete applications back to the customer, a KYC check with a rejection branch, and an automated account creation followed by a welcome message.
- Finding bottlenecks and improving a process with a flowchartMap the current process as it really runs, mark where work waits, loops back or changes hands, then draw the improved version and compare the two. The flowchart turns vague complaints ("it takes too long") into specific places to fix.
Turn your process into a flowchart
Describe it in a few sentences. Flowchartio draws the flowchart, then you refine it in conversation.
Generate a flowchart