How to Choose Which Processes to Automate First

Most automation programmes stall not because the technology fails, but because they start in the wrong place — either something too ambitious that never ships, or something too trivial to matter. Here is how to choose well.

Score each candidate on two axes

List your repetitive processes and rate each on value (how much time, money or risk it consumes) and feasibility (how well-defined and rules-based it is). Plot them on a simple grid.

• High value, high feasibility: start here. These are your quick wins.
• High value, low feasibility: worth doing, but later — they need more design.
• Low value, high feasibility: easy but not worth it yet.
• Low value, low feasibility: ignore.

Ask five questions

For each top candidate, ask: How many hours does it consume weekly? How often does it go wrong? Is the process well-defined or does it depend on judgement? How many systems does it touch? What happens if the automation makes a mistake?

Favour the boring and frequent

The best first automation is usually unglamorous: something high-volume, well-understood, and low-risk if it errs. Order data entry, lead capture, invoice processing and status updates all fit. They are frequent enough that the time saved is real, and safe enough that early mistakes are cheap.

Prove it, then expand

Deliver one automation, measure the hours it saves, and use that proof to fund the next. Momentum comes from visible wins, not from a two-year roadmap. Start small, measure honestly, and let results earn the mandate for more.