The Pomodoro Technique gets recommended so often for ADHD that it's become shorthand for "focus method" in general. Twenty-five minutes of work, a five-minute break, repeat four times, then a longer break. It's simple, it's free, and for a lot of people it works. For a lot of ADHD brains, it also falls apart in one of two very specific ways — and neither one means the person using it is doing it wrong.
Where it actually came from
Francesco Cirillo developed the technique in the late 1980s as a university student, using a kitchen timer shaped like a tomato — pomodoro in Italian, which is where the name stuck. The core idea wasn't really about the number 25. It was about externalizing time: instead of trying to feel how long you've been working, a timer tells you, so your brain doesn't have to hold that job on top of everything else.
That part — outsourcing time-tracking to something outside your head — genuinely helps a lot of ADHD brains, because time blindness (poor internal sense of duration) is one of the more consistent traits across ADHD presentations. The problem isn't the concept. It's the specific number.
The two ways 25 minutes backfires
First, the timer interrupts a hyperfocus state right when it's finally useful. If a task has traction at minute 20, an alarm at minute 25 doesn't read as a helpful boundary — it reads as getting yanked out of the one window where things were actually working. A lot of people either ignore the timer, which defeats the point, or resent it enough to drop the whole system within a week.
Second, 25 minutes is too long a commitment for a task that's already being avoided. Agreeing to 25 straight minutes can feel like agreeing to run a mile before you've laced your shoes. The size of the commitment becomes its own barrier, before any actual work happens.
Both problems point the same direction: the 25/5 split was designed for a fairly average, fairly steady attention curve. ADHD attention curves are frequently anything but average or steady — and the fix isn't abandoning the timer idea, it's changing the numbers to match the curve that's actually there.
Variations worth trying instead
| Variant | Good for |
|---|---|
| 5-minute starter | Tasks you're avoiding. The deal is only five minutes — genuinely allowed to stop after. Often the point where momentum kicks in anyway. |
| 10/2 sprints | Low-energy days or short attention windows. Smaller work chunk, smaller break, more repetitions. |
| Flowtime (no fixed length) | Hyperfocus-prone tasks. Track when you start, work until natural fatigue, then take a break sized to how long you worked. The timer measures instead of interrupting. |
| 50/10 long blocks | Tasks needing deep ramp-up (reading, writing, problem sets) where 25 minutes barely gets past the warm-up. |
The actual rule worth keeping from Pomodoro: a visible, external timer beats an internal sense of time, almost every time. The specific interval is just a variable to tune, not a rule to follow.
Making any version stick
- Write the interval down before you start. Deciding the length in the moment invites bargaining — "just a few more minutes" — that erodes the whole system over a couple of weeks.
- Protect the break as hard as the work block. A break that turns into 25 minutes of phone scrolling defeats the timer's purpose just as much as ignoring the work timer does.
- Log which interval actually got used, task by task, not just that you "did Pomodoro" in general. That turns the method into a personal dataset instead of a one-size rule.
Kindquill's daily planning pages leave the exact interval up to you — with a spot to log what length of block actually got the work done, so the system adjusts to you instead of the other way around. Not sure which edition or format fits how you study?
Take the study-style quiz- Cirillo, F. The Pomodoro Technique (self-published method, developed late 1980s; later formalized in Cirillo's 2006 book of the same name).