The 50/10 pomodoro is 50 minutes of focused work followed by a 10-minute break, with a longer break of 20 to 30 minutes after four sessions. It keeps the same 5:1 work-to-break proportion as the classic 25/5 and doubles the unit. It’s the standard fix for work that takes fifteen minutes to get going.
The warm-up problem it solves
Think about what happens in the first ten minutes of debugging something you haven’t touched in a week. You’re reading code, rebuilding the shape of the problem, remembering what you already ruled out. None of that is progress. All of it is necessary before progress is possible.
At minute 25 you’re finally useful. And the bell goes.
Do that four times and you’ve paid the warm-up four times over and had maybe forty minutes of real work out of a two-hour block. Run the same work at 50 minutes and the warm-up gets paid once per session instead of once per ten useful minutes.
That’s the whole argument. If your work doesn’t have a warm-up (flashcards, email, data entry), it doesn’t apply and 25/5 is fine.
Who it suits
Programmers. Almost any non-trivial change involves holding several files in your head at once, and that state is expensive to rebuild.
Writers editing rather than drafting. Restructuring an argument means holding the whole argument. Drafting is often fine at 25.
Students on problem sets and past papers. A maths question can take twenty minutes on its own. See pomodoro technique for studying.
Anyone who finds 25-minute breaks disruptive. Two breaks an hour is a lot of standing up if you were already concentrating fine.
Who should stay at 25
If your problem is starting, not sustaining, 50/10 will make things worse. A 50-minute commitment is a bigger ask, and on the day you’re avoiding a task you’ll simply not press start. Twenty-five minutes is deliberately small enough to be accepted by a reluctant person, which is the main thing 25/5 has going for it.
The same applies if you regularly abandon sessions halfway. Finishing shorter sessions builds something that abandoning longer ones does not.
Running a day of it
Four sessions of 50/10 with a 20-minute long break take 3 hours 50 minutes. Two of those blocks with lunch between them is a genuinely full working day of focused work, and more than most people manage.
A realistic shape:
9:00 Block one. Sessions on the hardest thing you have. Ten minutes off between each, away from the desk.
Long break. Twenty to thirty minutes. Eat, go outside.
13:30 Block two. Different kind of work if you can, because four more hours of the same thing is where quality drops.
If you only get one block, put it in the morning and defend it. One protected block beats a day of half-attention, and everyone who has tried both knows it.
The 10-minute break is the part that fails. It’s long enough to start something and short enough that the something isn’t finished when you get back. Go for a walk, make coffee, do nothing. Don’t open anything with a feed. Our pomodoro break ideas page has options that fit ten minutes cleanly.
50/10 versus 52/17
Same idea, different break. 52/17 came out of DeskTime’s 2014 analysis of its most productive users, and the notable part was never the 52; it was that those users took seventeen minutes and disconnected properly.
Choose 50/10 if you want round numbers and a day that maps onto the hour. Choose 52/17 if you keep cutting your breaks short, because seventeen minutes is long enough to leave the building, and ten is not.
More ratios, with the time each costs, are on pomodoro intervals.
FAQ
What is the 50/10 rule?
Fifty minutes of uninterrupted work on one task, then a 10-minute break away from the desk, with a longer break after four sessions. It’s a variation on the classic pomodoro for work that takes time to get going.
Is 50/10 better than 25/5?
Better for work with a long warm-up, such as debugging or restructuring a document. Worse if your problem is starting at all, because a 50-minute commitment is harder to accept on a bad day. Most people should use both, matched to the task.
How many 50/10 sessions can I do in a day?
Six is a heavy day and eight is unusual. Four sessions with a long break take 3 hours 50 minutes, so two blocks with lunch between them fills a working day. Beyond that, quality falls off faster than the session count suggests.
Should I take the full 10-minute break?
Yes, and away from a screen. The break is where the fatigue from 50 minutes of concentration actually clears. Ten minutes at the desk reading something else gives your brain the same job it just had and carries the fatigue into the next session.
What long break goes with 50/10?
Twenty to thirty minutes after four sessions. After four 50-minute sessions you need food and daylight more than you need another ten minutes. Treat it as a proper stop, not a stretch.
Give the longer unit a try today: start a 50/10 session with a 20-minute long break.