Why lists fail and blocks work

Twelve items on a list compete for one afternoon. Your brain picks the easiest — email, organizing, buying stationery. Time blocking forces a trade: if this hour is for the essay, it is not for Slack. The calendar becomes a contract with yourself, witnessed by Future You who will otherwise be tired and suggest "tomorrow."

Block types worth naming

Block typeDurationRule
Deep work45–90 minOne hard task, phone away
Shallow admin30 minBatch email, forms, scheduling
Learning / review30–60 minRetrieval, not rereading
Buffer15–30 minSpillover, walk, reset
OffAs neededProtected — not "catch-up in disguise"

Sunday reset (twenty minutes)

  1. Scan syllabus and inbox for the week's fixed commitments.
  2. Name three outcomes that would make the week successful.
  3. Place deep blocks before anything optional fills the gaps.
  4. Add one buffer block per day — non-negotiable.
  5. Share calendar with accountability partner if deadlines slip often.
Try Streakly

Make blocked habits visible

Time blocks work better when show-up streaks reinforce them. Streakly logs daily starts — the habit behind the calendar.

View on App Store →
Try Revu

Block review time, not just study time

Every learning block should spawn a review block. Revu schedules the return visit so blocked study time actually compounds.

View on App Store →

When blocks break (they will)

Meetings run long. You get sick. A problem set takes twice the estimate. The fix is not abandoning time blocking — it is rescheduling visibly. Drag the block to tomorrow. Shrink it. Split it. A calendar you never update becomes fiction.

Anti-patterns to avoid

  • Blocking every minute — no room to breathe guarantees collapse.
  • Vague block titles ("study") — write the outcome ("finish problem set 4, problems 1–6").
  • Scheduling deep work at your low-energy hour because it "looks free."
  • Treating missed blocks as moral failure instead of data.
A time-blocked day is a hypothesis. The weekly review is where you learn what was true.