Efficiency is not the only outcome
Automation can remove repetitive administration and make service more consistent, but it can also scale a poor rule or place friction in a moment that requires empathy. The right question is not whether a task can be automated, but whether it should be.
Map the task’s variability, consequence, reversibility, data sensitivity and emotional context. Stable, low-risk steps with clear inputs are stronger candidates than disputes, vulnerability, complex negotiation or decisions that materially affect a person.
Assess risk, variability and human need
Fix unclear policy before encoding it. If experienced staff routinely use judgement or work around the official process, automation will expose the inconsistency rather than solve it.
Use automation to prepare context, check completeness, route work and suggest actions while leaving accountable decisions with people where appropriate. Clearly identify automated interactions and make human help discoverable.
- Score tasks by consequence and predictability.
- Resolve policy ambiguity before implementation.
- Design visible handoff and override paths.
- Measure customer effort and recovery quality.
Design automation that supports people
Test with edge cases and people with different access needs, language confidence and digital ability. Monitor not only completion and cost, but abandonment, complaints, escalation and whether staff receive usable context.
Provide override, audit and rollback. A human-centred system allows customers and staff to recover when the model or rule is wrong instead of forcing them through the same failed loop.