Pomodoro vs deep work: when each works

I gave the first version of this article, published in 2024, a rather confident title: "Pomodoro technique is killing your Deep Work." I still think a timer can interrupt good work. But I made Pomodoro sound like the enemy, when the question is really what kind of work is in front of you.

If you're trying to begin something you've been avoiding, 25 minutes can feel possible when an open afternoon does not. If you're halfway through a difficult argument or a piece of code, the same timer may ring at exactly the wrong moment. Both things can be true.

What Pomodoro is good at

The familiar version is 25 minutes of work followed by a short break. Francesco Cirillo's full Pomodoro Technique also includes planning, handling interruptions and recording what happened. Reducing it to a kitchen timer is unfair to the method.

The timer has a real advantage, though: it makes starting cheap. You are not committing to finish a proposal or solve an entire technical problem. You are agreeing to work for one short interval. That can be enough to get past the part where the task looks larger than it is.

A fixed interval also makes sense for work with natural stopping points: clearing a few messages, reviewing a document, or doing a first pass over an unfamiliar problem. The bell gives you a chance to decide whether to continue. It does not have to make that decision for you.

Where the timer gets in the way

Some work takes time just to load into your head. You have to remember the constraints, read what you wrote yesterday, and work out why the obvious answer was wrong. Only then do you get to the difficult part.

If that is what the first 25 minutes are doing, stopping because the interval ended can be costly. You may spend the next interval reconstructing the same context. This is especially noticeable in writing, design and complex technical work, but it is not a rule about professions. A short session can be deeply focused; a three-hour session can be an elaborate way of avoiding a decision.

That is why I no longer think of "Pomodoro vs deep work" as a contest between 25 minutes and two hours. Deep work describes the attention the task requires. Pomodoro supplies a way to manage time. Sometimes they fit together. Sometimes the clock is in the way.

Cal Newport has made a similar point about breaks during deep work: a pause can help you continue, but some kinds of breaks pull your attention out of the problem. The question is less whether the clock reached 25 minutes than what the interruption does to the work.

How I choose a session length

I start with the work, not the timer. What would be different when I stop? If the answer is "I will have reviewed the draft and left comments," a short interval may be enough. If the answer is "I will have decided which architecture to use and written down why," I would leave more room for the problem to unfold.

When starting is the hard part, I can still use 25 minutes as an entrance. If I am finally making progress when it ends, I continue to a sensible stopping point. When the work has a clear boundary, I take the break. The timer is useful precisely because I am allowed to disagree with it.

There is another question after the session: what changed? Completing four intervals tells me I showed up for roughly two hours. It does not tell me whether I finished the argument, found a flaw in the plan, or spent the afternoon polishing its title. I wrote more about how to track deep work without mistaking hours for progress.

trydeepwork lets you protect a longer session around a task and see, at the end of the week, which commitments were met and which objectives received your time. It cannot tell you whether the work was good. That part still belongs to you. If your problem is protecting a piece of important work beyond the first 25 minutes, this is how the app works.