There isn’t one right way to block your time. There are five main approaches, each built on different assumptions about how attention works, what your work demands, and how much structure you can realistically sustain.
Choosing the wrong one isn’t just ineffective — it actively undermines your planning habit. Someone who needs extended focus periods will chafe against 25-minute Pomodoros. Someone who struggles to sustain concentration will find 90-minute blocks demoralizing. The fit between your work type and your blocking approach determines whether the system helps or frustrates.
Here’s an honest comparison of all five.
The Decision Criteria
Before diving into the methods, here’s what you’re actually choosing between:
Block length. How long is the fundamental unit of focused work?
Flexibility. How well does the approach survive disruptions and schedule changes?
Cognitive demand. How much mental overhead does maintaining the system require?
Depth potential. How well does this approach support sustained, uninterrupted concentration?
AI leverage. How much does AI assistance amplify (or reduce the friction of) this approach?
Approach 1: Pomodoro Blocks (25 Minutes)
The idea: Work in strict 25-minute intervals separated by 5-minute breaks. After four intervals, take a longer 15-30 minute break. Francesco Cirillo developed the technique in the late 1980s using a tomato-shaped kitchen timer (hence “pomodoro”).
Block length: 25 minutes, non-negotiable.
How it works in practice: You start a timer, work on exactly one task until it rings, take a short break, and repeat. The constraint is structural: 25 minutes is the maximum block length, and the break is not optional.
Honest strengths:
- Extremely low startup friction — the hardest part of any task is starting, and a 25-minute commitment is psychologically easy to accept
- Works well for tasks that don’t require deep immersion: email processing, administrative work, review tasks, coding sprints on well-defined problems
- The break structure prevents the extended fatigue that comes from working through natural rest points
- Research on the technique is modest but suggests benefits for motivation and procrastination reduction on routine tasks
Honest weaknesses:
- 25 minutes is often not enough to reach the kind of deep focus that produces qualitatively excellent creative and analytical work — you’re interrupted right when you’re hitting your stride
- Attention residue (Sophie Leroy, 2009) suggests that the 5-minute break doesn’t fully clear the task from working memory, which can interfere with the recovery the break is meant to provide
- Rigid interval structure doesn’t adapt well to work that has variable natural rhythms — a good writing session interrupted at 25 minutes may take another 10 minutes just to re-enter the same focus state
AI leverage: Moderate. AI can help you batch 25-minute task slots intelligently — identifying tasks of the right scope for a single Pomodoro and sequencing them efficiently. Re-blocking after disruptions is easier because 25-minute slots are easy to swap. But the core method benefits less from AI than longer-block approaches because it’s already simple and rigid.
Best for: Administrative work, email processing, studying, review tasks, routine development work, anyone prone to procrastination who benefits from the commitment device of a short timer.
Avoid if: Your most important work requires extended, uninterrupted concentration — writing, strategic analysis, complex system design, creative problem-solving.
Approach 2: 90-Minute Ultradian Blocks
The idea: Structure deep work in 90-minute blocks aligned with the brain’s natural ultradian rhythm — the roughly 90-minute cycle of higher and lower alertness that neurobiologist Nathaniel Kleitman identified as a feature of waking cognition (building on his earlier work on REM cycles).
Block length: 90 minutes, with genuine breaks (15-20 minutes minimum) between blocks.
How it works in practice: You schedule two or three 90-minute blocks per day for your most demanding work. You protect these blocks from meetings and interruptions. You work continuously during each block — no structured Pomodoro-style breaks — and then take a real break before the next one.
Honest strengths:
- Most neurobiologically coherent approach for cognitively demanding work — you’re working with your brain’s natural rhythm rather than against it
- Provides enough time to enter and sustain genuine flow states, where the quality of output is often substantially better than surface-level focused work
- Two 90-minute blocks per day represents a realistic ceiling for most people’s genuine deep work capacity — it prevents the trap of scheduling more deep work than you can actually sustain
- Aligns naturally with Cal Newport’s deep work prescription
Honest weaknesses:
- 90 minutes is hard to protect in meetings-heavy environments — most organizations have a culture that treats any 90-minute open calendar slot as available
- The genuine break requirement is often skipped, which eventually degrades the quality of subsequent blocks
- Not suited for administrative work — using a 90-minute block for email is overkill and will likely produce poor quality deep work due to the wrong task-to-duration match
AI leverage: High. AI is particularly useful for assessing which tasks warrant 90-minute blocks vs. shorter interventions, for managing the weekly structure of deep work days, and for re-blocking when a 90-minute slot gets disrupted. AI can also help you identify whether you’re genuinely reaching deep work during blocks or just sitting at your desk.
Best for: Writers, researchers, engineers, analysts, strategists — anyone whose most important work requires sustained cognitive engagement and produces qualitatively different output with extended focus.
Avoid if: Your work is primarily reactive and collaborative — managing, advising, coordinating. Long isolated blocks don’t fit the work mode and will create scheduling conflicts with the team dependencies your role requires.
Approach 3: Theme-Day Blocks (Newport’s Model)
The idea: Rather than scheduling at the hour level, assign each weekday a dominant work mode. Mondays for planning. Tuesdays and Wednesdays for deep work. Thursdays for meetings. Fridays for administrative tasks. Within each theme day, work in blocks appropriate to that day’s mode.
Block length: Variable — 90 minutes on deep days, 25-45 minutes on collaborative and administrative days.
How it works in practice: You protect each day’s theme by managing what you accept into it. A meeting request for Tuesday morning, on your deep work day, gets declined or moved to Thursday. Over time, the theme structure becomes a default that reduces daily decision-making.
Honest strengths:
- Operates at a higher level of abstraction than hourly blocking — disruptions to individual tasks don’t invalidate the whole structure
- Dramatically reduces the daily decision about what kind of work to do
- Works naturally with organizational rhythms — most companies have informal patterns for when meetings cluster; you can align your theme structure with these
- Provides a principled basis for declining certain requests: “I keep Tuesdays protected for deep work” is a clearer boundary than “I’m busy”
Honest weaknesses:
- Requires calendar control that not everyone has — managers and consultants often can’t realistically protect full days
- Theme days can become aspirational rather than real if you don’t actively defend them
- Less granular than hourly blocking — if your theme day is “deep work,” you still need a system for deciding which deep work to do and in what order
AI leverage: Very high. Theme days provide the container; AI provides the daily allocation within the container. The Themed Block Method (described in detail in our framework article) is built on this combination. AI handles the task-to-block assignment that theme days deliberately leave unspecified.
Best for: Knowledge workers with moderate calendar control, anyone who finds hourly scheduling stressful or rigid, people who work across multiple different modes throughout the week and want to reduce context-switching.
Avoid if: You have a fully meeting-driven role where you genuinely cannot control which days fill with which work. Theme days require at least partial calendar autonomy to function.
Approach 4: Task-Batched Blocks
The idea: Group similar task types together into dedicated blocks rather than interleaving them. All emails in one block. All calls in one block. All deep-focus work in one block. The rationale is reducing the setup cost and attention residue of constant task-switching.
Block length: Variable by task type. Email batches: 30-45 minutes. Call batches: 60-120 minutes. Focus work: 60-90 minutes.
How it works in practice: You identify your recurring task categories and assign each one a dedicated daily or weekly time window. Emails get answered twice a day, not continuously. Phone calls get batched into a two-hour window. Administrative work happens in one block rather than scattered throughout the day.
Honest strengths:
- Strong research foundation in the attention residue literature — batching reduces the cognitive cost of task-switching by minimizing the total number of switches
- Particularly effective for email and communication management — batching responses produces better-quality replies than constant inbox monitoring
- Easy to explain and adopt incrementally — you can start with just batching email and add other categories over time
Honest weaknesses:
- Doesn’t address the problem of prioritization within batches — a two-hour email block still requires deciding which emails to respond to, in what order, with how much depth
- Less effective for knowledge workers whose work doesn’t cleanly divide into recurring task categories — many important tasks are one-offs that don’t fit a batch
AI leverage: Moderate to high. AI is useful for designing the batch structure — identifying what categories make sense for your work type, how long each batch should run, and how to sequence them across the day. Within a batch, AI can help process efficiently (e.g., drafting email responses, triaging a batch of decisions).
Best for: Managers, executives, consultants — roles with high communication volume and many recurring task types. Also strong for anyone who currently has email open all day and wants a realistic first step toward better focus.
Avoid if: Your work consists primarily of one or two deep-focus projects where batching categories doesn’t apply. The approach is less useful when you’re essentially doing one type of work all day.
Approach 5: AI-Dynamic Blocks
The idea: Rather than using a fixed block structure, use AI to generate an optimized daily block plan each morning based on your current task list, energy, and calendar. When disruptions occur, use AI to re-generate the plan. The block structure is continuously rebuilt rather than set in advance.
Block length: Variable, determined by AI based on task type.
How it works in practice: Each morning you share your task list, available time windows, and any relevant context with an AI assistant. It generates a time-blocked plan for the day. When the day changes, you update the AI and it produces a revised plan. You work from the current AI-generated plan rather than a static schedule.
Honest strengths:
- Maximum flexibility — the plan adapts to real conditions rather than requiring reality to conform to the plan
- AI can make better optimization decisions than most people do under time pressure, especially for complex days with many competing demands
- Lower weekly planning overhead compared to methods that require building detailed structures in advance
- Well-suited for high-volatility roles where no two days look the same
Honest weaknesses:
- Without a stable underlying structure (like theme days), purely dynamic planning can lose the strategic coherence that makes theme-day and ultradian approaches valuable
- Requires consistent daily AI engagement — if you skip the morning allocation conversation, you have no plan at all
- Can encourage excessive planning optimization at the expense of execution — you can spend more time generating the perfect plan than working
AI leverage: Maximum. This approach is entirely built around AI; the leverage is intrinsic to the method.
Best for: Founders, executives, consultants, anyone with fundamentally unpredictable days and high tolerance for adaptive planning. Best combined with some structural element (theme days, protected anchor blocks) to prevent the daily re-planning from becoming entirely reactive.
Avoid if: You work better with stable, consistent routines and find frequent replanning disorienting rather than helpful.
The Comparison at a Glance
| Approach | Best Block Length | Disruption Resilience | AI Leverage | Best Work Type |
|---|---|---|---|---|
| Pomodoro | 25 min | Low | Moderate | Administrative, routine tasks |
| Ultradian | 90 min | Medium | High | Deep creative/analytical work |
| Theme Days | Variable | High | Very high | Mixed knowledge work |
| Task Batching | 30-120 min | Medium | Moderate | High-communication roles |
| AI-Dynamic | Variable | Very high | Maximum | Unpredictable, variable roles |
Which Should You Choose?
If you do primarily deep creative or analytical work: ultradian blocks, with theme days as the weekly container.
If your work is mixed between deep and collaborative: theme days with AI-dynamic allocation within each day.
If you’re drowning in communication and reactive work: start with task batching to create any focused time at all.
If your role is fundamentally unpredictable: AI-dynamic with one protected anchor block per day that you never let go.
If you struggle to start tasks at all: Pomodoro for the commitment device effect, then graduate to longer blocks as momentum builds.
This week: Identify which category your most important work falls into. Then pick the single approach that best fits that work type — not the one that sounds most sophisticated. Run it for two weeks. The science of why each approach works is in our research digest.
Tags: time blocking, productivity methods, AI planning, Pomodoro, deep work, ultradian rhythms
Frequently Asked Questions
-
Which time blocking method is best for deep work?
The 90-minute ultradian block approach is best suited for cognitively demanding deep work — writing, coding, strategic analysis, complex problem-solving. It aligns with the brain's natural alertness cycles and provides enough time to enter and sustain a genuine flow state. The Pomodoro method, while useful for other work types, tends to interrupt focus at the 25-minute mark, which is often right when deep work is reaching its productive peak.
-
Can I combine multiple time blocking approaches?
Yes, and most experienced time blockers do. A common hybrid: 90-minute ultradian blocks for deep creative or analytical work, Pomodoro intervals for administrative processing, and theme days as the weekly container that determines which approach applies on which day. The key is assigning each approach to the task types it's best suited for rather than using one method for everything.
-
Is AI-dynamic time blocking suitable for everyone?
It's most valuable for people with variable, unpredictable schedules — founders, managers, consultants, anyone whose day is frequently disrupted by external demands. For people with highly predictable schedules and good calendar control, a simpler static approach may work just as well with less overhead. The AI-dynamic approach earns its value in the re-blocking moments; if you rarely need to re-block, the simpler methods are sufficient.