The 52/17 rule: work 52 minutes, then break for 17
The 52/17 rule means 52 minutes of focused work, then a 17 minute break away from the screen. Where it came from, how it compares to Pomodoro, how to try it.
The 52/17 rule says to work in focused blocks of 52 minutes, then take a real break of 17 minutes away from the screen, and repeat that through the day. It is less a law than a rhythm: about an hour of proper work, a proper rest, and back again.
The numbers come from one company looking at its own users, not from a lab, and that matters when you decide how seriously to take them. Below: where the idea came from, what it does and doesn't show, how it stacks up against the Pomodoro technique, and how to test it on a Mac for a week.
Where the 52/17 rule came from
The rule is usually credited to a time tracking software company that, in 2014, went through the data its app had collected from its own users. It picked out the small group its software rated as most productive and found that they didn't work longer days than everyone else. On average, they worked in stretches of about 52 minutes and then stopped for about 17. The finding was widely reported that year, and "52/17" has been passed around ever since.
Two details are easy to miss.
- The tracker could only see the computer. "Productive" meant time spent in apps the software counted as work, and a break meant time when the computer sat unused. So the 17 minutes were, by definition, time off the screen.
- The numbers were averages. Nobody in that data was working to a 52 minute timer. The most focused people simply tended to fall into that pattern on their own.
The same company later reported a different, longer rhythm from newer data. That is a useful reminder that the exact figures are not magic. What has held up is the shape: a solid block of work, then a break long enough to actually count.
Does the 52/17 rule work?
It works in the way that matters most for most people: it makes breaks happen. Whether 52 minutes beats 45 or 60 is another question, and nobody has tested that properly. The original finding was an observation, not an experiment. It may be that people who are already good at their jobs feel able to take long breaks, rather than the long breaks making them good.
Research on breaks in general is more encouraging, if fairly modest. It broadly suggests that regular breaks help people feel less tired and keep their work steadier through a long day. There is more on that in do breaks make you more productive.
The rhythm itself has a few things going for it:
- 52 minutes is long enough to warm up. Writing, code, design and analysis often take ten or fifteen minutes before you are properly into them. A short block can end just as the work starts to flow.
- It is short enough to stop before you fade. You end the block with something left in the tank, which makes the next one easier to start.
- 17 minutes is a real break. It is long enough to leave the room, walk around the block or make something to eat, which a two minute pause is not.
It suits people who control a good part of their own day. It suits shift work, support queues and meeting-heavy days much less well, and that's fine. Use it for the hours you can shape.
How does 52/17 compare to Pomodoro?
The Pomodoro technique is the best-known timed method: 25 minutes of work, a five minute break, and a longer break after four rounds. The two are closer than they look.
| Pomodoro | 52/17 | |
|---|---|---|
| Work block | 25 minutes | 52 minutes |
| Break | 5 minutes, then 15 to 30 after four rounds | 17 minutes, every time |
| Where it came from | Francesco Cirillo, late 1980s | A software company's user data, 2014 |
| Good for | Starting a task you are avoiding, short tasks, learning to focus | Writing, code, design and other work that needs time to warm up |
| Weak spot | 25 minutes can cut deep work short | 17 minutes every hour is hard to take in a busy office |
Add up the rest and the difference shrinks further. Over an eight hour stretch at the desk, 52/17 gives you about seven rounds and close to two hours of breaks. Pomodoro, with the long breaks taken properly, lands in roughly the same place. Both methods ask for about the same total rest. They just slice it differently: Pomodoro in many small pieces, 52/17 in fewer, bigger ones.
If neither length feels right, a 50 minute block with a 10 minute break sits between them and fits neatly on the hour.
Is 17 minutes too long for a break?
This is a common objection, and in many workplaces it is a fair one. A 17 minute break every hour can look like slacking, even when it isn't.
A few ways to make it fit:
- Make the break useful but not screen work. The original breaks were simply time away from the computer. A phone call taken standing up, a chat with a colleague, reading something on paper or sketching an idea all count.
- Fold chores into it. At home, 17 minutes is a load of washing, a short walk to the shop or making lunch.
- Shorten it on busy days. Keep the 52 minute block and take 10. The block is the part that changes how you work; the break length is easier to flex.
- Fit rounds around meetings. One round is 69 minutes, so a 90 minute gap between calls holds one round with a little room to spare.
How to try the 52/17 rule on a Mac
You need a timer you will actually notice, and a week of honest attention.
With the Clock app
Clock came to the Mac with macOS Ventura and sits in the Applications folder.
- Open Clock. You can also press
Command-Space, type Clock and press Return. - Go to Timers, set 52 minutes, give it a label such as "Work", and start it.
- When it ends, start a 17 minute timer labeled "Break" and get up from the desk.
- Clock keeps your recent timers, so after the first day both lengths are one click away.
If you use a Focus mode while you work, check that Clock is allowed to notify you in that Focus, or the end of a block is easy to miss.
Keep a note for a week
On paper or in a note, write one line per block: did you make it to 52 minutes, and if not, what pulled you out. At the end of the week the pattern is usually obvious. Some people find they drift at 40 minutes and switch to 45/15. Others find 52 too short for real work and try 60 or more. The best rhythm is the one you keep.
What to do with 17 minutes
A break that happens on your phone is still screen time, and still attention. Since the whole idea came from time spent away from the computer, try to step away from screens altogether. Some good uses of 17 minutes:
- Walk outside, or around the building, without your phone in your hand.
- Refill your glass and drink half of it before you sit down. Eat something if it's been a while.
- Do a few stretches for your neck, shoulders and back.
- Stand at a window and find the farthest thing you can see, to give your eyes a rest from close work.
- Tidy one thing, so the desk you come back to is easier to work at.
If you sit back down feeling slightly bored, the break probably did its job.
Where Notchpals fits
Notchpals doesn't run a 52/17 timer, and it won't count your 17 minutes. It is a crew of characters who drop down from the notch with nudges, and three of those nudges happen to sit right on this rhythm.
The closest match is a focus session. With a Focus character in your crew (Bolt, Debug or Jot), click the Notchpals eyes in the menu bar, choose "Start a focus session" and pick 50 minutes, two short of a full 52/17 block. While it runs, only Focus moments, a nearly flat battery and a meeting about to start can visit. When the 50 minutes are up, the character comes back to close the session, and that is your cue to leave the desk:
DebugSession over. Rest your brain. I'll keep staring at the screen. My thing.
Start a 17 minute Clock timer on your way out if you want the break timed as well.
If you skip the session and simply forget to stop, a Movement character such as Nick, a white spitz, steps in after close to an hour of unbroken sitting. That lands only a few minutes after a 52 minute block would have ended.
Meetings are where timed blocks usually fall apart. If you allow calendar access, a Schedule character like Walter, a walrus with long tusks and longer complaints, comes by 3 to 10 minutes before the next meeting. It sees start times only, nothing about what the meeting is or who is in it. That visit is a good moment to end a block early rather than walk into a call mid-thought:
WalterShip's bell. Your next thing starts soon. All hands on deck.
More on meetings and the workday
Meetings and the workdayTime blindness at the computer: why hours vanish and what helpsWhy an hour at the Mac can feel like ten minutes, and the visible clocks, timers, planned transitions and well-timed nudges that bring you back to the time.
Meetings and the workdayTime blocking in the Mac Calendar app: a setup that worksHow to time block with Calendar on a Mac: a separate calendar for blocks, colors that mean something, repeating blocks, real breaks and a quick morning review.
Meetings and the workdayWhat to do in the five minutes before a meetingA five-minute routine before any meeting: the agenda, the right windows, water, a stretch, a slow breath, and why an early nudge beats one on time.

