Timeboxing: decide when to stop before you start

Why does this task never end? You sat down to write a short email, tidy a spreadsheet or plan a weekend, and two hours later you're still at it. One possible reason: you never chose a stopping point.

Timeboxing gives you that point. Before you start, decide how much time the task gets, what a good-enough result looks like, and what you'll do when the time's up. Then, when it's up, you stop and judge what you've got, instead of drifting on.

Timeboxing vs time blocking

Timeboxing decides how much time the work gets: "Give the proposal 60 minutes, then stop and assess the draft." Time blocking decides when you'll work: "10:00 to 11:00 is reserved for the proposal."

You can use both in the same session. Reserving 10:00 to 11:00 protects the time; agreeing to pause at 11:00, review the result and deliberately finish, reduce the scope, extend or park it adds the timebox. The distinction is the stopping rule, rather than simply having an end time in your calendar.

Timeboxing at a glance

• What it is: giving a task a fixed amount of time, then stopping when it ends and looking at what you've done.
• The three decisions you make first: the box (how long), the good-enough line (what you're aiming for), and the stop rule (what happens when the time's up).
• The move: deciding when to stop before you start, while you can still judge it calmly.
• Who it helps: anyone whose open-ended jobs, like research, planning, tidying or polishing, quietly take the whole afternoon.

Where it comes from

Timeboxing comes from software projects. The Agile Alliance defines a timebox as "a previously agreed period of time" for working towards a goal. Instead of working until the goal is reached, you stop when the time limit is reached and evaluate what you've done. Its glossary traces the idea to Scott Schultz's rapid prototyping approach in 1988, and to a chapter of James Martin's Rapid Application Development in 1991. Timeboxed iterations then became a distinctive feature of early Agile approaches such as Scrum and Extreme Programming.

The personal version keeps the same rule: the time is fixed, and what you finish is what gets judged. This article focuses on that time limit and the review at its end. For calendar planning and how this differs from Pomodoro and time blocking, see our comparison.

Before you start: set three things

1. The box. Choose how long the task gets, and turn it into a time you'll stop: "until 10:45", not "about an hour". Pick a length you can actually protect from interruptions.
2. The good-enough line. Write one sentence about what a finished-enough result looks like. "An email that says yes and gives the date and the price" is a line. "A great email" isn't.
3. The stop rule. Decide now what you'll do when the time's up. If you've reached the line, you're done. If you haven't, you'll choose one of the options below, and you'll allow yourself at most one extension.

The one-extension limit here is our suggested guardrail for trying the method, rather than a rule of timeboxing itself.

It takes a minute. That minute is the method: the decisions are made by the version of you who isn't yet deep in the task.

When the time's up: stop, review, then choose

Stop when the box ends, even mid-sentence. Look at what you have against your good-enough line, then choose one of these on purpose:

• Ship it. If it meets the line, it's done. Send it, file it or tick it off, even if you can see things you'd polish.
• Extend once. If you're close and the rest really matters, give it one shorter box, and decide its length now. When that one ends, ship, cut or park. No third box.
• Cut the scope. Ship the part that's done and drop the rest, or move the rest to a separate task for later.
• Park it with a next step. If it isn't close, stop anyway and write down exactly where to pick it up. A clear next step makes it easy to come back to.

Why decide before you start

When the time runs out and you're halfway through, "just five more minutes" always sounds reasonable. You can see what's left, you've already put the effort in, and stopping feels like wasting it. Five minutes at a time is how a short task takes the afternoon.

Deciding first means the stop is already agreed. You aren't arguing with yourself at 10:45 about whether to carry on; you're just following the rule you set at 10:00. The good-enough line does the same for quality: it tells you when the work is finished for this purpose, so you can stop polishing.

It's also a direct answer to Parkinson's law, the observation that work expands to fill the time available. A timebox makes the time available smaller, and decides in advance how it ends.

A worked example

Here's a made-up example. Leo is writing the newsletter for the school fair. Last year it took most of a Sunday. This year, before starting, he sets:

• The box: until 10:45, which is 45 minutes.
• The good-enough line: the date and time, the three main stalls, and how to volunteer.
• The stop rule: ship at the line; one 15-minute extension at most.

At 10:45 he has the date, two of the three stalls and the volunteering section. He's close, and the missing stall matters, so he extends once, until 11:00. At 11:00 the stall is in, and he sends the newsletter. The photo he wanted to swap for a better one doesn't make the line, so he parks it: "Ask Maya for the stall photos" goes on his list for next time.

Choosing your box

There's no correct length. Start with what the task deserves, not with how long it took last time. If last time it took all afternoon, that's the problem you're fixing.

For a short job, like a reply, a booking or a quick plan, try 15 to 30 minutes. For a bigger piece, like a draft or a tidy-up, try an hour. Then watch how it goes. If you always hit the line early, shorten the box. If you never get close, the line is too ambitious or the task needs splitting.

When not to timebox

• When it must be finished regardless. If the form has to go in today, a stop rule that says "park it" doesn't help. Use the box to focus, but finish the job.
• When quality really can't be cut. Some work has a fixed standard. Timebox the parts around it, like research or drafting, rather than the final check.
• When you're in a good flow on important work. A box is a tool, not a cage. If you choose to carry on, do it as a deliberate extension, not by ignoring the timer.

Common mistakes

• No good-enough line. Without one, you can't tell whether to ship, so you keep going.
• Silent extensions. Running over without deciding to is just not timeboxing. If you extend, say how long, once.
• Stopping without a next step. A parked task with no note is hard to restart. Write where you got to.
• Boxing everything. Timeboxing suits open-ended jobs. A task with a clear end, like posting a parcel, doesn't need one.
• Treating the box as a deadline for perfection. The box asks "is it good enough?", not "is it perfect?"

How to timebox in dypt

dypt doesn't have a timer, so use your phone or a kitchen timer for the countdown itself. dypt's job is to hold the decisions you make before you start, and what happens after the box ends.

1. Write the box and the line in the task note. Before you start, add a short note: "Until 10:45. Good enough: date, three stalls, how to volunteer." It's there when you check your work at the end.
2. Set a deadline for when the box ends. Give the task a deadline at your stop time and add an At deadline reminder. It's a nudge to stop and review, not a countdown, so keep the timer running too.
3. Record the outcome. If it meets the line, tick it off. If you cut the scope, update the note to say what the smaller task includes and move any remaining work to a new task. Tick off the smaller task once that agreed result is complete. If you park it, add the next step as a subtask, so the next session starts with something clear. If the next step is still too big, AI task breakdown can suggest smaller steps.
4. Box the stuck jobs. From our Do the thing videos: if a job has sat unfinished for days, a timebox is a good way to move it on, either to done or to a clear next step.

Try it today

Pick one task that tends to spread. Before you start it, write down the time you'll stop and one sentence about what good enough looks like. When the time's up, stop, look, and choose: ship it, extend once, cut the scope or park it.

If you'd like your good-enough lines, deadlines and next steps in one place, try it in dypt, free to start.

Next in our Do the thing videos: personal kanban, for limiting how many jobs you have in progress at once.

Sources and further reading

• Agile Alliance, "Timebox"
  The definition, the rule to stop and evaluate at the end, and the idea's history from 1988.
• Pomodoro vs time blocking vs timeboxing
  How the three methods differ, and when to use each.
• Parkinson's law
  Why work expands to fill the time you give it.
• Personal kanban
  Limiting how many jobs are in progress at once.