The DeskTime 52/17 Study: What the Top 10% Actually Do

DeskTime is a productivity tracking company. In 2014, they published an internal analysis of how their highest-output users structured their work day. The finding was that the top 10% of users by productivity averaged 52 minutes of focused work followed by 17 minutes of rest. The pattern is now widely cited as the 52/17 rule and is the most common alternative to the 25-minute Pomodoro Technique.

The study is one company's user data, not a peer-reviewed controlled trial. It shows what top performers happened to do; it does not prove that doing this would make a different person a top performer. But the directional finding (longer focus blocks than Pomodoro, with proportionally longer breaks) shows up across multiple research streams including ultradian rhythm work and NIOSH ergonomics studies. The 52/17 rhythm is worth taking seriously even with the methodology caveats.

This post covers what the DeskTime study actually was, why the 52/17 rhythm works for many knowledge workers, and how to apply it without overinterpreting the data. For other research-backed intervals, see our deep-dives on the 25-minute Pomodoro origin and the 90-minute ultradian cycle.

What the DeskTime study actually was

DeskTime is a time-tracking SaaS that runs in the background and logs which apps users have in focus throughout the work day. By "productive" they mean time spent in apps the user has classified as work-related (the user defines what counts as productive vs distracting in their account settings).

The 2014 analysis pulled data from their user base, ranked users by aggregate productive minutes per day, and examined the work pattern of the top 10%. The pattern that emerged was an average of 52 minutes of continuous productive app time followed by 17 minutes away from those apps before another productive block began. The finding was published as a blog post and picked up by mainstream productivity press, which is how the 52/17 number became widely cited.

The honest framing is "top performers tend to take a 17-minute break every 52 minutes." Not "if you take a 17-minute break every 52 minutes you will become a top performer."

What the methodology shows and does not show

What it shows

• A correlation between productive output and a specific work-rest pattern in DeskTime's user population.
• The pattern is consistent across enough users that it is unlikely to be random.
• The work-rest ratio (roughly 3:1) is larger than the Pomodoro ratio (5:1) — top performers rest proportionally more than the Pomodoro Technique recommends.

What it does not show

• Causation. Top performers might take longer breaks because they have the seniority and autonomy to do so, not because the breaks make them top performers.
• Industry generalizability. DeskTime's user base skews toward knowledge workers in tech and creative industries. The pattern may not apply to manufacturing, healthcare, education, or trades.
• Optimal interval for any individual. 52 is an average. Some top performers in the data had shorter cycles, others had longer. The mean is not a personal recommendation.

The right way to read the study is as evidence that intervals longer than Pomodoro can produce strong output. The wrong way is to treat 52 minutes as the universal optimal interval for everyone.

Why 52/17 produces more output than 25/5 for many tasks

The mechanism is warmup cost, also called attention residue or task-loading time. Most knowledge work requires 5 to 15 minutes of mental setup before useful output begins (loading the relevant context, recalling where you left off, rebuilding the mental model of the task). This warmup is a fixed cost per work block, regardless of how long the block is.

For a 25-minute Pomodoro, if your warmup is 10 minutes, you have 15 minutes of productive work per block. Across 4 blocks (the canonical Pomodoro cycle), you produce 60 minutes of useful work in 100 minutes of clock time, plus 15 minutes of breaks.

For a 50-minute block with 10 minutes of warmup, you produce 40 minutes of useful work per block. Across 2 blocks (the same 100 minutes of clock time), you produce 80 minutes of useful work plus 17 minutes of break (using the DeskTime ratio).

The 52/17 rhythm produces 33% more useful work per hour for tasks with non-trivial warmup. The math gets even more lopsided as warmup time increases. For deep cognitive work where warmup is closer to 15 minutes, 52/17 produces nearly twice the useful output of 25/5.

What other research backs the 52/17 finding

The DeskTime number is one data point. The directional finding (longer blocks with proportional breaks) is supported by several other research streams.

• Kleitman's ultradian rhythm research. The body cycles through approximately 90-minute periods of high and low alertness. The 52-minute interval falls inside one full ultradian cycle, which means a 52-minute block is consistent with riding a single alertness peak. See our ultradian rhythm deep-dive.
• K. Anders Ericsson's expert-performance research. Elite practitioners across domains (musicians, athletes, chess players) cap focused practice sessions at around 90 minutes per session. 52 minutes fits comfortably inside this cap.
• NIOSH and Cornell ergonomics research. Workers given short breaks at least once per hour reported less musculoskeletal and eye-strain symptoms while maintaining productivity. 52 minutes is just under the hourly threshold, which keeps users in the safe ergonomic zone.

The 52/17 finding is consistent with all three. It does not violate any of them. That consistency is part of why it gets cited despite the methodology limits.

How to apply 52/17 to your work

The technique is simple to start.

1. Set a 50 or 52-minute work timer. Most break-reminder tools have a 50-minute preset. Doggy Break ships with a 50-minute preset specifically for this rhythm and shows the DeskTime backing in the settings panel.
2. Set a 17-minute break timer (or 15 if your tool snaps to 5-minute increments). The exact number is less important than the proportion. The break should be roughly 25 to 30% of the work block.
3. Use the break for actual rest. Stand up. Look at something more than 20 feet away. Drink water. Do not check email; that is more screen work, not rest.
4. Run the rhythm for two weeks before judging. One week is too short. The benefit shows up as cumulative output across days, not within a single day.

Benefits of the 52/17 rhythm

1. Lower warmup-to-output ratio

The biggest practical benefit. Each 50-minute block has the same fixed warmup cost as a 25-minute block, but produces twice as much useful work after warmup. For knowledge work with non-trivial warmup, the math compounds across the day.

2. Better fit for deep work

Writing, coding, design, and analysis benefit from longer uninterrupted blocks. Cutting at 25 minutes interrupts the build-up to flow. 50 minutes is long enough that flow can establish and produce output before the break.

3. More restorative breaks

17 minutes is long enough to actually rest, not just stretch. You can step outside, drink water, look at something other than your screen, and have your eyes and mind genuinely recover. Five-minute Pomodoro breaks are barely long enough to leave the desk.

4. Reduced afternoon decision fatigue

Fewer cycles per day means fewer break-decision moments. The 52/17 rhythm produces approximately 6 cycles in an 8-hour work day; a 25/5 Pomodoro produces 12. Each cycle decision (do I really need a break right now? what should I do during the break?) is a small drain that compounds.

5. Better aligned with calendar blocks

Calendar tools default to 30 and 60-minute blocks. A 52-minute work block fits comfortably inside a 60-minute calendar slot with the 17-minute break overlapping the next slot's start. 25-minute Pomodoros fragment calendar blocks awkwardly.

Frequently Asked Questions

Is the DeskTime study peer-reviewed?

No. It was an internal analysis published as a marketing blog post by DeskTime. Treat the 52/17 number as one data point rather than scientific consensus. The directional finding (longer than Pomodoro, with proportional breaks) is supported by other research; the specific 52 and 17 numbers are not.

What if I cannot focus for 50 minutes straight?

Two possibilities. First, you may be in a high-distraction environment where a shorter Pomodoro interval is a better fit. Second, you may have a task with very low warmup cost where the 25-minute rhythm produces equivalent output. Try 25-minute Pomodoros for two weeks; if you finish blocks consistently feeling like you were just getting started, switch to 50.

Does 52/17 work for meetings?

Sort of. Meetings already have natural break structures (between meetings, during scheduled breaks). The 52/17 rhythm is most useful for sustained solo work. For a day full of meetings, focus on protecting the gaps between meetings as actual rest rather than email triage.

Why exactly 17 minutes for the break, not 15 or 20?

17 is what came out of the DeskTime data; there is nothing magical about it. 15 is fine. 20 is fine. The proportion (roughly 3:1 work-to-break) matters more than the exact number. Round to whatever your timer tool supports.

Can I combine 52/17 with body doubling apps like Focusmate?

Yes, and many users do. Schedule a 50 or 75-minute Focusmate session, work for the full duration, then take a 15 to 20-minute break before the next session. The body double provides accountability; the long block produces deep work; the break is restorative. We covered this combination in our ADHD anti-procrastination guide because it works particularly well for executive-function challenges.

Should I scale 52/17 if I work shorter days?

The proportion (3:1) and the warmup logic stay the same regardless of total day length. For a 4-hour focused work day, you would do 3 cycles of 50/17 instead of 6. For an 8-hour day, 6 cycles. The rhythm is per-cycle, not per-day.

Has DeskTime updated the study since 2014?

Not in the same depth. The 2014 analysis is the canonical source. Subsequent DeskTime blog posts mention the 52/17 finding but do not present new analyses with updated numbers. The original is the data; later mentions are summaries.