Open the editor

Process map

A multi-actor process with the data and tools at every step.

1 process map example

Survey production process

Five steps of a field survey across four divisions, with the data and tools at each one.

Process goes further than a swimlane: every node says who does it, what it produces and which tool is used. The test step is focal because it is the quality gate, and the dashed arrow is the fix loop back to IT.

Open in the editor

What is a process map?

A process map documents how a piece of work gets done from trigger to outcome: the steps, who performs each one, and the data, documents and tools used along the way. It extends a flowchart with the context around each step.

Read it in step order. Each step shows its actor, the inputs it needs and the outputs it produces, so you can trace where information comes from and which system holds it.

When to use a process map

  • Use it to document an operational process, such as producing a survey, for training or compliance.
  • Use it before automating, to see which steps are manual and which tools exchange data.
  • If you only need decision logic without actors and tools, a flowchart is lighter.

How to make a good process map

  1. Define the start trigger and the end outcome before drawing any steps.
  2. Map the process as it is today first; design the improved version separately.
  3. Name the tool or data source at every step, since gaps there are usually the problem.
  4. Highlight manual handoffs and waits that you want to remove.