Block recovered time for priority work immediately — unallocated recovered time fills with low-value activities within weeks
Immediately block recovered time on your calendar for specific priority work before recovering it—recovery without preallocation creates a vacuum that entropy fills with new low-value activities within weeks.
Why This Is a Rule
Eliminating a time-wasting activity (canceling a useless meeting, automating a manual process, dropping a commitment) creates free time. But free time without preallocation is a vacuum — and vacuums fill. Within days, the recovered 2 hours per week will be consumed by email expansion, longer lunch breaks, social media, new low-value commitments that "seem quick," or simply unstructured drift. Two weeks later, you can't identify where the recovered time went, and your schedule feels as full as before the optimization.
The mechanism is Parkinson's Law applied to time recovery: work (and non-work) expands to fill the time available. If recovered time isn't immediately designated for specific priority work, it gets absorbed by the existing activity set expanding to fill it. The solution is preallocation: before you eliminate the time-wasting activity, decide what the recovered time will be used for and block it on your calendar with the same commitment level as an external meeting.
The "immediately" constraint is critical. Each day that passes between recovery and allocation increases the probability that the time gets consumed by entropy. Block the time on the same day you recover it — ideally in the same action (cancel meeting → create deep work block in its place).
When This Fires
- When eliminating a recurring meeting or commitment
- When automating or delegating a task that previously consumed your time
- When optimizing your schedule and "freeing up" blocks
- Complements Consolidate meetings into 1-2 designated days — meeting distribution destroys more capacity than meeting duration (meeting consolidation) and Replace status-update meetings with async written updates — synchronous time is for coordination and decisions, not information transfer (async status updates) by ensuring recovered time produces value
Common Failure Mode
Celebrating time recovery without protecting it: "Great, I eliminated 3 hours of meetings this week!" Three weeks later, those hours are invisible — consumed by longer email sessions, new ad-hoc meetings, and general schedule inflation. The recovery produced zero net productivity gain because the time was never allocated to anything specific.
The Protocol
(1) Before eliminating a time commitment, decide what the recovered time will be used for. Choose a specific priority: deep work on project X, skill development, strategic thinking, etc. (2) In the same action as the elimination, create a calendar block for the replacement activity. If you're canceling a Tuesday 10-11am meeting, immediately block Tuesday 10-11am for "[Priority work]." (3) Protect the new block with the same rigor as the old commitment. It's not "free time" — it's allocated priority time. (4) If you can't identify a specific priority use for the recovered time, that's a signal that your priorities aren't clear enough. Clarify priorities before optimizing time. (5) Review after one month: is the recovered time actually being used for the allocated priority? If not, either the block isn't being protected or the allocation was wrong.