The difference between automation and displacement
Many efficiency gains move work rather than remove it. How to tell the two apart before investing.
When a step is automated, it rarely disappears entirely. It changes its form, its location and the person who performs it. Whether effort has been saved or merely moved determines the economics — and is seldom examined separately.
Three forms of displacement
The first is temporal: effort leaves day-to-day operation and reappears in setup and maintenance. That can be worthwhile, but it is a different calculation from a saving.
The second is organisational: effort leaves one department and appears in another, frequently in IT or quality assurance. From the first department's point of view that is a success; from the company's, possibly not.
The third is the most uncomfortable: effort leaves the business and appears with the customer, who now completes forms or reports faults themselves. That displacement shows up in no internal measure at all.
The test
A workable test is to look at the whole process from end to end and ask how many person-hours it costs in total — before and after, across everyone involved, including those outside your own area.
If that total falls, it is automation. If it stays the same and merely redistributes, it is displacement. Either can be sensible; only the first justifies the investment on efficiency grounds.
Why the distinction gets lost
It gets lost because measures are collected along departmental boundaries, and displacement happens precisely at those boundaries. Measure the process across the boundary and you see it; measure within one and you see a success.