The Pomodoro Technique Is Overrated — Here's What I Do Instead

Twenty-five minutes is great for shallow work and terrible for the stuff that actually matters. A simple alternative I've used for two years.

Pomodoro is the productivity advice everyone gives because it's the easiest to explain. Set a timer. Work 25 minutes. Rest 5. After four rounds, take a longer break. Done. It fits in a tweet. It has the comforting structure of a recipe. And for a particular kind of work, it really does help.

The problem is that the work it helps with isn't the work that actually moves your week forward. After two years of running a different system — and watching my output go up rather than down — I'm convinced the Pomodoro Technique is the most overrated productivity tool of the last decade. Here's why, and what I do instead.

Why Pomodoro Falls Apart for Deep Work

Writing, designing, coding a hard feature, working through a strategy problem — these activities have what researchers call a warm-up cost. It takes roughly 15 to 20 minutes of focused effort before your brain fully loads the context: the variables, the constraints, the half-formed ideas, the dead ends you've already ruled out.

Pomodoro asks you to stop precisely as that loading completes. Twenty-five minutes in, you're finally in the zone. The timer rings. You take a five-minute break, get distracted by a notification, and come back to a cold cache. You've spent your warm-up budget and gotten almost none of the deep work it was supposed to enable.

Where Pomodoro genuinely works

I'm not arguing it's useless. For shallow work — inbox triage, ticket grooming, expense reports, content reformatting, anything that has a clear start and end inside one screen — Pomodoro is excellent. The 25-minute box prevents the task from sprawling and the 5-minute break prevents you from binging too long on something that drains you.

If most of your job is shallow work, ignore this article and keep Pomodoro-ing. If most of your job is the kind of work people pay you the real money for — the thinking, the building, the deciding — read on.

The 90/20 System I Actually Use

I run what I call the 90/20: one 90-minute block of single-task work, followed by a real 20-minute break away from any screen. The math isn't sacred — what matters is the structure. A block long enough for your brain to load, plus a break long enough for your body to reset.

What a 90-minute block actually looks like

Phone in another room. Slack quit, not minimized. One tab, one document, one problem. I write the specific goal of the block on a sticky note before I start — not "work on the report", but "draft the methodology section, end to end, ugly is fine."

The first 15 minutes feel slow. The next 60 feel like nothing — that's the zone Pomodoro keeps stealing from you. The final 15 are when I do the second pass on what I just wrote, because I'm still warm enough to see it clearly.

What a 20-minute break actually looks like

This is where most people get it wrong. The break is not for catching up on Twitter or answering "quick" Slack messages — both of those re-engage the same shallow-attention system the deep block just rested. The break needs to be physically different: a walk, stretching, real food, conversation with another human, anything that gets you out of the chair.

Two of these 90/20 cycles per day is a serious creative output. Three is a luxurious week. I've never managed four without one of the blocks turning into something I had to throw away.

Designing Your Own Rhythm

The point of the 90/20 isn't the exact numbers — it's matching the rhythm of the timer to the rhythm of the work. If you write long-form fiction, you might need 120/30. If you do design reviews, 60/15 might be perfect. The questions to ask aren't "what's the optimal block length?" but:

• How long does it take you to fully load the context of this kind of task?
• How long can you sustain that loaded state before quality drops?
• How long does your body actually need to feel reset?

Once you start watching yourself for those answers — even casually, for a week — you'll converge on a rhythm that's specific to your work. That rhythm is going to look almost nothing like 25/5.

The Takeaway

Pomodoro isn't wrong; it's just aimed at the wrong target. If you treat all work as if it were the same and try to slice it into identical 25-minute pieces, you'll do okay at the easy stuff and quietly mediocre at the hard stuff. Trade the universal timer for a rhythm that respects how long your brain actually needs to warm up — and protect that rhythm fiercely. The best week of work I've had this year had only six deep blocks in it. That's the entire output that mattered.