What timeboxing actually is
Timeboxing means work gets a fixed span rather than an open end. Not "I work until the quote is done", but "I work on the quote from 09:00 to 10:30, and at 10:30 I decide again".
The difference looks small and is fundamental. Without a box, duration follows the task; with a box, scope follows the time. The first is why work expands until the day is full. The second forces a decision, and decisions are what keep a day moving.
Three related terms get mixed up constantly:
| Term | What it does | What it does not do |
|---|---|---|
| Calendar blocking | Reserves time for a topic | Does not force an end |
| Timeboxing | Sets start, end and a decision at the end | Does not dictate how often you break |
| Pomodoro | A fixed 25/5 rhythm | Does not adapt to the kind of work |
Pomodoro is a special case of timeboxing with a fixed length. For work whose spin-up time exceeds five minutes — most knowledge work — the 25-minute box is too short: you are just getting in when the timer goes.
Disclosure: we build Balane Plan, an app that places focus blocks into real calendar gaps automatically. Timeboxing itself needs nothing but a calendar and the willingness to actually stop when the box ends.
Why it works: three mechanisms
1. It makes overcommitment visible before it happens. Seven tasks on a list look feasible. Seven blocks in a calendar do not fit into the day — and you see that immediately. The list hides the collision; the calendar shows it.
2. It closes the open-ended task. Work without an end expands. The effect is known as Parkinson's law, and it cuts both ways: a tight box regularly leads to cutting the task smaller — and then discovering the smaller cut would have been enough.
3. It generates measurements. Every expired box is a data point: planned 90 minutes, needed 130. After two weeks you have a correction factor, and your next boxes are right.
Block sizes: what belongs in which box
The most common question, and the answer depends on the kind of work, not on taste.
| Kind of work | Box size | Reasoning |
|---|---|---|
| Demanding solo work | 90 min | After ~15 min of spin-up, 75 minutes of real depth remain |
| Building and development | 90–120 min | Long spin-up, high cost of re-entry |
| Writing (first draft) | 45–60 min | Quality drops earlier than in analytical work |
| Debugging | 60–90 min, then reassess | Duration unknown; the box caps the loss |
| Small stuff, email, approvals | 20–30 min, batched | Done together, not scattered through the day |
| Coordination, clarifications | 25 min | Longer usually means a decision is missing |
Two rules alongside that:
- Under 25 minutes a box is not worth it. Spin-up eats the value. Small stuff belongs batched into a shared box.
- Over 120 minutes nobody holds out. Your head takes the break anyway — better planned than as twenty minutes of scrolling.
The method in practice
Step 1 — work out net time. Subtract meetings, breaks and recovery first. Putting boxes into gross time means planning boxes into time that does not exist. The full calculation is in the day planning guide.
Step 2 — place the hardest box first. Into the longest contiguous block of the day, usually the morning. Everything else arranges itself around it.
Step 3 — size the box with your correction factor. A box set to the estimated duration is a box that will break. Multiply.
Step 4 — put buffer between the boxes. 10 minutes between boxes on different projects, 10 to 15 minutes after each longer meeting. Buffer at the end of the day is not buffer.
Step 5 — actually stop when the box ends. This is the step the whole method stands or falls on. Note two sentences: where I am, what the next step is. Then decide: done, second box, or cut differently.
Step 6 — record the deviation. Planned and actual, on one line. That is the data for next week.
The five mistakes that kill it
Mistake 1: planning the whole day. The most common reason people quit. A day that is 100% boxed tips over at the first interruption — and there will be one. Box 60 to 70 per cent of your net time. The rest is the reserve that lets the plan survive.
Mistake 2: treating boxes as appointments with yourself. A block with no decision at the end is calendar blocking, not timeboxing — and then you simply move it. The decision is the method.
Mistake 3: cutting too finely. Five 20-minute boxes are four context switches and therefore about an hour of lost time. Merge them.
Mistake 4: using one box size for everything. Pomodoro for everything means deep work is constantly interrupted and small stuff is artificially stretched.
Mistake 5: never checking. Without comparing planned against actual, the boxes stay as wrong as the estimates they came from. Two weeks of measurement fixes them.
Timeboxing in a team
Two things change once several people are involved:
Visibility. Focus boxes belong in the shared calendar — not with task detail, but as occupied time. A team that cannot see each other's focus time will book meetings into it, and then there is none.
Response windows. Timeboxing only works alongside an agreement about how fast answers are expected. "Within four hours" is compatible with focus blocks; "immediately" is not. Making that agreement explicit does more than any app.
When automation earns its place
Timeboxing by hand costs ten to fifteen minutes a day. That is well spent — until three things come together: many meetings, many projects, and a correction factor that differs per kind of work. Then the arithmetic outgrows its benefit.
That is what Balane Plan is built for: it reads the real gaps in your calendar, subtracts the learned recovery time after meetings, sets focus blocks between 25 and 120 minutes, batches small stuff into the leftovers and caps context switches at seven a day. Divisible tasks are split and numbered; indivisible ones are never cut. And whatever no longer fits is printed under the plan as a quantity, instead of quietly disappearing.
In short
Timeboxing is not a productivity technique, it is a decision technique. The calendar is only the tool; the actual work happens at the end of the box, when you decide instead of drifting on.
If you are starting, start small: two boxes a day, both for the most important work, both with a real decision at the end. That lasts longer than a fully booked calendar abandoned on Wednesday.
Common questions
What is the difference between timeboxing and calendar blocking?
Calendar blocking reserves time for a topic without forcing an end — the block is a place in the calendar. Timeboxing adds a hard limit and a decision at the end: done, continue, or cut differently. Without that decision a timebox is just an appointment with yourself.
How long should a focus block be?
Between 25 and 120 minutes. Under 25 minutes the spin-up time dominates; over 120 minutes quality drops measurably and the break gets taken anyway, just without control. For demanding work, 90 minutes is a good default.
What do I do when the box runs out and I am not finished?
Stop and decide. Write two sentences on where you are and what the next step is, then either set a second box or re-cut the task. Working on without deciding devalues the measurement your next estimate depends on.
Does timeboxing work in a heavily interrupted job?
Yes, with smaller boxes and declared response windows. In support work you plan two or three short focus boxes a day and treat the rest deliberately as response time — instead of pretending the whole day is plannable.