Overpacked blocks
Back-to-back dense blocks collapse with a single interruption.
MethodFailure FixTime Blocking
Reduce Time-Blocking Failures
A practical guide to diagnose why blocks fail and rebuild a recoverable plan for the next day.
Failure Patterns to Check First
Treat failure as a system issue first. Start with these three checks.
Oversized task units
Multiple outcomes inside one block raise startup friction.
Ignoring energy pattern
Hard tasks scheduled in low-energy hours fail more often.
Recovery Routine
Ten minutes at night or next morning is enough to recover effectively.
- STEP 1
Tag three failed blocks
Analyze only the latest three failures to detect repeat patterns quickly.
- Use tags: scope/interruption/energy
- Record facts, not self-judgment
- STEP 2
Cut block size in half
If 2-hour blocks keep failing, split them into 50-60 minute units with buffers.
- Fix a 10-15 minute buffer between focus blocks
- Keep daily core blocks between 2 and 4
- STEP 3
Retry next day
Do not delete failed work. Re-schedule a smaller version and regain momentum.
- Compare same-slot retry vs different-slot retry
- Keep only successful structures as templates
Screens Used for Recovery
Use these screens to move from block diagnosis to carry-over recovery.
Common Mistakes
- Reducing all failures to 'motivation issue'
- Deleting failed blocks and losing pattern data
- Treating deep-work blocks like meeting blocks
Recovery Steps
- Tag causes into scope/interruption/energy.
- Retry the same work in half-size blocks first.
- Separate meeting/communication blocks from deep-work blocks.