The best first automation is not the process people complain about most. It is the smallest repeatable flow with enough volume, measurable cost and clean ownership to prove the system works.
What makes a process a strong automation candidate?
Frequency, consistency, measurable effort and clear ownership matter more than headline size.
A process that runs every day compounds small savings quickly. A process that runs twice a year may be painful, but it rarely produces a useful first system.
Look for work where the same information is copied, checked, transformed or routed repeatedly.
- High transaction frequency
- Stable inputs and outputs
- Visible time or error cost
- One accountable process owner
- A result that can be measured within weeks
Avoid automating organisational confusion
Automation scales the process you give it, including its ambiguity and waste.
If teams disagree about ownership, rules or the definition of completion, engineering will not solve the underlying operating problem. Clarify the process first, then encode it.
Do not automate a process that nobody can explain end to end.
PROMTURE discovery rule
Score before you build
A simple score prevents urgency and internal politics from deciding the roadmap.
Rate frequency, manual effort, error impact, data readiness and implementation risk from one to five. Start where value is high and dependency risk is low.