Automation makes activity easy to scale
A business can generate more emails, reports, notifications and task updates with little marginal effort. The resulting activity looks efficient because machines performed it quickly.
But recipients still spend attention. Systems still need data, permissions, monitoring and maintenance. Faster production of unnecessary work increases the burden.
More automation can mean worse work
| More automation | Better work |
|---|---|
| More messages sent | Fewer, relevant actions understood |
| More reports delivered | Better decisions with owned evidence |
| More tasks created | Necessary work completed |
| More systems connected | Less duplicate entry and clearer truth |
| Less manual action | Appropriate human judgment at the right point |
Ask whether the outcome improved
- Did cycle time fall without reducing quality?
- Were errors and rework reduced?
- Did customers or colleagues face less friction?
- Was useful capacity released?
- Did maintenance and exception work remain acceptable?
- Would removing the step create more value than automating it?
The argument is not against automation. It is for starting with the workflow map and ending with evidence of better work.
Apply the idea to one real workflow
Choose one current workflow. Record the present outcome, the proposed change, the accountable owner, the most important exception or failure, and one before-and-after measure. Test the smallest safe version before expanding it.
Sources & further reading
- Measuring Productivity: OECD Manual
OECD. Official measurement guidance relating outputs to production inputs. Business teams still need quality, customer and outcome measures rather than treating activity volume as value.
- Measuring the benefits of your service
GOV.UK Service Manual. Guidance connecting time, cost and service measures to outcomes and benefits. It does not provide universal automation ROI assumptions.
- Map and understand a user's whole problem
GOV.UK Service Manual. Public-service guidance on mapping journeys, collaborating across boundaries and locating pain points. The module adapts the method to business workflows.
Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.
A correction, a counterexample or an experience worth sharing?
Join the conversation ↗