Ana has been doing client invoicing for three years. When she was asked to document how she does it, she wrote four lines. By the third review, eleven steps nobody knew existed had surfaced, two that were no longer needed, and one only she did out of habit.
Automating a process you don't understand just makes it fail faster. Documenting it first is the dull part almost everyone skips, and it's the part that saves the most later.
Why Document Before You Automate
Most processes live in the head of whoever runs them, with steps done without thinking, exceptions nobody wrote down and shortcuts that work "because it's always been done this way." Automate that without looking and you'll automate the unnecessary steps and the mistakes too. Putting the process on paper is the cheapest way to find out what's extra, what's missing and who should answer for each part.
How to Do It in an Afternoon
1. Pick one process. The one that hurts most or repeats most. Don't try to document the whole company.
2. Walk through it with the person who actually does it, not the person who thinks it's done that way. Ask them to show you on screen instead of telling you.
3. Write each step down using the template below. One per row, no judging yet.
4. Mark where it gets stuck. Waiting, rework, "ask Laura." That's where your time goes.
5. Ask "why do we do this?" at every step. Steps without a convincing answer are candidates for removal.
6. Assign one owner per step. A step without a name isn't a step, it's a wish.
The Template
Copy these columns into a spreadsheet, one row per step:
Step: the number, in order.
What happens: the action, in one sentence.
Who does it: a person, not a department.
Where it happens: the tool or place (email, Excel, accounting system).
What it needs to start: the input or prior approval.
What it hands off: the concrete result.
How long it takes: real time, not the ideal.
What usually goes wrong: the most common error or delay.
An example with three rows from an invoicing process:
1. Confirm the service was delivered. Sales. Email. Needs the approved quote. Hands off a written confirmation. 10 minutes. Usually confirmed verbally, then nobody can find it.
2. Create the invoice. Admin. Accounting system. Needs the confirmation and tax details. Hands off the issued invoice. 15 minutes. The client's tax details arrive incomplete.
3. Send it and follow up on payment. Admin. Email. Needs the issued invoice. Hands off a scheduled payment reminder. 5 minutes. Nobody looks at it again until the client is late.
When to Stop Documenting
Don't chase perfection. If the process changes every week, document the principle, not every detail. An hour per process is usually enough, and if you're eight hours in, you're writing a manual, not a map.
Then, What to Automate
With the process on a sheet, the question of what to automate almost answers itself: the repetitive steps, with a clear rule and no need for human judgment. Leave the rest to a person. If you get here and find the process has more gaps than you expected, that's a good sign: it means you documented before building anything on top. (If you're wondering whether your operations have outgrown their current tools, see 7 Signs Excel, WhatsApp and Notion Have Stopped Working as Your System, and for the bigger picture, How to Scale Your Operations Without Losing Control.)
See how we organize and automate processes for growing businesses
Want Us to Do It With You?
Tell us which process hurts most. Sometimes a single mapping session is enough to see where to start, and if you can solve it yourself with this template, we'll tell you that too.
