Most businesses answer this question by starting with the task that annoys them most. It's an understandable instinct, and it's usually the wrong place to start.
The most annoying task is often visible, contained and only mildly expensive. The work worth automating first is usually less visible: a handoff, the moment information has to move from one person or tool to another before anything else can happen.
Look for the waiting, not the work
Pick one thing that comes into the business, like a new enquiry, an order or a support request, and follow it from the moment it arrives to the moment it's finished. Write down every step. Then mark each place where it waits for a person to move it on.
Those waits are the bottleneck. A task that takes two minutes but waits half a day for someone to notice it costs far more than the two minutes.
Three questions for every step
For each step you wrote down, ask:
- Does it need judgment? If a person is deciding something that depends on context, keep the person. Help them decide faster instead.
- Is the information already somewhere else? If someone is re-typing what a form, email or tool already holds, that step shouldn't exist.
- Does anything wait for it? If the next step can't start until this one finishes, it's on the critical path. Start there.
The first thing to automate is usually a step that needs no judgment, re-types existing information, and holds everything behind it.
Remove before you automate
Before you automate a step, check whether it should exist at all. A lot of manual work is a workaround for an earlier problem: a report nobody reads, an approval nobody refuses, a spreadsheet that exists because two tools don't share data.
Automating a broken process only makes the broken process faster.
Removing a step is cheaper than automating it, and it never breaks.
Start small, but connected
The best first automation is small enough to finish quickly and connected enough to matter: the new enquiry that creates its own record, notifies the right person and schedules its own follow-up. One workflow, end to end, that your team can see working.
Then measure what changed, and use what you learned to choose the next one.
If you'd like a second pair of eyes on the first step, show us the process. We'll tell you where we'd start.