What a good process map actually looks like.

Process maps have a bad reputation, mostly because they are drawn to look impressive rather than to be useful. A good one fits on a page and makes people nod.

Draw what happens, not what should

The official process and the real one are rarely the same. We map the real one: the spreadsheet someone keeps on the side, the Slack message that unblocks everything.

Mark the waiting

Most delays are not in the work itself but between steps. We highlight every handoff where a task sits waiting for someone.

The fastest win is usually not automating a step. It’s removing a wait.

Keep it to one page

If the map needs scrolling, it is too detailed to decide anything from. Detail belongs in the notes, not the picture.

Map with the people who do the work

Managers know how a process is supposed to run. The people doing it know where it actually breaks. We run a short session with two or three of them and a whiteboard — no software, no notation rules.

What every step should show

• Who does it — by role, not by name.

• Which tool it happens in.

• How long it takes, and how long it waits before the next step.

• What happens when something goes wrong.

Turn the map into a shortlist

Once the map is up, the candidates for automation are usually obvious: copying between tools, long waits for approval, steps everyone calls annoying. We circle three, score them, and the map has done its job.

Keep it afterwards. Six months later it is the easiest way to show how much has changed.