Your team got faster tools. What happened to the time?
What happens when saved time becomes another request?
An automated report still needs checking. A faster draft still needs a decision. What changed in the workload when you changed the tools?
What is going on
Jevons Paradox
The cheaper a process becomes, the more of it the organisation commissions.
Jevons described increased coal use alongside efficiency gains. Applying that idea to office work is an analogy: if faster reporting leads to more reports being requested, the saved effort can be absorbed by new demand.
→Plan for demand to rise when you remove effort. Unplanned, that rise lands on individuals as unpaid overhead.
Work Expands To Fill Cognitive Bandwidth
When one layer of difficulty disappears, the ceiling rises rather than the floor.
Parkinson’s Law applied to attention rather than to time. Removing the straightforward part of a role does not create breathing room inside it. It hands the same person a harder problem, usually without a rewrite of the job description or the grade.
→Automation promotes people. Job design, workload models and grading rarely get rewritten to match, so the promotion is invisible except in how tired everyone is.
Cognitive Load Shifting
Automation changes the type of thinking required, not the amount.
When a tool takes over execution, the human keeps designing the system, checking the output, catching what the tool missed, and switching between the six places the work now lives. That is a different kind of load, and a more expensive one.
→The load moved from execution to orchestration. Orchestration runs on executive function, which is exactly the resource that fluctuates in ADHD, autism and chronic illness.
The Automation Paradox
The more you automate, the more demanding the remaining human role becomes.
Machines absorb the predictable work. What is left for people is ambiguity: the edge cases, the judgement calls, the integration between systems, the conversations that go wrong. The residue of automation is the hardest part of the original job.
→You have concentrated the hardest work into fewer hands. Check whether the support around those hands was concentrated too.
Complexity Inflation
Tools cut the effort per task. Expectations rise to absorb the saving.
Your competitors bought the same tools in the same quarter, so the standard lifts for everyone at once. Output per person rises and the baseline recalibrates upward behind it, which is why the saving never shows up as time.
→The sense of running to stand still is a structural fact about the work. A structural fact needs a structural response, which is why resilience training reads as an insult to the people receiving it.
What this could mean in practice
What to do about it
Treat cognitive load as a planning input, the way you already treat headcount.
Time matters, and so does the effort of making decisions and switching between them. Look at meeting load, interruptions and recovery space alongside hours. Ask employees what those demands cost them.
"We need to manage how much high context work sits in one person’s week"
Work, admin, emotional labour and life all draw on one executive function budget. Adding to any of them spends the same account.
Recovery time between demanding pieces of work is a scheduling decision rather than a wellbeing nicety. It determines whether the next piece lands well.
Capacity aware planning is an operational control. Choosing the rhythm of a week deliberately is a management skill, and it can be taught.
Before adding another tool, look at the decisions, interruptions and recovery time in a real working day.