Pomodoro not working? Seven places it comes apart
It is the third Thursday since you started. The timer is still on the desk, next to the notebook you bought for this.
You have set it once since Sunday. That was Monday at 4:50pm, for a task you had already half-finished, so the count would not go to zero.
Nothing dramatic happened. It just stopped being worth the tap.
A timer manages the edges, not the middle
Every failure below is the same failure wearing a different coat. People expect the timer to handle the work, and a timer cannot handle the work. It handles two moments — when you start and when you stop — and hands you back everything in between.
That is still a lot. Most bad afternoons are bad because they have no edges. But it means the setup you do before the first session matters more than anything you do during it.
Why does it work for two weeks and then stop?
Because the first fortnight runs on novelty, and novelty pays for a great deal of bad setup. When it wears off you are left with whatever you actually built.
If what you built was a timer with a vague task attached and a phone within reach, week three is when you find out.
Seven places that setup goes wrong.
1. You skip the break because it is going well
You start at 9:00. At 9:25 the sentence is finally moving, so you carry straight on. Same at 9:50. By 10:40 you have read the same paragraph three times and been to the fridge twice, and you cannot point to the moment it turned.
Take the break at the ring, and take it away from the screen. Stand up, refill the glass, look at something more than two metres away. If five minutes feels wasteful, take three — but leave the chair, because the chair is the thing your body is measuring.
2. Your task is too big to name in one sentence
The scrap of paper says thesis. Twenty-five minutes later it still says thesis, and you spent eleven of those minutes deciding which part of the thesis this was supposed to be.
Write the task as one sentence with a verb and an object: “Draft the 200-word method summary.” If your sentence needs the word and, you have written down two tasks and you are allowed to pick one. The test is not tidiness — it is that a vague task makes you do the planning inside the session, on the clock, badly.
3. You let a second window into the session
The timer is running and Slack is open in the other half of the screen, because the client might have replied. You check at minute four. You are still there at minute fifteen, and the reply you read was one line long.
Sophie Leroy’s work on attention residue (Organizational Behavior and Human Decision Processes, 2009) found that switching away from a task before it is finished leaves part of your attention behind, degrading the next thing you do. Those were short lab tasks, so treat the size of the effect as unsettled — but the direction matches what the rest of your morning feels like. One window, one task, and every stray thought goes on the paper instead of into a tab.
4. You count sessions instead of outcomes
It is Friday. The app says 22 sessions this week and you feel reasonably good about that, right up until you remember the invoice never went out.
The count is real information — it tells you which days had shape. It is not a result. Write the intended outcome next to the number when you set up: 4 sessions → intro drafted and sent. At the end of the week the honest question is not how many rings closed, it is which of those outcomes exist now.
5. The phone is both the timer and the problem
You pick up the phone at 2:00 to start a session. At 2:00:14 you are reading a notification that arrived during lunch. You have not started anything, and the timer is not running, and you have already spent the freshest fourteen seconds of the afternoon.
This one has a real double edge. The phone is the most convenient timer you own and the most expensive object in the room to touch. Two ways out that both work: use a separate timer and put the phone across the room, or use the phone but make the session the only thing it will show you — blocking your usual distractions for the length of the session, so that the timer and the temptation are no longer one tap apart.
6. You are protecting a perfect streak
Day 31 is a travel day. You do not get a session in, and the number resets. On day 32 you do not open the app at all, and on day 34 you delete it, which is a strange amount of feeling to have about a counter.
A streak is useful when it is a floor and poisonous when it is a trophy. Define it so it survives a bad day: one session counts, ten minutes counts, and a missed day is a missed day rather than the end of the project. Streaks that actually hold tend to be the ones with a deliberately low bar and no drama attached to breaking them.
7. You never look at the week
It is Friday at five. Somebody asks when you do your best work and you say “mornings, I think,” which is what you said last year, and you have never checked.
This is the cheapest fix on the list and the one nobody does. Six minutes, Friday, with your session history open. Two questions: which two hours this week were the good ones, and what was different about them? Do it four weeks running and you will know something about your own days that no article can guess for you — often something inconvenient, like that your good hours are at 7am and you have been giving them to email.
When it is not the mistakes
Sometimes the method is the wrong shape for the work, and grinding harder at it is just a slower way of quitting.
Your calendar is confetti. If the gaps between meetings are eighteen minutes, the technique will mostly measure the gaps. Fix the calendar first; no interval survives an afternoon chopped into eighteen-minute pieces.
The work has a long warm-up. If it takes twenty minutes to load a problem into your head — most code, most writing, most design — a bell at minute 25 arrives roughly when you became useful. Move to fifty or ninety minute blocks, which is what deep work blocks are for, or drop the fixed bell entirely.
The problem is not attention. Three bad weeks in a row after a run of good ones usually means sleep, illness, or too much work, in that order. A timer will faithfully measure all three and fix none of them.
And if the interval itself keeps feeling wrong, the number was never the point — twenty-five came from one student’s kitchen in the 1980s and was always meant to be adjusted.
Fomodo runs the timer, shields your distracting apps for the length of a session, and keeps the history so Friday takes six minutes instead of twenty. What it deliberately does not have is a shared study room or a leaderboard. There is nobody else in the app. If what gets you started is another person visible on a screen, working while you work, this is not that app and we are not going to build it.
The part we did fuss over: the running session sits in the Dynamic Island with buttons on it. The most common reason to pick the phone up mid-session is to see how long is left, and now that question is answered before you unlock anything.
Six of these seven are setup, done once, before you start. The seventh is six minutes on a Friday.
