Does time blocking work if my job is highly reactive?
Yes, but the implementation looks different. In highly reactive roles, you don't block every hour, you reserve two to three smaller deep work windows (45–60 minutes each) and treat the rest as reactive time. Even one protected deep work block per day, consistently maintained, produces measurably more meaningful output than a day without any. Time blocking doesn't require full schedule control to be effective.
How do I handle unexpected tasks that come up during blocked time?
Capture them immediately in a running list and address them in the next shallow work or buffer block. Assess genuinely urgency before deciding to interrupt a deep work block, most 'urgent' interruptions are not actually urgent and can wait 90 minutes. Your buffer blocks exist specifically for the things that genuinely can't wait. If you're consistently getting interrupted by genuine emergencies, the system problem is upstream of time blocking.
What's the difference between time blocking and a to-do list?
A to-do list tells you what to do. Time blocking tells you when you'll do it. The two work together: your to-do list is the inventory of tasks; your time block schedule is the commitment about when each category of task gets addressed. Without time blocking, a to-do list is just a wish list, tasks sit there accumulating without a mechanism to get them done.
How rigid should time blocks be?
Rigid enough to protect, flexible enough to survive real life. The deep work blocks should be treated like external commitments, you need a genuine reason to move them. Shallow work and buffer blocks are more flexible and can shift day-to-day. Think of your schedule as a weekly template that you adapt each Monday, not a rigid minute-by-minute plan that fails the moment something unexpected happens.
- Audit your current week (Day 1) — Before you can design a better schedule, you need honest data about your current one. Track how you actually spend your time for one full week, in 30-minute increments. Most people are shocked by how much time goes to email, meetings, and context-switching. This audit is your baseline.
- Identify your two peak focus hours — Based on your chronotype and your week's audit, identify the two hours per day where your cognitive performance is highest. These hours are non-negotiable deep work blocks, they will never be filled with meetings or emails. For most people, this is a 90-minute window in the late morning.
- Block all recurring meetings first — Add every recurring meeting to your template week before adding any work blocks. This gives you a realistic view of the time that's already committed. If recurring meetings are consuming more than 30% of your workweek, that's the real problem to address, before any time blocking system can help.
- Schedule your deep work blocks next — Around your meetings and within your peak hours, carve out at least two 90-minute deep work blocks per day. These are the highest-priority blocks in your schedule. If you can only protect one, protect the morning one. Mark them as 'Busy' to external calendars.
- Fill in shallow work and buffer blocks — Assign specific shallow work categories to the remaining time: 'Email and responses', 'Administrative tasks', 'Planning and prep'. Add at least one 30-minute buffer block per day for the unexpected, because something unexpected always happens, and without a buffer, it steals from your deep work time.
- Review and adjust the template weekly — Time blocking works as a weekly template, not a rigid daily dictate. Each Sunday or Monday morning, adapt the week's template to reflect that week's specific priorities, meetings, and deadlines. The template is the default; judgment adjusts it weekly.
Originally published on Xenith.
Top comments (0)