Attention Is a Budget
What does an interruption cost after the interruption ends?
The idea
Every interruption creates switching cost and recovery time.
In the real world
A silent twenty-minute block beats an hour of fragmented work.
Going deeper
An interruption costs the interruption plus the reload of context afterwards, and the second is usually larger and entirely invisible. It is why four uninterrupted twenty-minute blocks outperform a fragmented hour.
The fragments also fail a threshold test. Work requiring held context needs a runway before it becomes productive, so pieces shorter than that runway produce almost nothing regardless of their total. This is why the number of interruptions matters more than the time they consume, and why protecting a contiguous block is different from protecting the same minutes scattered.
Where it stops applying
Not all work is context-heavy. Tasks that are genuinely modular suffer far less from fragmentation, and treating all time as needing protection wastes the flexibility.
Why it matters
The recovery time is invisible and usually larger than the interruption, so a fragmented hour is not an hour.
Try this today
Protect one distraction-free block.
Test yourself
Someone has four uninterrupted twenty-minute blocks and someone else has a full hour broken by six messages. Both spent similar time. Why is the second worse?
Show the answer
Each switch costs the reload of context on top of the interruption itself, so much of the hour goes to restarting. Attention behaves like a budget that switching spends, and the leftover fragments are too short to do the work that needed the hour.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.