Dev.to
7/11/2026

Time-blocking mostly failed me. Two pieces of it saved my week anyway.
Short summary
A writer tried full time-blocking for a month and found it collapsed under interruptions, energy dips, and guilt from missed blocks. Two pieces survived: one protected 9–11am drafting block treated as a container rather than a deadline, and batching email/Slack/admin into two daily windows. The simplified approach stuck for nearly a year.
- •Full time-blocking failed due to interruptions, energy mismatch, and guilt from missed blocks
- •One protected morning drafting block survived — treated as a container, not a deadline
- •Batching shallow work into two daily windows made it faster and eliminated constant context-switching
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



