Efficiency Trap
Cap incoming work instead of optimising an endless supply
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 98%
The efficiency trap occurs when increased capacity attracts enough new work to consume the gain. Replying to email faster builds a reputation for responsiveness and produces more replies; writing articles quickly makes an editor bring the next assignment to the same journalist. The result is greater throughput but no greater freedom. Diagnose the loop by tracking what arrives after you become faster, then impose boundaries on intake and reserve capacity for the few priorities and relationships that matter. The mechanism resembles the demand-expansion idea Bartlett identifies with Parkinson's law, but Burkeman's focus is practical: no amount of speed reaches the end of an effectively infinite supply. Efficiency remains useful when it serves a bounded purpose rather than becoming the measure of self-worth or permission for unlimited work.
Origin
Extracted from The Diary of a CEO
Core principles
- 01Higher throughput can attract higher demand
- 02An infinite supply of work cannot be completed by moving faster
- 03Efficiency is useful only when bounded by priorities
- 04Saved capacity needs protection or it will be refilled
How to run it
- 1
Find the expansion loop
Identify an area where faster delivery has increased requests, expectations, meetings, or messages.
Pro tip Compare incoming volume before and after the efficiency gain.
- 2
Define enough
Set a practical limit for what you will process or accept instead of treating zero backlog as the only success state.
Watch out An unbounded inbox can always generate more work.
- 3
Protect reclaimed capacity
Assign saved time to meals, relationships, rest, thinking, or a selected priority before new demand fills it.
Pro tip Block the capacity before advertising greater availability.
- 4
Control intake
Decline, delay, or redirect work that exceeds the boundary even when you could technically process it.
Watch out Capability does not make every request a priority.
- 5
Judge the real result
Evaluate whether efficiency created space and better work, not merely a larger volume of completed tasks.
In the wild
As a young journalist, Burkeman became able to produce long, complicated articles quickly. Editors then knew whom to ask for the next fast assignment, which benefited his career but did not make him less busy.
→ Improved throughput increased demand instead of reducing workload.
Bartlett describes a reputation for handling an extremely dense meeting calendar. He then found nearly every minute of a 14-hour day scheduled, with no room for lunch or a message to his girlfriend.
→ Calendar efficiency displaced activities he said gave life meaning.
Common mistakes
Measuring throughput alone
More completed tasks can hide the fact that incoming demand and lost personal time grew faster.
Treating inbox zero as freedom
Rapid replies can trigger more replies and reinforce expectations of immediate availability.
Is it for you?
Best for
It is best for people whose quick replies, dense calendars, or rapid delivery generate more requests and expectations.
Not ideal for
It does not argue against all process improvement; it addresses efficiency pursued without a limit on incoming demand.
From the transcript
“more and more tasks like flood in to fill the excess capacity”
“it certainly didn't make me less busy”
From the episode
How To Finally Stop Procrastinating: Oliver Burkeman