Your to-do list has twenty items, your calendar belongs to other people’s meetings, and the work that matters keeps sliding to tomorrow. Time blocking replaces the list with the calendar: every piece of work gets a slot before the day begins, so you decide in advance what each hour is for.
In practice that means five habits. Plan tomorrow in 10 to 20 minutes, put your hardest work in a protected block during your best hours, batch the small tasks, leave buffers, and redraw the plan when it breaks instead of abandoning it. Timeboxing adds a hard stop to a block. This guide covers setup, how the four related methods differ, and what to do when meetings and interruptions hit.
Where time blocking comes from and why it works
The modern version comes from Cal Newport. In his post on planning every minute of your work day, he describes spending 10 to 20 minutes at the end of each workday assigning every working hour to a block, then rewriting the schedule whenever it breaks. The point is not obedience to the plan. The point is that every hour has a deliberate decision behind it.
It works for three reasons. First, it cuts task switching. In the experiments behind Rubinstein, Meyer and Evans’s work on task switching, alternating between tasks cost measurable time, and the cost grew with task complexity.
Second, a block turns “work on the report” into a specific time and place, which removes the daily debate about when to start. Third, a finite calendar exposes overcommitment. If eleven hours of tasks will not fit into seven hours of blocks, you find out at 5 p.m. the day before, not at 5 p.m. on deadline day.
Timeboxing is the close cousin. Nir Eyal describes timeboxing as committing to inputs, meaning time and attention, rather than promising a finished output. A block says when you will work on something; a timebox also says when you will stop.
Set up your calendar in five steps
1. Use one calendar and switch on its focus features
Pick the tool you already open fifty times a day. If you use Google Calendar through a work or school account, its Focus time event type can automatically decline meetings that land on a block and mute chat notifications while it runs. In Outlook, a recurring event marked Busy does a similar job.
2. Assign six colors, one per type of energy
- Blue: deep work such as writing, coding, analysis. Notifications off.
- Orange: meetings and calls.
- Gray: shallow work and buffers such as email, chat, expenses.
- Green: breaks, lunch, exercise, personal appointments.
- Yellow: learning and development.
- Brown: commute and travel.
A glance at the week now tells you whether blue survived or orange swallowed it.

3. Place fixed commitments and travel first
Enter meetings you cannot move, classes, school runs and commutes before any task. Block the commute at its realistic length: if the trip usually takes 30 minutes and sometimes 45, block 45.
4. Put deep work in your best hours, then batch the rest
Give your most important task the first blue block of the day, usually 90 to 120 minutes. Then group email, messages and admin into two or three gray blocks using task batching so small requests stop leaking into focus time.
5. Add buffers, then plan tomorrow before you log off
Leave 15 minutes after any meeting or long block. Buffers matter because people systematically underestimate how long tasks take, a bias known as the planning fallacy, even when past experience says otherwise.
A sample office day
Here is how this looks for an insurance claims adjuster with one team meeting and two priorities:
- 8:45 to 9:00 (gray): settle in, scan the inbox for urgent claimant issues only.
- 9:00 to 11:00 (blue): write coverage findings for two complex water-damage claims.
- 11:00 to 11:15 (green): break away from the screen.
- 11:15 to 12:00 (gray): first email and chat batch.
- 12:00 to 1:00 (green): lunch away from the desk.
- 1:00 to 2:30 (orange): team claims review.
- 2:30 to 2:45 (gray): buffer to process meeting notes.
- 2:45 to 4:15 (blue): draft settlement letters, a more routine task for lower afternoon energy.
- 4:15 to 4:45 (gray): second communication batch.
- 4:45 to 5:00 (gray): block out tomorrow.
That is 3.5 hours of protected deep work in a day that still includes a 90-minute meeting and two inbox sessions.
Time blocking vs timeboxing vs batching vs day theming
These four methods are often blurred together. They solve different problems and stack well.
| Method | What it is | Best for | Calendar granularity | Typical failure mode |
|---|---|---|---|---|
| Time blocking | Every working hour assigned to a type of work in advance (Cal Newport) | Knowledge workers with some control over their day | 30 minutes to 2 hours, planned daily | Over-detailed plan breaks by 10 a.m. and gets abandoned |
| Timeboxing | A fixed maximum time for one activity, with a hard stop | Perfectionism, open-ended tasks, inbox clearing | 15 to 90 minutes | Ignoring the stop, so the box becomes a suggestion |
| Task batching | Similar small tasks grouped into one session | Email, calls, errands, admin | 30 to 60 minutes, one to three times a day | Checking leaks between batches and undoes them |
| Day theming | Each day or half day dedicated to one category (popularized by Jack Dorsey and Mike Vardy) | Multiple roles, hybrid weeks, founders | Half day or full day | Too rigid when an urgent cross-theme request arrives |
A common combination is themes for the week, blocks for the day and timeboxes inside the blocks. Our guides to theme days and the timeboxing method go deeper on each.
Two weeks side by side
The same system bends to very different constraints. Compare a hybrid HR business partner (home Monday and Friday, office Tuesday to Thursday) with a second-year architecture student.
| Hybrid HR business partner | Architecture student | |
|---|---|---|
| Fixed blocks | Office days, commute in brown | Studio sessions, crits and part-time shifts, marked immovable |
| Deep work | 4-hour Monday morning block for workforce planning and policy drafts; no video calls on Mondays | Outcome-specific blocks: “2:00 to 4:00 Studio project, finish two section drawings”; “7:00 to 8:30 Architectural history chapter 7, read and outline” |
| Shallow work | 60-minute blocks on office days for employee-relations follow-ups and updating the case tracker | 45-minute blocks for university email, organizing sketches and notes, planning the week |
| Weekly themes | Monday deep work, Tuesday to Thursday manager meetings and employee conversations, Friday wrap-up and learning | Weekdays coursework around studio; weekends for model building and long-term projects |
| Protected personal time | 30-minute decompress buffer after the commute home | Four 60-minute workouts; weekend social time blocked |
| Main risk | Office days fully consumed by meetings | Studio work expanding into every unstructured hour |

When meetings and overruns break the plan
Interruptions: triage, then redirect
Ask one question: will something break, or will someone be blocked, before my block ends? If yes, handle it now and redraw the rest of the day. If no, give it a slot. These scripts help:
- Colleague at your desk: “I’m in a focus block until 11. Can it wait until then, or is something blocked right now?”
- Brainstorm request: “Happy to dig into this. I have 3:00 open; I’ll send an invite.”
- Manager wants something now: “I can do it now and move the report draft to tomorrow morning, or do it at 2:45 today. Which matters more this week?”
- Chat status: “Heads down until 11:00. Call if it’s urgent.”
For requests that should get a firmer answer, see how to say no and protect your time.
Overruns: stop, then choose
When a block ends and the task does not, never silently steal from the next block. Stop and pick one option: swap with a less important later block, split the task into smaller blocks such as “finish research” and “outline”, or ship the good-enough version and schedule revisions separately.

If overruns are constant, your estimates are the problem. A short time audit will show the real duration of your recurring tasks; if a weekly report always takes 3 hours against a planned 2, block 3.
Meeting-heavy calendars
Paul Graham’s essay on the maker’s schedule and the manager’s schedule explains why one badly placed meeting can wreck an afternoon of focused work. Cluster meetings into one half of the day when you can, ask for an agenda before accepting, and label the gaps: a 30-minute slot becomes “Process notes from the vendor call, prep for budget review.” If your role is genuinely reactive and unpredictable, block categories instead of tasks, such as a two-hour “support queue” block followed by a gray follow-up block.
Your first-week checklist
- Choose your calendar and create the six colors.
- Enter fixed commitments and realistic travel time for next week.
- Schedule one 90-minute blue block per day for your single most important task.
- Add two gray batches for communication and 15-minute buffers after meetings.
- Spend the last 15 minutes of each workday blocking tomorrow.
- On Friday, count how many blue blocks survived and move the weakest one to a quieter time slot.
Expect the plan to break on day one. Redrawing it in five minutes, rather than giving up on it, is the skill that makes time blocking last.






16 Comments