Frequently Asked Questions About Todoist Time Blocking Productivity System
20 answers covering everything from basics to advanced usage.
// Basics
What exactly does 'schedule as self-appointment' mean?
It means treating a task block in your calendar as legitimate and non-negotiable as any external appointment. Tasks aren't things you get to 'when you can' — they're protected slots you're keeping with yourself, as important as a meeting with your boss. This mindset shift is what stops important work from being perpetually crowded out by other people's demands.
What is the planning fallacy and how does time blocking address it?
The planning fallacy is the psychological tendency to systematically underestimate how long tasks take. Time blocking forces honest confrontation with it because every commitment requires a real physical slot in your calendar — you can't overload a day that only has so many hours. Recording actual durations during your weekly review corrects your estimates over time.
What is the 40-hour time-blocked workweek rule?
It's Cal Newport's principle that a 40-hour week of structured time blocking produces the same output as a 60+ hour unstructured week. The multiplier is structure, not raw hours. By eliminating reactive scrambling and context switching, and by protecting deep work, you extract far more meaningful output from fewer, more focused hours.
// How To
What tools do I need to start time blocking?
You need a task list, your existing calendar commitments, and a calendar tool of choice — paper, Google Calendar, Outlook, or a task manager with a calendar view like Todoist. Optionally, knowing your peak productivity window and historical time data makes blocks far more accurate. If you lack that data, run a tracking week first.
How do I decide which tasks deserve deep work blocks?
Review your full task list and separate what's truly important from what's merely loud or urgent-feeling, using a method like the Eisenhower Matrix if needed. The high-priority, high-focus tasks — strategic thinking, drafting, creative work — become deep work blocks. Schedule these during your peak productivity window and never fill those hours with email or admin.
How much buffer time should I add to my schedule?
Add enough buffer to absorb realistic spillover — often a 15-30 minute block at the end of each day, plus short buffers before and after meeting batches for prep and follow-up. Buffer time captures overrunning tasks, unexpected requests, and bonus work. Because of the planning fallacy, err toward more buffer than you think you need.
How do I run the weekly review for time blocking?
At the end of each day or week, compare what you planned against what actually happened. Note which tasks consistently overran their estimates, which blocks got disrupted most, and where your energy mismatched your scheduling. Adjust future estimates and block placement accordingly. The system only improves through this reflect-and-iterate cycle.
// Troubleshooting
What do I do when an interruption blows up my schedule?
Move the affected block rather than abandoning it — time blocks are a plan, not a prison. The power of the system is knowing exactly what you planned and having the clarity to adjust in real time without losing momentum. To reduce disruption, build reactive-mode or 'requests from others' buffer slots into your schedule from the start.
Why does everything take longer than I blocked for it?
That's the planning fallacy in action — humans systematically underestimate durations. Fix it by tracking actual task times during your weekly review and adjusting future blocks upward. If drafting consistently runs three-and-a-half hours instead of three, block three-and-a-half. Always keep end-of-day buffer time to absorb overruns while your estimates recalibrate.
My deep work block keeps getting invaded by meetings — what do I do?
Batch all meetings into a dedicated afternoon block and protect your morning deep work window as a non-negotiable self-appointment. When meeting creep invades it, use your review data as evidence to push back on scheduling requests. Treat the block with the same weight you'd give an external meeting you couldn't reschedule.
Is time blocking too rigid for a chaotic, unpredictable job?
No — flexibility over rigidity is a core principle. Blocks are expected to move as real life intervenes. For unpredictable roles, build generous reactive buffer slots and shorter deep work blocks, then shift things around as needed. The value isn't a perfect plan; it's the clarity to know what you intended and the control to adapt.
What are the biggest mistakes beginners make with time blocking?
The top mistakes are underestimating task duration, being too rigid when life intervenes, scheduling relaxation as a chore, failing to prioritise so everything feels urgent, ignoring interruptions instead of buffering for them, wasting peak hours on shallow work, and skipping the weekly review. Each one either overloads the plan or stalls the improvement cycle.
// Comparisons
How does time blocking compare to the Pomodoro Technique?
Pomodoro structures focus within a session using fixed 25-minute intervals and short breaks, while time blocking structures your entire day by assigning tasks to calendar slots. They're complementary: use time blocking to decide when you work on what, and Pomodoro inside a deep work block to sustain focus. Time blocking is the macro plan; Pomodoro is a micro tactic.
How does time blocking compare to time boxing?
Time blocking reserves an open-ended slot for a task or batch, while time boxing sets a strict, fixed limit you refuse to exceed. Time boxing is useful for capping low-value or perfectionism-prone tasks, whereas time blocking is broader and includes deep work, batching, and buffers. Many people combine them — box the admin, block the deep work.
How is time blocking different from just prioritising a to-do list?
Prioritising tells you what matters most but not when you'll do it, so top tasks still compete for whatever time is left over. Time blocking adds an implementation intention — a specific time, date, and task — which research shows dramatically improves follow-through. It also forces you to confront the planning fallacy because every priority needs a real slot.
// Advanced
How do I combine task batching with deep work blocks effectively?
Batch shallow, similar tasks — emails, admin, quick calls — into shared blocks outside your peak hours to minimise context switching. Reserve your peak productivity window exclusively for deep work on one important task at a time. This way batching handles the volume of small work efficiently while deep work protects the high-value output that actually moves things forward.
What is the implementation intention effect and why does it boost follow-through?
The implementation intention effect is research showing that people who assign a specific time, date, and task to a goal are far more likely to follow through. 'I'll work on X Monday 10am-12pm' vastly outperforms vague intentions like 'I'll get to that next week.' Time blocking builds this effect into your schedule by design.
Should I time block every single day or just plan the week?
Do both — block the week to see the big picture and protect deep work, then refine daily as reality shifts. Weekly planning gives intentional structure and lets you spot meeting creep and energy mismatches; daily adjustment keeps blocks realistic. The daily review also feeds the reflect-and-adapt cycle that steadily improves your estimates.
How do I use my peak productivity window in a time blocked schedule?
Identify the hours when you feel most focused and capable of your best work, then reserve them exclusively for deep work blocks — never email or low-value admin. Wasting your best hours on shallow tasks is a core pitfall. Schedule batches of admin and reactive work for your lower-energy periods so your peak hours produce your highest-value output.
Can I time block if I don't have historical time data?
Yes — start by running a tracking week where you record how long tasks actually take before you build blocks. This data is invaluable and non-negotiable for accurate planning. Once you have it, your estimates and blocks become dramatically more realistic. Until then, rely on honest guesses plus generous buffer time to cover the uncertainty.