The original is one click away. Open original ↗
Why busyness is the enemy of good knowledge work
Executive overview
Knowledge work defaulted to pseudo-productivity — visible activity as a proxy for productive effort. Email, Slack, and smartphones made this unbearable: constant context-switching and performative busyness crowded out the actual work.
Slow productivity offers an alternative: do fewer things at once, work at a natural pace, and obsess over quality. These three principles are mutually reinforcing — quality obsession makes the other two inevitable.
The biggest lever in knowledge work is reducing the number of active commitments, not optimising how you handle them.
Why pseudo-productivity broke down
- Pre-IT, visible activity was a rough-and-ready proxy for output — uncomfortable but manageable
- Mobile computing and email enabled granular, always-on demonstration of activity at every hour
- Result: performative busyness exploded while actual progress slowed
- The pandemic pushed already-overloaded workers past the red line: ~20% more tasks overnight, plus ad-hoc conversations inflated into 30-minute Zoom blocks (Microsoft data: 252% increase in meetings 2020–present)
- Quiet quitting, the Great Resignation, and remote-work wars were all symptoms of the same underlying overload
The mechanics of overload
- Every commitment brings administrative overhead — emails, meetings, coordination
- Most workers manage workload via stress: keep saying yes until distress outweighs the social cost of no
- This heuristic keeps workload perpetually at the red line
- A diverse inbox is cognitively devastating: each email represents a separate attention frame; rapid switching prevents the brain from ever fully loading the right context
- Doing fewer things at once actually speeds completion — less overhead, longer focus blocks, higher quality output
Making workload visible
- The root enabler of overload is that nobody talks about their workload — everyone is treated as an execution vessel
- Break this by maintaining a transparent list: actively working on vs. queued, with order
- When asked to take on something new, show the list and let the requester see where it lands
- Alternatively, schedule every project on the calendar before accepting it — forces a realistic confrontation with available time
- Both approaches earn a reputation for reliability, not for being difficult
- Reducing commitments by ~25% is rarely noticed by others but can transform your experience of work
Obsessing over quality as the flywheel
- Quality obsession makes busyness intolerable — the two are incompatible, so the motivation to simplify becomes internal
- Literary novelists and elite programmers are left alone because their output is unambiguously measurable; most knowledge workers have the same leverage but it is obscured
- Delivering exceptional work creates asymmetric leverage: employers are far more scared of losing a high performer than they let on
- Accountability (measured output) can be traded for accessibility (freedom from meetings and constant messaging)
- The flywheel: doing fewer things → higher quality output → more autonomy → even easier to simplify
Working at a natural pace
- Entrepreneurs have the most flexibility to experiment with non-standard schedules (seasonal work, two months off in summer)
- Even salaried workers can make the trade: ~20% less income for dramatically reduced hours is often a better deal than it first appears
- Project timelines should be doubled — humans systematically underestimate time needed, and artificial deadlines produce disappointment, not speed
- Rituals and fixed environments help route specific types of work, reducing startup friction
More like this — when you're ready for early access.
Join the waitlist for a personal account and content recommendations based on what you're working on.
No spam. Unsubscribe at any time.
You're on the list. We'll be in touch before launch.