Practical guide
A practical way to choose your first automation project
A lightweight prioritisation method balancing frequency, clarity, risk and business usefulness.
By Eleva Solutions5 min readWeek beginning Monday: 17 August 2026
Avoid choosing only by frustration
The loudest complaint may involve a complex process with unclear rules and many exceptions. That can be a poor place to learn how automation will be owned and supported.
Compare candidates using the same simple questions so urgency does not hide delivery risk.
Balance four factors
Rate each process as low, medium or high. The goal is not a mathematical score; it is a clearer conversation about trade-offs.
- Frequency: how often does the process occur?
- Clarity: how stable are the normal rules and outcome?
- Usefulness: who benefits and what becomes easier to manage?
- Risk: what happens if information or automation is wrong?
Design a bounded first release
Choose one trigger, one normal path and one clear result. Keep unusual exceptions visible for a person to handle until their pattern is understood.
A bounded release makes it possible to verify whether the improvement fits the business before expanding it.