How to run an automation opportunity assessment

"We should be automating more" is a sentiment heard in almost every operations conversation. It is usually true, and usually unhelpful — because without a structured way to decide what to automate, organisations either automate nothing or automate whatever a vocal team happens to nominate. An automation opportunity assessment replaces that lottery with a repeatable method.

Start with a structured inventory

The first step is building an inventory of candidate processes across the functions in scope. This does not require months of analysis; a disciplined series of interviews and data pulls can produce a credible inventory in weeks. For each candidate, capture the essentials: transaction volumes, team effort consumed, systems involved, and the nature of the work.

Score candidates against consistent criteria

Every candidate should be scored against the same set of criteria. The ones worth weighting most heavily:

• Rule-based content — how much of the process follows definable rules versus judgement.
• Volume and frequency — enough throughput to justify build and maintenance effort.
• Process stability — processes about to change with a new system are poor near-term candidates.
• Input data quality — automation amplifies whatever data it is fed.
• System accessibility — whether the underlying applications expose APIs or require fragile surface-level automation.

Scoring forces useful conversations. A process everyone assumed was ideal for automation often turns out to be judgement-heavy; an unglamorous reconciliation task turns out to be the strongest case in the portfolio.

Build a value-and-effort matrix

Plotting scored candidates on a value-versus-effort matrix makes the roadmap almost self-evident. High-value, low-effort candidates form the first wave and fund credibility for the programme. High-value, high-effort candidates need proper business cases and often pair automation with process redesign. Low-value candidates are documented and deliberately parked — an explicit "not now" list prevents the same debates from recurring every quarter.

From shortlist to pipeline

The output of a good assessment is not a report; it is a pipeline. Each shortlisted opportunity should carry an estimated benefit range, a complexity rating, dependencies, and a suggested sequence. An assessment across a single function typically surfaces more viable opportunities than any team can build at once — the strongest handful, sequenced deliberately, form a deliverable first wave.

Run this way, an opportunity assessment takes weeks, not quarters — and it converts automation from an aspiration into a managed portfolio with owners, sequence and expected returns.