Time-box tasks instead of scheduling by list
Assign each task a fixed time block on the calendar rather than a position on an open-ended to-do list.
Why it works
A to-do list is open-ended: items have no capacity constraint, so the list grows without limit and creates ongoing cognitive load. A time-boxed calendar is finite: you cannot schedule more than the available hours. This constraint forces prioritization at the planning stage rather than at the execution stage — when decision fatigue is higher. Time-boxing also pairs Parkinson’s Law containment with implementation intentions: the task has a specific when, which improves follow-through.
How to do it
- Translate your to-do list into calendar blocks, estimating how long each item will actually take.
- When the time block is full, stop working on the task — not by ignoring quality, but by accepting the output at that point.
- Review at day’s end: tasks that were genuinely incomplete deserve honest re-scheduling, not automatic carry-over.
Evidence
Time-boxing is a standard practice in agile software development and has practitioner endorsement across productivity frameworks. Implementation-intention research (when-and-where planning) supports the calendar-over-list format. Direct RCT comparisons between time-boxing and list-based planning for knowledge workers are sparse. (mechanistic)
The implementation-intention research supports the scheduling format; the Parkinson’s-Law mechanism for why time-boxing improves output is plausible but not directly isolated.
Sources
- Gollwitzer & Sheeran (2006), implementation intentions meta-analysis, Advances in Experimental Social Psychology
Common mistake
Creating a time-boxed calendar and then treating it as a list with time labels — allowing blocks to extend indefinitely, which reintroduces the expansion the structure was meant to prevent.
Practice this with IX Coach
More practices for Parkinson's Law, Made Practical
- Set deadlines shorter than you think you need
Assign a deadline that is tighter than comfortable — not unrealistic, but just tight enough to prevent scope creep.
- Define "done" before you start
Specify the minimum criteria for a complete output before beginning, so you have a clear stop condition.
- Default to shorter meeting lengths
Schedule 25- and 50-minute meetings instead of 30 and 60 — the meeting expands only as far as the slot allows.
- Deliberately underschedule your day to prevent expansion cascade
Leave 20–30% of your workday unscheduled as buffer for tasks that expand beyond their box.
- Work on one task per block to prevent multi-task expansion
Assign each time block a single task — multitasking within a block causes both tasks to expand while neither gets full attention.
Related concepts
- Deep Work, Made Practical
Focus blocks, attention residue, and the shutdown ritual — with the evidence
- Time Blocking, Made Practical
Calendar blocks, day theming, and the deep/shallow split — with the mechanisms
- Essentialism, Made Practical
Less but better — the disciplined pursuit of less, trade-offs, and the mechanisms
- The Pomodoro Technique, Made Practical
The 25/5 cycle, the real mechanisms, and an honest read on the evidence