Pomodoro and Time Blocking in ADHD: Why They Fail, How to Adapt

Two methods appear on every ADHD list: pomodoro and time blocking. I tried both, dropped both on the third day, and blamed both on my own clumsiness.

I later saw that the problem was not the methods. It was applying them as written.

Why making time visible matters

The real function of both methods is the same: making time visible from outside.

What we call time blindness is the inability to feel duration from inside. Counting in the head is not reliable in ADHD; twenty minutes can pass like an hour, two hours like twenty minutes. The detailed version is in the article what is time blindness.

A visible timer fills this gap. Its name in the glossary is visible timer, and it is one of the single interventions that helps most in ADHD.

The metacognitive therapy study that Solanto and colleagues (2010) ran in adult ADHD shows that exactly this kind of time management skill has a measurable effect on inattention symptoms. In Barkley's (1997) model too, being able to feel time from inside is treated as part of executive functions; so an outside timer is a support that stands in for a missing function.

The job of the method is not to make you work. It is to make visible where the time goes.

Why pomodoro fails

The classic pomodoro: work twenty-five minutes, take a five-minute break, and after four rounds take a long break.

In ADHD it snags in three places.

The break interrupts hyperfocus. You have entered a rare period of focus and the bell rings. When you take the break, getting back costs a great deal. In the glossary: attention residue. This is what made me drop the method first: losing that flow state, which comes a few times a month, to a timer is very annoying.

Twenty-five minutes is sometimes too long. On a bad day, starting twenty-five minutes feels impossible and the method never starts.

The break does not end. A five-minute break lasts forty. Moving into the break is easy, coming back from it is hard. This is called difficulty with transitions.

The adapted version

• Set the duration to suit you. Ten minutes is a pomodoro too. On bad days, five. The duration is not a sacred number.
• Skip the break if you are in flow. The rule is: if it is going well when the bell rings, continue. Use the break when you are stuck.
• Set a timer for the break too. A separate alarm for the end of the break is the only thing that makes coming back from it possible.
• Do not look at a screen during the break. A break that reaches for the phone makes it impossible to come out of the break. Stand up, drink water, look out of the window.
• Do not touch work during the break. Checking email during the break stops the break from being a break, and by the time you return your attention is already scattered.

Why time blocking fails

Time blocking is dividing the day into blocks in advance and assigning a job to each block.

In ADHD it collapses in one place, and that place is decisive: the time estimate.

The planning fallacy described by Buehler and colleagues (1994) exists in everyone: people systematically underestimate how long jobs will take. In ADHD this deviation is larger.

The result: the plan made in the morning falls apart by noon. When it falls apart, the plan is abandoned entirely, because all-or-nothing thinking kicks in.

In my case there was a second thing that spoiled the picture: the invisible jobs next to the ones that filled the calendar. A meeting lasts an hour, but the preparation before it and the recovery after it never had a place in the calendar. At the end of the day the plan did not hold and I could never find the reason.

The adapted version

• Multiply the estimate by two. Take your first estimate of how long a job will take and multiply it by two. If that seems like too much, measure for a week and find your own coefficient.
• Leave half the day empty. Blocks should not exceed fifty percent of the day. The other half is for delays, transitions and unexpected jobs.
• Cut the number of blocks to three. Do not block the whole day, block the three important jobs of the day.
• Put fifteen minutes between blocks. The transition is itself a job and needs a place in the calendar.
• Name blocks flexibly. "Work on the report" instead of "write the report." A block that does not promise completion does not produce guilt when it falls apart.

Measure first, then plan. For one week, plan nothing and only write down how long things take. That one week makes all your later plans realistic. In the glossary: time estimation.

The choice of timer matters too

It looks like a small detail, but for me it was decisive.

The timer on the phone. The easiest to reach, the riskiest option. The phone you open to set the timer can find you in a completely different place ten minutes later.

A visual timer. There are clocks that show the remaining time as a colored area. Seeing the area shrink instead of reading a number is the most direct way to make you feel time. This kind of tool touches time blindness most.

A kitchen timer. Cheap, a device with one job that opens onto nothing else. This was the solution that lasted longest for me; its one feature is that it has no other features.

Whichever you choose, the rule is the same: the timer must be visible. A timer set in a drawer does not do the job of making time visible.

Which suits whom

A rough distinction can be made.

Pomodoro is for people who have trouble starting. Promising a short stretch lowers the threshold for starting. If getting into a job is the hardest thing for you, start here.

Time blocking is for people who get scattered through the day. Knowing in advance what will be done when removes decision-making during the day. If you start but keep switching jobs, start here.

It is also possible to use both together: set the blocks and work in short intervals within a block. This is the arrangement that settled for me, and the only reason it settled is that I stopped applying either one as written.

Three common mistakes

Spending time looking for an app. The only tool these methods need is a timer. Trying a new app is the most legitimate-looking way of putting off work.

Planning the whole day on the first day. An eight-hour plan never holds. Starting with a single block lasts longer than starting with ten.

Blaming the system when it breaks. When a plan breaks, what to do is not change the method but correct the estimate. Changing methods is the sweetest form of procrastination in this area.

Where to start

If you are going to choose one of the two: if you have trouble starting, begin with a short timer; if you scatter, begin with a three-block day.

And in the first week plan nothing and only measure. I lost years by skipping this step; every plan made without measuring is a plan built on an estimate, and that estimate is wrong.

I covered the starting side in the article the two-minute rule.