Timeboxing for Focus: How to Plan a Day in Fixed Blocks

A timebox is a fixed period, with a start and an end, reserved for one piece of work and a defined output. When the time is up you stop, look at what you have, and decide what happens next. The idea comes from software project management, where fixed-length iterations such as Scrum sprints replaced open-ended deadlines, but it works just as well for a single person's day.

The difference from a to-do list is structural. A list has no sense of time: it grows faster than it shrinks, treats a five-minute reply and a five-hour report as equal lines, and quietly rewards picking the easy items first. A timeboxed day forces three decisions a list lets you avoid:

• What exactly will exist at the end? "Draft the first three sections", not "work on the report".
• How long is it worth? A box is a budget as much as an estimate.
• When will it happen? If a task has no slot, it is not really planned.

Most people keep the list as an inbox and use boxes to decide what actually gets done today.

In a 1955 essay in The Economist, the historian C. Northcote Parkinson wrote that "work expands so as to fill the time available for its completion". He was describing bureaucracies, but the pattern is familiar in any job: give a task an afternoon and it takes the afternoon, with extra polishing, research and rereading. A box caps that expansion by setting a near, concrete deadline.

The opposite problem is just as common. Psychologists Daniel Kahneman and Amos Tversky named it the planning fallacy: people underestimate how long their own tasks will take, even when they know similar tasks overran before. In a well-known 1994 study, students predicting when they would finish their final-year theses took about three weeks longer on average than expected, and longer even than their own worst-case guesses.

Timeboxing addresses both. The fixed end stops work sprawling, and because every box ends with a check, you find out within the hour, not at the deadline, that an estimate was wrong.

Start from the output, not the clock. Write down what "done" means for this box, estimate how long it would take if nothing went wrong, then add about a quarter. Useful standard sizes:

• 15 minutes for small admin: a form, a booking, a quick reply that needs thought.
• 25 to 30 minutes for batched email and messages, or one clear sub-task. The Pomodoro technique is simply a fixed 25-minute box.
• 45 to 60 minutes for most focused work: writing, analysis, a code change.
• 90 minutes as a ceiling for deep work. Few people sustain full concentration longer without a break.

If a task will not fit in 90 minutes, it is a project; split it into boxes with their own outputs. If you cannot say what the output of a box is, the task is not yet understood, and the first box should be "define the task". Try to keep a day to three or four focused boxes; beyond that, quality usually drops.

A box only works if it is protected, which in practice means it lives in your calendar as an event, marked busy, with the output in the title. Colleagues see a meeting with yourself and book around it.

1. Put the hardest work in your best hours. For most people that is the first box of the morning, before messages fragment attention.
2. Batch the shallow work. Two or three fixed boxes for email and chat beat checking constantly.
3. Cluster meetings. Two meetings back to back cost less focus than two meetings two hours apart. Keep them short with a meeting timer; running a timed meeting explains how.
4. Leave 20 to 25 per cent unscheduled. Interruptions and overruns will happen; buffer boxes absorb them without wrecking the afternoon.
5. Plan tomorrow before you finish today. Ten minutes of shutdown turns tomorrow's first box into something you can start without deciding.

During the box, keep the time visible. The focus timer, with 25, 50 and 90-minute modes, or a plain countdown timer works; students can use the study timer, which builds in breaks.

When the timer rings, stop, even mid-sentence, and take one of three decisions:

• Done: mark it and move on.
• Nearly done: take one explicit extension of at most 10 to 15 minutes, drawn from a buffer box, never from lunch or the next box.
• Not close: write down where you stopped and the next step, then schedule a new box. Re-scope the output if the original was too ambitious.

Never let an overrun silently cascade. A box that eats the next one does not add time to the day; it just moves the failure somewhere else. Keep a note of estimated versus actual time for a week or two. Most people find a consistent ratio, often 1.3 to 1.5, and multiplying future estimates by it makes plans honest.

Time	Box	Defined output
08:45–09:00	Plan	Today's boxes confirmed, top three outcomes written
09:00–10:30	Deep work 1	Proposal sections 1–3 drafted
10:30–10:45	Break	Away from the screen
10:45–11:15	Email and chat, batch 1	Everything answered, filed or scheduled
11:15–12:00	Deep work 2	Three charts for the proposal
12:00–13:00	Lunch	—
13:00–13:30	Team meeting	Decisions and owners recorded
13:30–14:15	Admin	Expenses submitted, next week booked
14:15–14:30	Buffer	Overruns and interruptions
14:30–15:30	Deep work 3	Colleague's draft reviewed with comments
15:30–16:00	Email and chat, batch 2	Inbox clear of actions
16:00–16:40	Buffer	Overflow, or an early start on tomorrow
16:40–17:00	Shutdown	Estimates checked, tomorrow's boxes set

Three deep-work boxes total just over three hours, a realistic amount of concentrated work for most people. Teams that plan in two-week sprints can track the bigger block with the sprint timer, and a countdown to a real deadline keeps the week's boxes in proportion.