Time blocking gives each task a slot in your calendar, with a start and an end. Book the block for your most important goal before the week’s invitations arrive, and size it from the task’s steps: a block sized from a task’s name runs over.
What to block first
A to-do list says what you will do. A block also says when. People who decide in advance when and where they will act on a goal reach it more often than people who only intend to (Gollwitzer and Sheeran, 2006). In a 2013 post, Cal Newport, the author of Deep Work, estimates that a 40-hour time-blocked week gets as much done as 60 or more hours without structure. It is his own estimate, with no data behind it.
So the first block goes to the task that moves the most important of your goals for the year, for 90 minutes to two hours at the time of day you think best. If you are unsure which task that is, sort your list with the Eisenhower matrix: the important work nobody is chasing is the work a block protects.
Meetings are blocks already, set by other people, and they cluster: in Microsoft’s 2025 data on Microsoft 365 use, half of all meetings fell between 9 and 11 am or between 1 and 3 pm. If those are your best hours, book the goal block before the invitations take them, and batch email and short replies after it.
Put one task in each block, named so you know when it is done: “Work on the launch” fills any slot you give it, and “QA pass on Android” ends with the pass. Unfinished work follows you: in two experiments by Sophie Leroy, people who switched away from an unfinished task kept thinking about it and did worse on the next one.
Plan the week ahead, the day the evening before
Place the week’s goal blocks before the invitations arrive: each priority from your weekly plan gets at least one long block. A block that is always at 9:00 is easier to defend, for you and for whoever books your calendar.
Then spend ten minutes each evening on tomorrow: check which meetings were added and move the blocks around them. Book breaks and a stop time too: a day with no end lets overruns spill into the evening, and the open hour should catch them first. If your goals live in FocusPilot, each task carries a start time and a length and sits under the goal it serves, so tomorrow’s blocks are already a view of your goals (how to set it up).
A block sized from the task’s name runs over
People tend to underestimate how long their own tasks will take, even when similar tasks ran late before (Buehler, Griffin and Ross, 1994). In five experiments by Kruger and Evans, people who first listed a task’s parts, from holiday shopping to formatting a document, gave longer estimates than people who judged it whole, and closer to the time the tasks really took, most of all on complex tasks.
The goal block is the most complex task in your day, so unpack it: write its steps inside the block, each with its minutes, and make the block as long as their sum. Listing finds the parts you forgot. It cannot find the call that interrupts you, so keep one open hour in the afternoon too.
My own example is a landing page and onboarding update. I expected 2 hours, and had not thought of the copy, mobile QA, edge cases or the feedback rounds with my co-founder. AI sped up the first draft a lot, but review and polish still took about 5-6 hours in total.
When a block is interrupted, note where the task stopped and move the rest to the next open slot. Dropping a goal block is a decision, and it belongs in your review.
A worked example
Ada, the account we use for demos, leads product at a fintech company. Her most important task that week was the QA pass on Android for the new onboarding flow, and on Wednesday evening she listed its steps before she gave it a length:
- Install the beta build and run sign-up on the test phone: 30 minutes
- Check every onboarding screen on a small and a large phone: 60 minutes
- Log the bugs and retest the blockers: 30 minutes
Two hours, so it went into Thursday at 9:00, before anything else, and the rest of the day fitted around it.
Thursday, 15 October
- QA pass on Android2 hGoal: Ship the new onboarding flow9:00 to 11:00, goal block
- Partner meeting prep with Jonas45 min11:00 to 11:45
- Lunch and email2 h 15 min11:45 to 14:00, left open
- Northwind partner meeting1 h14:00 to 15:00
- Open for overruns1 h15:00 to 16:00, left open
- Get budget sign-off from Lena30 min16:00 to 16:30
- Sign off the final designs30 min17:30 to 18:00
At 9:40 a payment bug in production pulled her into a call until 10:20. She noted where the QA pass had stopped, went back to it after the call, and kept the 11:00 prep because Jonas was booked for it. The 40 lost minutes went into the open hour at 15:00, and by six every block had happened, the QA pass in two parts.
Example data from a demo account. Names and numbers are illustrative.
Review what held
At the end of each day, take two minutes: which blocks held, which moved, and why? Not sure of your best hours? Add one question: when did the goal block go best? At the end of the week, look at the goal blocks together. A block that keeps moving is a finding: usually a meeting that always lands in that slot, or a task bigger than its block.
Over my last four weeks I planned about 80 blocks. Roughly 50 held, 20 moved and 10 were dropped, and the moves usually happened when a founder task or a deadline jumped the queue. The one that kept moving was “Admin and email cleanup”, because it never feels urgent. It turned out to be a pile of small repetitive tasks, so I automated the recurring ones (email triage and drafts, meeting notes, follow-ups) and batched the rest into 15-minute slots.
After a few weeks your notes show how long your goal tasks really take and when they go best: size and place the next blocks from them.
Template
This week’s priorities (from your weekly plan)
Goal blocks for the week (day, time, task, the goal it serves)
Tomorrow, planned the evening before
- First block, your most important task, from ___ to ___:
- Its steps, each with its minutes (the block’s length is their sum):
- Meetings already booked:
- Small tasks and email, in one batch, from ___ to ___:
- Open time for overruns, from ___ to ___:
- Stop time:
When a block is interrupted
- Where the task stopped:
- The open slot it moves to today:
Before you close the day
- Which blocks held as planned?
- Which moved, and why?
- When did the goal block go best?
- What goes in tomorrow’s first block?
Where time blocking falls short
A full block plan assumes most of your day is yours to arrange. In support, on-call or sales-floor roles it is not, so book one protected block a day and leave the rest open. A block also cannot stop a call that never had an invite: in the same Microsoft data, 57 percent of meetings among the fifth of users with the most meetings were ad hoc calls.
If a reserved slot does not fit your work, a related method may. Here are the four that get mixed up, on Ada’s Thursday:
- Time blocking fixes when: the QA pass owns 9:00 to 11:00.
- Timeboxing fixes how long: two hours for the QA pass, wherever they land.
- Task batching groups small work of one kind: her email, in one slot.
- Day theming gives a weekday one kind of work: every partner meeting on a Thursday.
A blocked day usually uses all four.
You do not need an app for any of this. A paper planner with an hour column does the whole method. Google Calendar’s focus time events decline meetings booked over them, on work and school accounts. Sunsama is built around a daily planning routine and lets you timebox tasks on your calendar.
Time block your day in FocusPilot
FocusPilot keeps each block under the goal it serves.
- Add the goal block as a task under the goal it moves. Every goal sits in an area: Professional, Personal or Health.
- Give the task a day, a start time and a length. Ada’s: Thursday, 9:00, two hours.
- On the Goals tab, tap ⋯, then Display, and choose the Calendar layout.
- In the morning, open Today’s Read from the + button. It reads how much the day can hold, and Plan My Day turns that into a plan for the day.
- At the end of the week, the weekly review (Goals, ⋯, Weekly review) shows what closed and which tasks kept slipping.
FocusPilot is free to download on iPhone and Android, and every plan starts with a free trial.
FocusPilotiPhone and Android
We make FocusPilot. The method above works without it.
The bottom line
Time blocking works when at least one block a day is yours to protect, and in a reactive role one block is enough: book it and batch the rest. Tonight, list the steps of tomorrow’s first block and give it the length they add up to.
