The Pomodoro technique does not fail. Your phone does.

The timer has four minutes left, and the document has not changed since ten.

Nothing went wrong with the twenty-five minutes. You set them, you meant them, and then at some point you wanted to know how many were left.

That is where it breaks. Not at minute one, and not at minute twenty-four with the bell coming, but at the first glance at the clock, because the clock and the distraction are the same rectangle of glass.

Which makes the answer to why doesn't Pomodoro work for me annoying. It does work, right up until you want to know the time, at which point it hands you the thing it was keeping you from.

The rule you have never followed is the whole technique

Francesco Cirillo worked it out in the late 1980s, as a student, with a wind-up kitchen timer shaped like a tomato. Twenty-five is where that timer landed, not the output of a laboratory, and the right length for your work is an argument we have elsewhere.

Everybody knows the shape it produced: twenty-five on, five off, a longer break after four. That is half the technique and it is the half that does nothing.

The other half is the fifth rule below, and almost nobody has heard of it. A pomodoro is indivisible. If it begins, it has to ring, and if something interrupts it, it is void. Not paused. Void. The nineteen minutes do not count, and you start a fresh twenty-five.

The interruption gets its own protocol, and the protocol is a pencil. You do not act on the thought. You write it down beside the task and carry on with the timer running. Booking the dentist goes on the list, not in a browser tab.

Every timer app implements the first four. Almost none implement the fifth, because it is the only one that involves saying no to the person holding the phone.

Every interruption the technique was built for arrived from somewhere else

Cirillo's interruptions are things that happen to you. A colleague at the desk. A phone ringing on the wall. Each has the properties that make the void rule workable: a moment you could point at, an origin outside your own head, no chance of passing for the work.

The reach for the phone has none of them. Nothing arrived, nothing rang, and the impulse came out of the same head that is meant to be enforcing the rule. It even turns up wearing a badge: I am checking the timer. By the time voiding is the right call you have been gone four minutes, and voiding feels like an overreaction.

So the only enforcement is a manual rule, applied by the person being interrupted, firing on an event shaped to go unnoticed. It never fires. That is not you being bad at it. There is nothing there to be good at.

The tomato had three properties nobody bothered to write down

The kitchen timer came with a design brief it never asked for.

• It was a separate object. Looking at it put you inside nothing.
• It could not show you anything. Its whole vocabulary was one number and one bell.
• Winding it took a hand and a few seconds, so every pomodoro began with a physical promise.

Now run those past a timer app. It lives on the phone, one swipe from everything that has ever taken an evening off you, and starting it is a tap, like everything else all day.

That is the join. Not the twenty-five, not the five, not the tick sheet. The technique's one mechanical part was that the clock lived where the distraction could not reach it. Move the clock onto the phone and you have kept the packaging and thrown the technique away.

You did not open Instagram. You opened the clock. Instagram was on the way.

The repair is cheap. Use a kitchen timer, the microwave, anything in the room with a number on it that is not a phone. If it has to be the phone, set the countdown in the Clock app rather than a timer app: a running Clock timer sits on the Lock Screen, and in the Dynamic Island on the iPhones that have one. Checking it then costs a raised wrist rather than an unlock, and only one of those goes past your notifications.

Five minutes on a phone is not a break, it is a faster job

Cirillo is specific about the break. The mind comes off the task completely: stand up, drink water, be slightly bored. What people do instead is spend it inside the medium that was the problem, so their attention works harder in the five minutes than in the twenty-five.

Then there is the part that actually kills it. Overrunning the work block has a rule attached. Overrunning the break has none: nothing rings to end one, so it is the only unguarded stretch in the loop. This technique almost never dies nine minutes into a block. It dies eleven minutes into a five-minute break, in the same chair, with the document open behind the tab.

So give the break a place instead of a length. The kettle, the stairs, the front step. A break in the same chair facing the same screen is a smaller tab. And time it, which Cirillo says to do and nobody does.

The Pomodoro technique does not work for you because it times the wrong thing

The technique counts minutes of work. Nothing in it is pointed at the phone, and its only defence against one is a manual rule firing on an event you cannot see, judged by the person being interrupted, off a clock that lives inside the interruption.

So I did a twenty-five minute pomodoro describes a period of time. It does not describe a period of work, and certainly not a period in which the phone stayed shut, because nothing was measuring that.

What an iPhone will and will not do about this

Four controls come with the phone, and three get recommended for this job by people who have not tried it.

Focus governs what reaches you, not what you reach for. Downtime is the strongest of the four, but its unit is a stretch of the day set in advance, and moving it means a trip into Settings on the phone you were trying not to touch. An App Limit budgets a whole day, so it arrives after the minutes are gone.

No first-party control on an iPhone means shut these four apps for the next twenty-five minutes, starting now. That is the hole, and it is not an oversight. Apple builds on the assumption that whoever holds the phone is in charge of it. At ten past two, you are.

A pomodoro that survives contact with a phone

Rebuild it with the broken join replaced. Four properties, the first three costing a kitchen timer.

1. The clock is readable without opening anything. Lock Screen, wrist, microwave, tomato. Any of them, so long as reading it puts you inside nothing.
2. The break has a place, not just a length. If it happened in the chair, it did not happen.
3. The door is on the apps, not the notifications. Silence is not a door. Everything still opens when it is quiet.
4. Nothing depends on you deciding, at minute nine, whether this counts as an interruption.

The fourth is the one you cannot assemble out of settings, because every setting here can be changed by whoever is holding the phone, and at minute nine that is the person losing.

Which is where we admit what we make, because it is the same shape. Scrappy is a small dog who stands in front of the apps you name. His version of the block is a walk: name it, set it between twenty-five minutes and eight hours, and he guards the list until it ends. It runs as a Live Activity, so the countdown sits on the Lock Screen where the tomato used to sit.

The rest landed closer to Cirillo than we meant. Knock during a walk and he is polite. Knock again and he is surprised, then firm, then standing on the doorknob saying one word. Getting past him costs a treat, and treats come from real walking, roughly two thousand steps each, which puts a place inside the break. Treats are never sold.

The shortest walk he does is twenty-five minutes. That was not a tribute. It is about how long a person can stand to be somewhere else.