The Focus Session Length That Actually Matches Your Work
Ninety minutes is not the right block length for every type of work. Here is how to find the one that actually fits.
Someone told you to use 90-minute deep work blocks. Or maybe it was 52 minutes. Or 25. You picked one and it felt wrong and you assumed the problem was you.
It probably was not you.
Block length is not universal. The right session length depends on the type of work, not on a study you read or a system someone else swears by.
Why One Block Length Does Not Fit Everything
Writing a first draft is different from reviewing a contract. Designing a layout is different from reconciling a budget. Some tasks need long uninterrupted stretches to get anywhere meaningful. Others reach a natural stopping point in 30 minutes and then just spin.
Using a 90-minute block for a task that bottoms out at 40 minutes means spending the last 50 minutes pretending to work or doing the task badly to fill the time. Using a 25-minute block for work that takes an hour just to warm up means you never actually produce anything in a single session.
The block has to match the work.
How to Find the Right Length
The most direct method: track it.
For two weeks, run a timer on every focus session. Do not set a target length. Just start, work until you hit a natural stopping point or notice your output degrading, and stop the timer.
After two weeks you will have a real dataset. Look at it by task type. Writing sessions might cluster around 75 minutes. Client review work might consistently end at 35. Admin tasks might be done in 20.
You are not looking for one number. You are building a map.
The Degradation Signal
The moment to watch for is when your output quality drops while your effort stays the same or increases. That is the end of your effective block, even if the clock says you have time left.
Most people push through that signal because stopping feels like quitting. But working through degraded output often means redoing the work later, which costs more time than the break would have.
Tracking time honestly makes this visible. If a two-hour block produces 45 minutes of usable output, that shows up in your logs. You can see it.
Protecting the Block You Find
Once you know your natural block lengths by task type, you can schedule them accurately instead of hopefully.
If deep writing blocks reliably run 70 minutes, book 70 minutes. Not 60, not 90. The accurate number. That precision makes calendar protection easier. You are not guarding a vague "morning block." You are protecting a 70-minute window with a hard start and a hard stop.
Clients and colleagues are also easier to manage when you know exactly what you need. "I am blocked until 10:40" is a real answer. "I am in deep work mode" is not.
What This Does to Your Billable Hours
If you bill hourly, session length accuracy directly affects what you capture. A block that runs longer than you expected and bleeds into transition time often does not get logged fully. You forget the last chunk. Or you round down out of habit.
When you know your realistic block length and you set a timer that matches it, you capture the actual time. Not an estimate. Not a round number. The real number.
Over a month, those small gaps between estimated and actual time add up to real money.
One Adjustment to Make Now
Pick one recurring task type. Writing, code review, client communication, whatever you do most.
For one week, track how long it actually takes before your output noticeably drops. Do not decide in advance. Let the work tell you.
At the end of the week you will have a number. Use that number to set your blocks next week and see if the sessions feel different.
They usually do.
Track your time, bill every minute.
Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.
Free during beta.
Download Time-Trak →macOS + Windows · Floating widget · Auto screenshots