The Problem with an Open Calendar
Most knowledge workers operate from a reactive model: you show up, you check what needs to be done, you respond to whoever needs responding to, and at the end of the day you do whatever's left. This feels productive because it's busy. But busyness is not the same as meaningful progress, and for most people, the work that actually matters — the creative thinking, the strategic decisions, the complex writing or analysis — gets squeezed into whatever fragments of time remain after everything urgent has been handled.
Time blocking is a direct challenge to this model. Instead of letting demands fill your time, you pre-decide how your time will be used, assigning specific blocks to specific types of work before the day begins.
What Time Blocking Actually Is
At its simplest, time blocking means dividing your workday into chunks and assigning each chunk a purpose. Rather than working from an undifferentiated to-do list, you have a day-plan that looks something like:
- 8:00–10:00 am: Deep work — writing/strategic thinking (no interruptions)
- 10:00–10:30 am: Email and messages
- 10:30 am–12:30 pm: Project work
- 12:30–1:30 pm: Lunch / walk / genuine rest
- 1:30–3:00 pm: Meetings and collaborative work
- 3:00–3:30 pm: Email and messages
- 3:30–5:00 pm: Admin, planning, shallow tasks
The specifics will vary enormously depending on your role and life. The structure is the point — not the exact allocation.
The Case for Protecting Deep Work
Computer scientist and author Cal Newport defines "deep work" as cognitively demanding activities performed in a state of distraction-free concentration that push your abilities to their limit and create real value. In contrast, "shallow work" covers logistical, administrative, and easily replicable tasks that don't require deep focus.
The key insight is that these two types of work are not just different in difficulty — they're different in neurological character. Deep work requires sustained, unbroken concentration to reach a productive state (sometimes called "flow"). Shallow work actively prevents that state from occurring, because each interruption or task-switch resets the mental momentum required to do complex thinking well.
Most workplace cultures inadvertently optimise for shallow work — constant availability, instant response norms, back-to-back meetings — while claiming to value deep work outputs. Time blocking is a structural response to this contradiction.
How to Start Time Blocking: A Practical Approach
- Audit your current time use for one week. Before redesigning your schedule, understand what you're actually doing. Track how you spend your working hours in rough 30-minute blocks. Most people find this uncomfortable — and revelatory.
- Identify your peak cognitive hours. Most people have a 2–4 hour window each day when their thinking is sharpest. For many, this is morning; for others, late morning or early afternoon. Reserve this window jealously for your most demanding work.
- Design your ideal day template. Create a rough template — not a rigid schedule, but a default structure — that reflects your priorities. What must happen every day? When will you do focused work? When will you handle communication?
- Batch similar tasks. Email, messages, and administrative tasks are most efficiently handled in concentrated batches rather than scattered throughout the day. Set 2–3 designated communication windows and stick to them as much as your role allows.
- Block time in your calendar as appointments. A focus block that isn't in your calendar is vulnerable. Treat your deep work blocks as meetings with yourself that can't casually be moved.
- Review and revise weekly. Time blocking requires iteration. At the end of each week, review what worked and what didn't. Adjust the template. The goal is a sustainable, workable system — not a perfect one.
Managing Pushback and Imperfect Days
One legitimate concern about time blocking is that it seems incompatible with collaborative or interrupt-driven roles. A few responses to this:
- Even one protected deep work block per day — even 90 minutes — is transformatively better than none.
- Most "urgent" interruptions are not actually urgent. Batching responses to a 2-hour delay is usually fine and often appreciated as clear communication.
- Imperfect days are not failed days. If your blocks get disrupted, adjust and recommit tomorrow. The value of the system is in the default orientation, not in rigid adherence.
The Philosophy Beneath the System
Time blocking is, at its heart, an act of values clarification. When you pre-assign your time, you're forced to answer: what actually deserves my best hours and clearest thinking? For most people, the honest answer is not email. It's not most meetings. It's the work that only you can do — the thinking, creating, and deciding that represents your genuine contribution.
Structuring your day around that answer isn't just a productivity hack. It's a way of taking your own work — and your own time — seriously.