Which Processes to Automate First: 5 Criteria

Which Processes to Automate First: 5 Criteria

· by Panayot Dimkov

Which processes should you automate first? The ones that repeat often, follow stable rules, receive their data through a tidy channel, can tolerate an error without serious consequences and have an owner who can validate the result. In practice, though, the choice is nearly always made on enthusiasm: people automate whatever sounds most modern, whatever the boss asked for or whatever the vendor knows how to build. Choosing by criteria takes an afternoon and completely changes the outcome of the first project — which is the one that decides whether there will be a second.

A warning to start with: the most painful process is rarely the best first candidate. It tends to be the most complex, to touch the most people and to carry the most exceptions. Starting there means starting with the hard thing while the team still has no confidence in the tool.

1The five criteria for prioritising processes

01
Frequency times unit time
Not how much it hurts, but how often per month multiplied by what each occurrence costs. A two-minute task done two hundred times beats a two-hour task done once.
02
Stability of the rules
Is it done the same every month, or does it change by customer, by month and by who is in that day? A process that changes every quarter gets automated and rebuilt every quarter.
03
Quality of the input
If data arrives through a controlled channel in a known format, the project is short. If it arrives five ways and everyone writes it differently, the real work happens before automating.
04
Cost of being wrong
An error caught and corrected at the next step is acceptable in a first project. One that reaches a customer or moves money is not. The first case should tolerate failure.
05
Who suffers it and who decides
There must be an identifiable person whose work it removes and who can say whether the result is good enough. Without that person, the project grades its own homework and always passes.
If you could keep only one, keep the second. Rule stability predicts success better than volume: a frequent but shifting process produces a flow that needs constant tweaking, and maintenance eats the saving.

2The effort-impact matrix, properly defined

The effort-and-impact matrix is useful if both axes are defined precisely. Left undefined, everyone puts their favourite projects in the top right.

AxisWhat it measures exactly
Impact Hours per year it frees, plus the cost of the errors it prevents. In numbers, not adjectives
Effort Number of systems to connect, number of known exceptions and whether the process has to be tidied first

With those two axes properly set, something uncomfortable usually appears: the highest-impact processes are nearly all in the high-effort zone. That is why the first project is not chosen for maximum impact but for the best impact-to-effort ratio in the low-effort quadrant.

3Three good first candidates in almost any business

📥
Filing the documents that arrive
Saving, renaming and placing whatever comes in by email. Very high frequency, stable rules, cheap errors and nobody defends it as their territory. It is the classic first project.
🔔
Alerts that depend on someone remembering
Due dates, renewals, expiries, follow-ups. The impact is not hours saved but problems avoided, and that shows quickly.
📊
The recurring report
The one someone assembles every Monday by copying from two places. Stable rules by definition, with the advantage that the result can be compared against the manual version to verify it. How to tackle it is covered in our guide to automating reports from ERP, CRM and Excel.

4Four traps when choosing

  • The process that is about to disappear. Before investing, ask whether that system is being replaced next year or whether a rule change is about to reshape the workflow.
  • The one the boss asked for. It may be the right one, but score it with the same criteria as the rest. If it comes out badly, that conversation is easier before than after.
  • The one nobody wants to touch. Sometimes the reason is technical and sometimes it is political. If it is the second, the tool will not solve it.
  • The one that only exists in one person's head. Tempting because the saving looks huge, but if it is undocumented it has to be documented first, and that is another task.
There is a fifth trap worth its own mention: automating something that should simply stop being done. Before optimising a report, ask who reads it. The answer sometimes turns a two-week project into a two-minute decision.

5How to score it in an afternoon

No methodology required. A table with the candidate processes and five columns will do, scoring each criterion from one to three.

What gives the exercise its value is not the final score but the conversations it triggers. The frequency column forces measuring instead of estimating. The stability column reveals that two people do the same process differently. And the "who decides" column discovers, more often than you would expect, that nobody owns that workflow.

01
Count, do not estimate
"Lots of times a month" is not good enough. Count the emails, rows or documents from one real month. The figure usually surprises in both directions.
02
Time it once
Have someone do the task with a stopwatch. Perceived and actual time differ quite a bit, and you need the actual one to prove the improvement later.
03
Ask about the exceptions
"When is it not done this way?" is the question that reveals the real effort. If the answer takes a while to arrive, the process is more variable than it looked.
04
Write down the baseline
Volume, minutes per unit, error rate and cycle time in days, noted before touching anything. Without that you will not be able to show it worked.

6Why the first one should be small

The first project is not chosen to maximise savings. It is chosen to prove this works and that the team adopts it, which are the two real unknowns. A small, stable, visible process answers both within weeks.

And there is a side effect worth more than the saving: when someone sees their repetitive task disappear, they start pointing at others. The best inventory of automatable processes does not come from a consultancy, it comes from the team after the first success.

MethodPrioritisationAutomation

Frequently asked questions

Where do I start with twenty candidate processes?

By scoring them against five criteria: frequency times unit time, stability of the rules, quality of the input data, cost of error, and whether an identifiable person suffers it. That reduces twenty candidates to three or four in an afternoon, and the conversation the exercise triggers is usually worth more than the score.

Should I start with the process that consumes the most time?

Not necessarily, and it is usually a bad idea. The most time-consuming process tends to also be the most complex and the one with the most exceptions. For a first project you want a good impact-to-effort ratio, something that shows results in weeks and builds the confidence to tackle the big one afterwards.

What if the process is not defined?

Define it first, which is business work rather than technical work. If everyone does it differently, automating only makes the disorder circulate faster. Sometimes that definition exercise already solves half the problem without touching any tool.

How do I know it is worth it before spending?

With the baseline: count one real month's volume, time the task once and note the error rate. With those three numbers and a quote, the return can be calculated without guessing. How to do that honestly is in process automation ROI.

What if the process disappears within a year?

Then it rarely pays off, unless the saving in that year already covers the investment. It is a question to ask explicitly when choosing: if the system is being replaced or a rule change will reshape the workflow, that candidate drops to the bottom of the list however painful it is today.

In short

There are five criteria and the most predictive is rule stability, not volume. A frequent but shifting process produces a flow that needs endless tweaking; a stable, boring one produces savings for years.

And the first project is chosen for something else: to prove quickly that it works and that the team adopts it. After that first success, the team itself points at the next candidates better than any analysis. That is how we approach AI process automation.

Several processes and no idea which to tackle?

We score them with you against the five criteria, measure the baseline of the two or three finalists and tell you which one shows results soonest. No obligation.

Request a process analysis