What is time blocking?
Time blocking is a planning technique that splits the day into time blocks. Every task enters the calendar the way a meeting does, with a start and an end. The reason is simple: a task with no assigned time has no protection — it slides through the day and often never happens.
The technique was widely popularised by Cal Newport, author of Deep Work: work that is not written into a calendar sits in your head for hours as an open tab and quietly drains focus (source: calnewport.com / Deep Work).
Which work suits it
- Deep work — coding, writing, design, studying. Blocks of 90-120 minutes are ideal.
- Meetings — with a clear start and end.
- Email and messages — once or twice a day inside a 30-minute block. Notifications stay off the rest of the time.
- Exercise, meals, rest — it feels unnecessary to schedule these, but without the blocks the day fills with something else.
Time blocking, Pomodoro and the to-do list
| Technique | Block length | Best for |
|---|---|---|
| Time blocking | 60-120 min | Deep work, meetings |
| Pomodoro | 25 min | Tasks that are hard to start |
| To-do list | – | Small, quick items |
Mixing them is normal: a daily plan sets the overall shape, the big items move into calendar blocks, and Pomodoro sessions run inside each block.
How it works in the Unumly calendar
Open Kalendar in week or day view. Click an hour slot to add a task, or drag an existing one onto the time you want. Dragging the edge of a slot sets how long the task should take, and the bot reminds you before it starts.
A good first run: place tomorrow's three biggest tasks into 90-minute blocks. Leave the remaining hours for small work, rest and meetings.
The mistakes that break it
- Blocking 100% of the day. A plan with every minute assigned breaks at the first surprise. Block 60-70% and leave 30% open.
- Skipping buffers. Leave 10-15 minutes between blocks for the switch, a pause and the loose ends.
- Optimistic estimates. Add at least 25% to whatever length feels right. The first week of time blocking mostly teaches you this.
If blocks collapse regularly, run inversion thinking over your schedule: list what breaks the blocks, then close each cause with one concrete change.
Frequently asked questions
- Is time blocking the same as using Google Calendar?
- No. Google Calendar is one tool; time blocking is the method. A calendar usually holds meetings. With time blocking every piece of work — writing a report, coding, reading — goes in too, as if it were a meeting.
- How long should a block be?
- 90-120 minutes for deep work, 30-60 for meetings, 15-30 for small tasks. The common mistake is scheduling deep work in half-hour blocks: attention is only starting to settle by the time the block ends.
- Who is time blocking wrong for?
- People whose day is made of unpredictable incoming work — support agents, doctors on call. There a "protected block" format works better: only breaks and rest are scheduled, the rest of the day stays reactive.
- What do I do when a meeting appears out of nowhere?
- Rearrange the blocks, but do not throw away the plan. If one block slips the others shift after it, and the calendar shows you that. If two or three blocks slip in a day, write down the reasons that evening — that is the raw material for tuning the system.
- Can I combine time blocking and Pomodoro?
- Yes, they pair well. Time blocking reserves a 90-minute deep work block; inside it you run three Pomodoro sessions (25 + 5 + 25 + 5 + 25). The combination suits writing, coding and studying.
- Isn't rebuilding blocks every day exhausting?
- For the first couple of weeks, yes. Then templates appear: exercise in the morning, deep work from 9:00, meetings on Wednesday. Once the template is stable, planning a day takes five to seven minutes.