The three names sound alike and are often used interchangeably, and all three promise a more focused day. They are not competing methods. Each one answers a different question. A frequent way for a technique to disappoint is being asked to do another one’s job: a block expected to enforce a stop, for instance, or a box expected to protect a slot on the calendar.

A time block reserves a slot on the calendar. A timebox (also written time box) caps how long a piece of work may take. A batch groups similar tasks so they are handled together. The useful part is not the definitions but where each one breaks, and what the research says about the mechanism behind it.

Three Questions, Three Techniques

A time block reserves the slot, a timebox caps the effort, and a batch decides who shares the slot. worldtimedata

The anchor row is the sharpest split. A block says 10:00 to 11:30, two points on the clock. A box says 90 minutes, a time interval with no fixed start. A batch says nothing about time at all. That is why one entry on a calendar can be all three at once, and why a template that only lists start and end times is a time-blocking template whatever it is called.

Time Blocking: Reserving the When

The best-known version comes from Cal Newport: give every minute of the workday a job by assigning specific work to blocks, and when an interruption knocks you off the plan, rewrite the rest of the day rather than abandon it. As commonly described, his method uses blocks of at least 30 minutes, adds conditional overflow blocks to absorb tasks that run long, and groups small tasks into shared task blocks. Newport’s own claim is that committed time blocking can roughly double your results. That is his experience, not a measured effect.

What research supports is the mechanism. A meta-analysis of 94 independent tests (more than 8,000 participants) found that specifying in advance when and where you will act on a goal improved goal attainment by a medium-to-large margin (d = 0.65), mostly compared with holding the goal alone. Those studies tested if-then plans, not calendar blocks, so time blocking is an application of the effect, not a direct test of it.

The weak point is estimation, because a block only works if the task fits in it. In a classic 1994 study, 37 psychology students predicted their thesis would take 33.9 days on average and took 55.5, which is 64% longer, and only about 30% finished within their own prediction. Those were multi-week projects, not half-hour tasks, but the direction of the error is the reason overflow blocks exist.

Timeboxing: Capping the How Long

The term entered the literature through James Martin’s 1991 book Rapid Application Development. Its cleanest modern form is the Scrum sprint. The 2020 Scrum Guide defines sprints as fixed-length events of one month or less (it no longer calls them timeboxes, but the logic is the same) and says scope may be clarified and renegotiated as more is learned. Time is the constant and scope is the variable. The guide does timebox the meetings around a sprint: Sprint Planning is capped at eight hours for a one-month sprint, and the Daily Scrum runs 15 minutes. This works against Parkinson’s law, the observation that work expands to fill the time available, because the time cannot expand.

The individual version is the Pomodoro technique, a timebox of 25 minutes with a rule that the bell means stop. The box itself needs no duration estimate: you decide how much time the work gets. (Cirillo’s full method does ask you to estimate tasks in pomodoros, but each box stays fixed.) Any timer is enough to run one.

The hidden cost is the stop itself. In Sophie Leroy’s 2009 experiments, people who moved on from an unfinished task performed worse on the next one, because part of their attention stayed behind. Being able to finish first was not enough on its own, and time pressure while finishing helped people let go of the earlier task. The implication for timeboxing is an inference, not a tested result: a hard stop leaves work unfinished by design, which is the condition that produces this “attention residue.”

A possible fix comes from Leroy and Glomb (2018). Across four studies, people who wrote a short ready-to-resume plan before switching, noting where they left off, what remains, and what to do next, showed less residue and performed better on the interrupting task. Those studies concerned interrupted work, not timeboxes, so applying the idea here is an extrapolation. It costs about two minutes at the end of a box, which makes it cheap to try.

Task Batching: Grouping the What

Batching attacks the switching problem from the other side. Instead of stopping unfinished work more carefully, it reduces how often you switch between kinds of work at all. The clearest controlled evidence is from email. In a two-week study, 124 adults spent one week limiting email checks to three per day and one week checking freely. They actually checked 4.7 times a day in the limited week and 12.5 times in the unlimited week, against a baseline of 15.5. In the limited week they reported lower daily stress and felt less distracted by email. No other well-being measure moved directly.

Three limits apply. The study measured stress, not output. It tested three checks against unlimited checking, not three against five, so three is not proven optimal. And it covered email only. The price of batching is latency: whatever arrives waits for its session, and a batch with no ceiling grows to fill the day. That is why the sensible pairing is a batch inside a timebox.

How They Combine in One Day

The calendar below stacks all three. Every row is a block on the clock. The 20-minute rows are batches with a timebox, and the overflow row is Newport’s conditional block.

Take out the lunch hour and the day has 420 working minutes. Protected focus is 150 of them, 36%. If the overflow block is needed for the same work, that rises to 210, 50%. The plan also reserves 110 minutes, 26%, for slippage: 50 in buffers and 60 in the overflow block, which is either focus or slack depending on how the day goes. That is deliberate slack in a day that would otherwise assume everything goes to plan. The three email passes match the cap tested in the study above. To run the same arithmetic for your own shift, a work hours calculator gives you the starting number.

Where Each One Breaks

Choosing by Problem