Appetite vs Capacity for Work
Assume you are already at capacity, so budget every new commitment as a swap
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 6
- Confidence
- 78%
The model separates appetite for work from capacity for work, and observes that driven people habitually let the first exceed the second. The naive assumption when adding something new is that it will be funded by down-regulating sleep or up-regulating efficiency, with visible inefficiencies — a daily half-hour of YouTube, an idle evening — treated as free budget. Abdaal's point is that those pockets are not slack; they are the recovery that makes the existing load survivable, so they do not surrender. What actually gets displaced is the optional-looking category: time with friends and family, weekends, sleep. The corrective rule, credited to Chris Sparks, is that to pick something up you must put something down — so every addition is planned as an explicit swap. Williamson's own annual pre-Freshers-Week collapse illustrates the failure mode when it is ignored.
Origin
Discussed by Ali Abdaal and Chris Williamson on Deep Dive with Ali Abdaal, with the core rule attributed to Chris Sparks and illustrated by Williamson's yearly October breakdown after a month of relentless event build-up.
Core principles
- 01Driven people already operate close to their real capacity
- 02Adding without subtracting is a debt, not a plan
- 03Apparent slack is usually recovery, not waste
- 04What gets sacrificed silently is what mattered most
- 05Going hard until you snap is not a work protocol
How to run it
- 1
Separate appetite from capacity
Distinguish how much work you want to do from how much you can sustainably absorb. The gap between them is where burnout is generated.
- 2
Assume you are already near the ceiling
If you had spare capacity you would already be using it. Treat your present load as approximately your maximum rather than a baseline to build on.
Watch out Type A personalities systematically underestimate how loaded they already are.
- 3
Stop treating downtime as reclaimable
The idle half hour exists because you need a break from the work you are already doing. It is a function, not a leak.
Pro tip If you cannot say what a pocket of downtime is doing for you, observe it for a week before cutting it.
- 4
Name the thing you are putting down
For each new commitment, specify in advance which existing commitment ends. If you cannot name it, you are not adding the new thing, you are borrowing against recovery.
- 5
Fence the load-bearing categories
Mark sleep, close relationships and unstructured weekends as non-negotiable so they cannot become the silent funding source.
Watch out These are the first things to go precisely because nobody is chasing you for them.
- 6
Read your crashes as data
A predictable post-intensity collapse is evidence that appetite has been running ahead of capacity, not a personal failing to push through.
In the wild
Williamson describes a month of constant build-up every autumn: releasing event after event on social media, working the night itself, four or five hours of sleep, back to the office the next morning, cash the tills, handle the cancelled DJ, then do it again. Every year at the start of October he would end up in bed for a couple of days, unable to get up, wondering why he always felt that way afterwards. His conclusion is that going that hard until you snap is not a sustainable protocol and will not produce consistent results.
→ A repeating multi-day shutdown each October, recognised in hindsight as a capacity signal rather than depression.
Abdaal describes the standard reasoning of a driven person adding a new project: they spot thirty minutes a day spent on YouTube and plan to fund the new commitment from it. In practice that half hour is the decompression that makes the rest of the schedule tolerable, so it stays. The new work is instead funded out of weekends, sleep and time with friends — categories nobody defends because nobody is asking for them.
→ The new project ships while the unmonitored, high-value categories quietly erode.
Common mistakes
Funding new work from efficiency
Assuming you will simply become faster or sleep less to absorb an addition ignores that you are already operating near your ceiling.
Treating breaks as waste
Cutting the visible inefficiencies removes recovery capacity and accelerates the crash rather than creating room.
Calling the crash depression
Mislabelling a predictable post-intensity shutdown hides the structural cause and leaves the workload untouched.
Is it for you?
Best for
High-drive founders and creators who keep saying yes and cannot understand why they periodically collapse.
Not ideal for
People genuinely underloaded who need more commitments, not fewer.
From the transcript
“It's like having an appetite for work, which is bigger than your capacity for work.”
“in order to pick something up, you have to put something down”
“Because going so hard, you end up snapping is not a sustainable work protocol”
From the episode
How To Embrace Your Weirdness - Chris Williamson
Chris Williamson