How to Map a Workflow Before You Automate It

Pick one workflow, with edges

A workflow is not “sales” or “operations” — that is a department. A workflow has a clear start and end: from a customer asking for a quote to the quote being sent; from an order arriving to it being shipped; from an invoice being issued to the money landing in your account.

Choose the one that hurts most or touches the most money. Write the start and end points down in one sentence each. If you cannot, the workflow is not ready to map — narrow it until you can.

Follow the work, not the org chart

Sit with the people who do the work and follow one real case from start to finish. Not the ideal case — the last actual one, with its missing information and its Friday-afternoon handoff. Ask at each step: what did you receive, what did you do, and what did you pass on?

What you are looking for is the difference between the official process and the real one. The gap between the two is where delays, errors and duplicate work live.

Draw it on one page

Use three shapes: a box for a step, a diamond for a decision, and an arrow for a handoff. Write the name of the person or role responsible under each box. If the map does not fit on one page, you are mapping at the wrong level of detail — group small steps into bigger ones.

Then add two numbers to every arrow: how long the work takes, and how long it waits. In most small businesses the waiting dwarfs the working. A quote that takes 40 minutes of effort commonly takes six days of elapsed time.

Mark the four kinds of waste

Put a mark on each one you find. This takes twenty minutes and gives you a ranked list of what to fix — which is the entire point of the exercise.

• Duplicate work — the same information entered or checked twice
• Dead steps — output nobody reads or uses
• Bottlenecks — steps where work queues up, usually behind one person
• Rework loops — arrows that go backwards because of avoidable errors

Only now, talk about tools

Look at your marked-up map. Fixes fall into three groups: steps to delete, steps to standardise with a checklist or template, and steps where software genuinely removes manual effort. Most maps produce more of the first two than the third.

For the steps that remain, you now have something priceless: a written requirement. Instead of asking a vendor “what can your tool do?”, you can ask “can your tool do this, here, at this step?” That question gets honest demos and accurate quotes.

The takeaway

One page, three shapes, two numbers, four kinds of waste. A workflow you can see is a workflow you can improve — and the map itself is the specification for any automation you buy afterwards. If you would like a second pair of eyes on your map, our workflow analysis service does exactly this with you.