Most to-do lists have a fundamental flaw: they tell you what to do but not when to stop. You work until a task feels done — which usually means working until you're either satisfied or exhausted. Timeboxing fixes this with one rule: every task gets a fixed duration, and you stop when it ends.
That constraint is the whole point. Here's how to apply it.
Plan the night before, not the morning of
The worst time to decide what to work on is the moment you sit down at your desk. By then you're already context-switching, checking notifications, and burning decision-making energy before you've done anything productive.
Spend 10 minutes the evening before. Write down every task you need to move forward tomorrow. Estimate how long each one actually takes — not how long you'd like it to take. Then stop. Don't plan the whole week. Just tomorrow.
Assign a timebox to every task
A timebox isn't a deadline. It's a commitment to work on this specific thing for this specific duration. The distinction matters: a deadline can be missed or extended. A timebox just ends.
Practical starting points:
- Email and admin: 15–20 minutes
- Writing first drafts: 30–45 minutes
- Deep work — coding, design, analysis: 45–90 minutes
- Meetings: 25 or 50 minutes (never a full round number)
Resist the urge to be optimistic. If you've never written a 1,000-word document in 20 minutes, don't plan for it.
Start the timer. Work only on that task.
When the timer starts, the only job is the task in front of you. Not Slack. Not a "quick" email. Not checking something that just came to mind. The constraint is the point — it's what makes the technique work.
If you finish early, use the remaining time to improve what you've done, or sit with it and think. You don't start the next task early. That defeats the structure.
When the timer ends, stop — even if you're mid-sentence
This is the hardest part. The natural impulse when you're almost done is to push through. Don't. Stopping at the timebox boundary does two things: it tells you whether your estimate was accurate, and it creates a genuine break before the next task. Both make you better over time.
If a task isn't done, schedule a second timebox for it. That's fine — it's information about how long this type of work actually takes you.
How long should a timebox be?
The research on sustained focus points to 25–90 minutes as the effective range for most people. Under 25 minutes and you barely get into the work. Over 90 minutes and quality drops regardless of how motivated you feel.
Start with 30–45 minutes and adjust from there. Some tasks will tell you they need more; some will be done in 20. Let the pattern emerge over a week or two rather than guessing upfront.
Breaks aren't optional
After each timebox, take a real break. Not "scroll my phone for 5 minutes" — stand up, move, look at something that isn't a screen. The length should be roughly proportional to the work session: 5–10 minutes after a 30-minute timebox, 15–20 minutes after 90 minutes.
Skipping breaks to get more done is the fastest way to make the whole system collapse by 2pm.
Review for 5 minutes at the end of the day
This is where most timeboxing systems fall short: they focus on execution and skip the feedback loop. Take 5 minutes at the end of the day and ask:
- Which estimates were accurate?
- Which tasks took twice as long? Why?
- What would I plan differently tomorrow?
After two weeks of this, your estimates become dramatically more accurate. After a month, your days become genuinely predictable in a way that's hard to achieve any other way.
Getting started on Mac
You can start with a kitchen timer — the habit matters more than the tool. But if you want something designed specifically for this, NovaFocus is a native macOS menu bar app built around timeboxing. You create a task queue with individual durations, start the timer, and the countdown lives in your menu bar so you always know how much time is left without switching apps. Flow mode handles breaks automatically.
The core idea remains the same either way: finite time, one task, full attention. Everything else is implementation detail.
Further reading: If you're comparing timeboxing to the Pomodoro Technique, see Timeboxing vs. Pomodoro: Which One Actually Works Better?
More from the blog
← All articles