What time blocking actually is
A to-do list answers "what needs to be done?" A calendar answers "where do I have to be?" Time blocking answers the question between them: "what will I be doing at 10:15?" You divide the day into blocks - usually thirty minutes to two hours - and assign each block one job: a piece of focused work, a batch of small tasks, a meal, a commute, a rest.
The defining move is that everything gets a block, not just meetings. Deep work gets a block. Email gets a block instead of leaking into every gap. Lunch gets a block so it stops being the thing that gets skipped. When the day is fully allocated, "what should I do now?" always has an answer, and the answer was chosen calmly the night before rather than under pressure at 10:14.
Why it works when lists do not
A list has no capacity limit. It will happily accept forty items on a day with room for six, and it lets you feel productive by doing the three easiest. The pile does the choosing.
A day is a fixed container. The moment you place work into hours, you are forced to confront capacity: there are only so many blocks, so putting one thing in pushes another thing out. That collision - painful the first few times - is the entire value. Prioritization stops being an abstract ranking exercise and becomes a concrete question: which of these two things gets Tuesday morning?
Blocking also moves decisions to when you are good at them. Deciding at 9 PM what tomorrow’s deep work will be costs little; deciding at 9 AM, cold, with a full inbox, costs the best hour of the day. And a block is a commitment to one thing at a time - a structural defence against the constant low-grade switching that fragments unstructured days.
Step 1: Find the fixed points
Start with the parts of the day that are not up for negotiation: sleep, meals, commute, standing meetings, school pickup, training sessions. Put them in first. What remains is your actual discretionary time - usually a smaller number than it feels like, and seeing that number honestly is the first correction time blocking makes.
These fixed points are also your anchors. A day with a firm 12:30 lunch and a firm 5:30 shutdown has natural walls to build against; a day that is one undifferentiated slab from waking to midnight gives your blocks nothing to hold on to.
Step 2: Place the blocks that matter most, first
With the anchors in place, add blocks in order of importance, not in order of time. The one or two blocks of demanding, high-value work go in first, and they go at the hours when you are actually sharp - which you may only discover honestly after a couple of weeks of tracking. Everything else fits around them.
Then batch the shallow work. Email, messages, admin and errands go into one or two dedicated blocks rather than being sprinkled through the day. A "small stuff" block at 11:30 and another at 4:00 will absorb an astonishing amount of what used to interrupt your mornings.
- Deep work blocks: 60-120 minutes. Longer than two hours rarely survives.
- Shallow batches: 30-45 minutes, placed after deep work, never before.
- Breaks and meals: real blocks, not gaps. Unblocked breaks get eaten.
- Buffers: 10-15 minutes between consecutive commitments. Days without buffers fail by noon.
Step 3: Size blocks with evidence, not hope
The fastest way to abandon time blocking is to build a day out of best-case estimates. If a report has never once taken you less than three hours, a ninety-minute block for it is not a plan - it is a wish with a border around it, and by 11 AM the whole day behind it has collapsed.
Until you have real data on yourself, use a blunt rule: take your instinctive estimate for any open-ended work and add half again. Then, as you start comparing planned days against real ones, replace the blanket rule with your actual multipliers - most people discover their estimates for creative work run low by a consistent, correctable factor. Sizing from your own history is what eventually makes the plan trustworthy.
Step 4: Run the day without worshipping the plan
The plan will break. Someone calls, a task overruns, energy dips. This is not failure; it is the medium. The skill is in the response: when a block breaks, you move blocks - drag the afternoon around, shrink something, push something to tomorrow - rather than abandoning the schedule and free-falling through the rest of the day.
A useful mental posture: the plan is a default, not a contract. At any moment you either follow the current block or make a deliberate decision to change it. What you never do is drift - the state where no decision was made and the hours simply go missing.
Step 5: Close the loop
This is the step most time-blocking advice skips, and it is the one that makes the habit permanent. At the end of the day - or the week - put the plan next to what actually happened. Which blocks started late? Which ran over, and by how much? Which never happened at all? What consumed time that was never on the plan?
Without this comparison, your blocks stay fictional forever and the daily failure slowly convinces you that "time blocking doesn’t work for me." With it, next week’s blocks inherit this week’s lessons: the 9:00 start becomes 9:30 because that is when you actually start; the writing block doubles because writing always doubles. The plan converges on reality, and a plan that matches reality is one you can finally trust.
The failure modes to avoid
Almost everyone who quits time blocking quits for one of a handful of preventable reasons.
- Blocking every minute. A day scheduled to 100% capacity fails on first contact. Leave slack - aim to allocate roughly 70-80% of your discretionary time.
- No buffers. Back-to-back blocks assume teleportation and instant context switches. Fifteen unglamorous minutes between blocks keep the whole chain alive.
- Rebuilding from scratch daily. If you re-create the same morning routine block by block every evening, you will stop within two weeks. Routines should repeat automatically; you should only plan the exceptions.
- Treating drift as a character flaw. A block that never holds is a data point about the block - wrong size, wrong hour - not about your discipline. Fix the block.
- Planning without reviewing. Write-only time blocking decays into fiction. The comparison step is not optional; it is the mechanism.
Key takeaways
- Give every hour a job, chosen the night before - including breaks and shallow work.
- Place fixed points first, then the most important deep work at your genuinely best hours.
- Size blocks from your own history, not best-case estimates; until you have history, add half again.
- When the day breaks, move blocks deliberately - never drift.
- Compare the plan with what actually happened; that loop is what makes the blocks realistic over time.
Doing this in Fezer
Fezer was built around exactly this loop. The Schedule tab is the day timeline: blocks are draggable, deadlines pin to the day, and repeating blocks - daily, weekdays, weekly or biweekly - carry your standing structure forward so you only ever plan the exceptions. The Now view holds up the current block so "follow or deliberately change" stays a one-glance decision.
The review step is native rather than a spreadsheet you have to maintain: Track mode records real sessions with one tap, and Compare mode draws the planned day and the tracked day side by side on the same hours. Everything stays on your device - no account, no cloud, free.