Deep Work Timer: How to Focus for 90-Minute Sessions
How I stopped bouncing between tabs and actually started finishing things.
I used to "work" all day and accomplish nothing. I'd sit at my computer for 10 hours, feel exhausted by evening, and realize I hadn't made real progress on anything that mattered. Email, Slack, quick browser checks, half-finished tasks - that was my day.
Then I read Cal Newport's book and tried 90-minute sessions with zero distractions. No phone. No browser tabs. No "quick checks." Just me and the one thing I needed to do. The first session felt like torture. The second one, I lost track of time and actually finished something.
That's deep work: extended focus on cognitively demanding tasks. Writing code, designing, analyzing data, learning something hard. The stuff that actually moves your work forward but keeps getting squeezed out by the "urgent" noise.
Why 90 Minutes? (It's Not Arbitrary)
I picked 90 minutes because Pomodoro (25 minutes) felt too short. By the time I got into flow, the timer went off. Turns out there's actual science behind the 90-minute mark - your brain runs in roughly 90-minute cycles called ultradian rhythms. Work with this rhythm and you get more done. Fight it and you burn out.
What I Notice in a 90-Minute Session
- First 15-20 minutes: Painful. My brain wants to check something. I resist.
- 20-70 minutes: This is where the magic happens. I forget about time and actually produce.
- 70-90 minutes: Starting to feel it. Good time to wrap up, not start new things.
- After 90 minutes: Diminishing returns. Take a real break or the next session suffers.
The research on elite performers (musicians, athletes, chess players) shows they consistently practice in 60-90 minute sessions before taking breaks. They figured this out intuitively. The science just explains why.
When Pomodoro Fails (And When It Works)
I still use Pomodoro for shallow work - emails, admin tasks, stuff I don't want to spend all day on. But for anything complex? 25 minutes is a joke. By the time I understand the problem, the timer goes off.
| Task | What I Use | Why |
|---|---|---|
| Writing code | 90 min deep work | I need 20+ min just to load context |
| Inbox zero | 25 min Pomodoro | Prevents me from spending 2 hours on email |
| Learning something new | 60-90 min | Understanding builds slowly |
| Admin tasks | 25 min batched | Forces me to be quick |
| Strategic thinking | 90 min | Big picture needs unbroken time |
The problem with switching every 25 minutes: your brain needs time to reload context. For complex work, you might spend 10 minutes getting back into it every time. That's 40% of your Pomodoro wasted on ramp-up.
My Actual 90-Minute Routine
Here's what I actually do (after a lot of trial and error):
Before I Start (2-3 minutes)
- Phone goes in another room. Not airplane mode - another room.
- Close Slack. Actually close it, not minimize.
- Write down ONE thing I'll accomplish this session
- Set the 90-minute timer and commit
During (The Hard Part)
- When I want to check something (and I will), I write it on paper and continue
- First 20 minutes are uncomfortable. That's normal. Push through.
- If genuinely stuck, I change approach rather than task
- The timer handles when to stop. I just focus.
The Break (Actually Take It)
- 15-20 minutes minimum. No screens.
- Walk around. Get water. Look outside.
- I used to skip breaks. Then my second session was garbage. Don't skip.
- Your brain processes while you rest. This isn't wasted time.
If 90 Minutes Sounds Impossible
It did to me too. My first attempt, I lasted maybe 25 minutes before "quickly" checking email. Build up gradually:
Start Here: 45 Minutes
Just practice not touching your phone for 45 minutes. The focus will come. Took me about 2 weeks.
Then: 60 Minutes
You'll notice when focus wavers. Don't fight it - just notice and return. This is the practice.
Progress: 75 Minutes
At this point you'll start experiencing flow. The last 15 minutes are where you'll do some of your best work.
Target: 90 Minutes
2-3 of these per day is all you need. More isn't better - quality drops after about 4 hours total.
Cal Newport says beginners can sustain maybe 1 hour of deep work, experts manage 4 hours. I'm somewhere in between. Two solid 90-minute sessions is a great day. Three is rare.
What I Struggled With (And What Helped)
- The phone urge: Putting it in another room was the only solution. Airplane mode doesn't work - if it's visible, I'll pick it up.
- Random thoughts: I keep a notepad next to me. "Remember to reply to X" gets written down, then I return to work. Otherwise these thoughts bounce around my head.
- Feeling stuck: The first 20 minutes are the hardest. If I push past that, the breakthrough usually comes. Giving up early means I never get to the good part.
- People interrupting: Headphones on = do not disturb. I had to train my colleagues. "If my headphones are on, it better be urgent."
- Afternoon slump: I schedule deep work in the morning. My brain is mush after 3 PM. Don't fight your biology.
Try One Session
Set 90 minutes (or 45 if you're starting out). Put your phone away. Close your tabs. Work on one thing until the timer sounds. The fullscreen mode helps - it's harder to "quickly check something" when the timer takes over your screen.
Start 90-Minute Timer