Process Mapping for Beginners: Draw It Before You Fix It

Choose one process with a clear start and end

Resist mapping the whole company. Pick one process that hurts, and define where it begins and where it ends. For example, 'from the day a customer confirms an order to the day the invoice is sent' is a good boundary. 'Sales' is not.

A useful test is whether you can name a trigger and an output. The trigger is the event that starts the work, such as a purchase order arriving on email. The output is what the next person or customer receives, such as a dispatched consignment and a matching invoice.

Walk the process with the people who do it

Do not draw the process from your own memory or from the official procedure. Sit with the person doing each step and ask, 'What did you do the last time this came in?' Use a real case if you can, and follow one actual order or enquiry from start to end.

Expect differences between what the owner believes and what happens. A step that was added to cover a past mistake, a spreadsheet someone keeps privately, a phone call that replaces a form: these are normal findings and they are the point of the exercise.

Draw it simply

Write each step as a short action on a sticky note: verb plus object, such as 'check stock' or 'raise invoice'. Place the notes left to right in order. Put the name of the person or team responsible above each note, so you can see handoffs.

Use only a few shapes. A box for a step, a diamond for a decision with yes and no paths, and an arrow for flow. Anything more elaborate makes the map harder for the team to read, and a map the team cannot read will not be used.

• One note per step, written as an action
• The owner of each step written above it
• A diamond wherever the path splits into yes or no
• A different colour for steps that wait, repeat or get corrected

Mark the waits, handoffs and loops

Once the map is on the wall, look for three things. Waiting: places where work sits in someone's inbox or tray. Handoffs: every point where work moves from one person to another, because information gets lost there. Loops: places where work goes back for correction.

Ask the team to put a mark on each and, where possible, a rough note of how long work usually waits. Estimates from the people doing the work are good enough at this stage. You are looking for the biggest problem, not an exact figure.

Fix one thing, then redraw

Choose one or two changes that remove a wait or a loop, and test them for a few weeks. It might be a checklist at a handoff, a shared sheet that replaces a phone call, or a rule that approvals happen by a set time of day.

Then redraw the affected part of the map and compare with the old one. Keep both versions. The new map becomes a training tool for new joiners and the baseline for the next improvement.