Frequency and burden
How often does the work occur, how much attention does it consume and what downstream delay or cost does it create?
Loading...

A practical way to find repeated work that can be improved without encoding confusion, exceptions or poor ownership.
Why this check exists
Manual work is visible, which makes it an easy target. But repetition does not automatically make a workflow a good candidate for automation. The Automation Opportunity Check separates stable, costly movement from human work that still contains judgement, ambiguity or unresolved operating choices.
Which workflow to improve first, what must be clarified before automation and where people should remain in the loop.
Is this the right door?
You do not need all of these signals. One consequential uncertainty is enough reason to examine the decision more carefully.
Teams spend meaningful time copying, reconciling, routing or re-entering information.
A growing volume of work is creating delays, errors or dependence on extra headcount.
Automation ideas are multiplying but there is no shared way to prioritise them.
An existing automation is brittle because exceptions and ownership were never properly designed.
What the check examines
The check looks at the operating conditions around the decision—not just the technology being considered.
How often does the work occur, how much attention does it consume and what downstream delay or cost does it create?
Are the inputs, normal path and decision rules consistent enough to encode without hiding ambiguity?
How often does the workflow leave the normal path, why does that happen and who can resolve it?
Can an automated action be checked, explained and reversed before an error becomes consequential?
What you leave with
The first check is designed to improve the next move. It does not pretend to replace the deeper work that may follow.
A clear statement of the workflow, burden, value and automation boundary worth investigating.
The rules, ownership, information or process changes needed before technology should be introduced.
A bounded, observable candidate that can prove value without attempting to automate the entire operation at once.
What this is not
Bring the context you have. Zoe will help you frame the question, surface the assumptions and decide the most useful next move.