Skip to content

Guide

Timeboxing vs time blocking: which works for you?

Both put your work on the clock, but they answer different questions. Time blocking decides when you work on something; timeboxing decides how long it is allowed to take. Here is how to use each, and how to size the boxes so they hold.

To-do lists say what to do, never when or for how long. That is why the same five items can roll over from day to day. Time blocking and timeboxing both fix that by bringing the clock in, and they are often confused because many people use them together. The difference is worth knowing, because they solve different problems.

Time blocking: give the day a shape

Time blocking means dividing your working day into blocks in your calendar and giving each block a job: 9:00–11:00 writing the report, 11:00–11:30 email, 13:00–14:00 meetings. The author and computer science professor Cal Newport, one of its best-known advocates, describes it as giving every minute of the workday a job, instead of reacting to email and picking whatever is next on a list.

The plan will break, and that is expected. Newport’s advice is to rebuild the schedule for the rest of the day when it does, rather than abandon it. The point is to decide where the time goes, not to follow the plan perfectly. Time blocking is strongest for protecting long stretches of focused work from meetings and messages, and weakest in jobs that are mostly interruptions.

Timeboxing: a fixed limit, then stop

A timebox is a fixed amount of time you allow for a task. When it ends, you stop and judge the result: it is done, it is good enough, or it gets another box later. The limit is the point. It forces you to start with the part that matters most and stops perfectionism from eating the afternoon. In a 2018 Harvard Business Review article, Marc Zao-Sanders reported that timeboxing came out top in a ranking of 100 productivity hacks.

Software teams use timeboxes for meetings. The Scrum Guide caps each of its events, scaled for a sprint of one month (shorter sprints usually get shorter events):

Timeboxes in the Scrum Guide (2020)
EventMaximum length
Sprint Planning8 hours
Daily Scrum15 minutes
Sprint Review4 hours
Sprint Retrospective3 hours

Side by side

MethodTime blockingTimeboxing
DecidesWhen you work on each thingHow long a task may take
Lives inYour calendarA timer, or a limit on an agenda
When time runs outMove to the next block, or rebuild the planStop and decide: done, good enough, or another box
Best forProtecting focus time across a whole dayTasks that expand, perfectionism, meetings
Typical trapBlocks too full, so every day ends behindBoxes so short that nothing gets finished

They combine naturally. Block 9:00–11:00 for the report, then work inside it in timeboxes: 45 minutes for the draft, 30 for the figures, 15 to tidy up.

Why a limit helps: Parkinson’s law

“Work expands so as to fill the time available for its completion.” C. Northcote Parkinson opened a 1955 essay in The Economist with that line. He was poking fun at government departments, not giving productivity advice, but the sentence stuck because it matches everyday experience: give a task the whole afternoon and it will usually take it. A timebox takes away the spare time it would expand into.

Short focus rounds

The best-known system of short timeboxes is the Pomodoro Technique®, which Francesco Cirillo began developing as a university student in the 1980s with a kitchen timer. He describes it as a complete system for dealing with time, with stages for planning, focusing and reviewing, rather than just a timer. Pomodoro® is his registered trademark, and his site and book are the place to learn the method as he teaches it.

Whatever system you follow, short rounds with breaks suit tasks you keep putting off, because a short stretch is easy to start. The focus timer runs rounds of focus and breaks of any length you choose; the plain online timer works for any single box.

How long should a box be?

The hard part of both methods is estimating. People are reliably optimistic about their own tasks, a bias psychologists call the planning fallacy. In a well-known 1994 study, psychology students writing an honours thesis expected to finish in 33.9 days on average. They took 55.5. Only 29.7% finished by their own best guess, and fewer than half, 48.7%, even finished by the date they gave for the case where everything went as badly as it could.

The study found that people base predictions on their plans for the task and neglect how long similar tasks took before. That points to the remedy for timeboxes too:

  1. Measure a few real tasks. Run the stopwatch while you do the things you plan most often, such as a weekly report or a set of emails. Use the lap button to time each part.
  2. Box from the measurement, not the hope. If the report took 70 minutes the last two times, a 45-minute box isn’t ambitious, it is wrong.
  3. Leave slack in the day. In a time-blocked day, leave some blocks empty for whatever overruns or turns up.
  4. Decide at the bell. When a box ends, choose: done, good enough, or a new box later. Extend once at most.

Timeboxing a meeting

  • Give every agenda item a length and put the times in the invitation.
  • Run a visible countdown for each item, such as a 10-minute timer on the shared screen, so the limit belongs to the room, not to the chair.
  • When an item runs out, park the rest of the discussion with a named owner.
  • End on time, even if items are left. Timeboxes only work if they are kept.

Running timers in a browser tab? Read how accurate online timers are to make sure the alarm goes off when you expect it to.

Frequently asked questions

What is the difference between timeboxing and time blocking?

Time blocking decides when you work on something: you divide your calendar into blocks and give each one a task. Timeboxing decides how long you will spend: you set a fixed limit and stop when it runs out, finished or not. Many people combine them by putting a timebox inside each block.

What happens when a timebox runs out and the task isn’t done?

You stop and decide on purpose instead of drifting on. Either the result is good enough, or you plan another box for it later, or you extend it once, knowingly. What matters is that running over becomes a choice rather than something you notice at the end of the day.

How long should a timebox be?

Long enough to finish something meaningful, short enough that the end is in sight. A short box makes a dreaded task easier to start; deep work such as writing needs longer to get into. Base it on how long similar tasks really took you, not on how long you hope this one takes.

Is Parkinson’s law a scientific law?

No. It is the opening line of a humorous 1955 essay in The Economist by C. Northcote Parkinson, who was really writing about the growth of government departments. It is quoted because it matches common experience, not because it was measured.