15-Minute Focus Blocks: The Science of Short Sessions That Actually Get Done

A fifteen-minute block is short enough that you won't negotiate with it. That's the whole mechanism. A ninety-minute deep work session requires a decision — do I have the energy, is the calendar clear, is my head in the right place. Fifteen minutes requires nothing. You start.

That sounds like settling for less. Usually it isn't. Most stalled work isn't stalled because it's long. It's stalled because the first physical move is undefined, and an undefined first move is exactly what a brain avoids. A short block forces you to name a move small enough to fit inside it — and naming the move is most of the job.

Why short sessions beat long ones on stuck work

Two well-described effects do the heavy lifting here.

The first is the Zeigarnik effect: unfinished tasks stay more mentally available than finished ones. An open loop keeps surfacing. Practically, this means the fifteen minutes you spend starting buys you background processing for the rest of the day — the solution that arrives in the shower, on a walk, halfway through a conversation about something else. You only get that dividend if you opened the loop. A task you have never touched does not run in the background; it just sits there generating dread.

The second is attention residue, a term from organizational psychology for what happens when you switch tasks before reaching a natural stopping point: part of your attention stays behind on the thing you left. This is usually offered as an argument against short blocks. It's actually an argument for designing them well. A block that ends mid-sentence leaves residue. A block that ends with two written lines saying where you stopped and what comes next leaves far less, because you've handed the loop to paper instead of holding it in your head. The note is the boundary.

Then there's Parkinson's law: work expands to fill the time available for its completion. Give a task an afternoon and it takes an afternoon. Give it fifteen minutes and you'll skip the font-choosing, the tab-reorganising, the three-minute stare at the ceiling. The constraint does your editing for you.

The mechanics of running one properly

Setup takes about thirty seconds. Skip it and you get fifteen minutes of drifting, which is worse than doing nothing, because it teaches you the method doesn't work.

1. Write the outcome, not the topic. Not “work on the deck” but “get slides 1 to 4 to a state I'd show someone.”

2. Decide the first physical action. Open which file? Type which sentence? Call whom? If you can't name it, then naming it is this block's job — which is a legitimate use of the block.

3. Put the phone in another room. Face-down on the desk still works as a cue.

4. Close every tab that isn't the work. Not minimise — close. Reopening takes four seconds; that friction is the point.

5. Set a timer you can hear from across the room. Phone timers fail here, because the phone is elsewhere. A kitchen timer or a smart speaker works.

6. Begin the first action immediately. No warm-up email check. The first ninety seconds set the tone.

7. When the timer sounds, stop and write two lines: where you stopped, and what's next. Then stand up.

A first-fifteen-minutes script

Here is what a real block looks like when the task is “write the quarterly summary I've been avoiding for a week.”

• 0:00 to 0:45 — Open the document. Type the heading and the three section names. Nothing else.

• 0:45 to 3:00 — Under each section, write one ugly sentence saying what that section will claim. Ugly is required. If you catch yourself editing, type TK and move on.

• 3:00 to 9:00 — Pick the section you know best and write it badly, straight through, without stopping to check any figures. Where a number belongs, type [NUM].

• 9:00 to 13:00 — Keep going into the next section. If you've run dry, go back and fill three [NUM] placeholders from the source file instead.

• 13:00 to 15:00 — Stop writing. At the very top of the document, type: “NEXT: fill remaining [NUM] in section 2, then draft section 3 — the argument is that margin improved because of the pricing change, not volume.” Close the laptop.

That block produced maybe two hundred words of bad draft. More importantly, it converted “write the quarterly summary” — a phrase vague enough to trigger avoidance every time you read it — into “fill three numbers, then draft one section,” which is something you can start tomorrow without any emotional preamble. The second block will be faster than the first. The fourth will be dramatically faster.

What belongs in fifteen minutes, and what doesn't

The format has a shape. Force the wrong work into it and you get frustration, which then gets blamed on the method rather than the mismatch.

Fifteen minutes is excellent for:

• Starting anything you've avoided for more than three days

• Tasks with an end you can actually reach — one email, one form, one phone call, one paragraph, one bug

• Reviewing or correcting something someone else drafted

• Any queue-shaped admin: expenses, inbox triage, invoices, filing

• Deliberate practice with clean reps — scales, a language deck, free throws

• Thinking on paper, where the output is a page of notes rather than an answer

It's poor for work with a long ramp — debugging a subtle failure where the first ten minutes go on reconstructing state, complex modelling, anything that needs six variables held in your head at once. For that kind of work, use short blocks as preparation rather than execution: write the reproduction steps, gather the files, list the three hypotheses. Then when you do get ninety uninterrupted minutes, none of it is spent on setup.

Stacking blocks without turning the day into a marathon

Three blocks with real breaks is a solid day's movement on a hard project. The pattern that holds up over weeks: fifteen on, five off, fifteen on, five off, fifteen on, then a genuine break of twenty minutes or more.

The five-minute break has one rule: no screen with a feed on it. Stand, refill water, look out of a window, stretch your hips. If the break is a social app, you aren't resting — you've switched to a task that's much harder to stop than the one you were doing, and the third block will quietly fail to happen.

This is a close relative of the Pomodoro Technique, developed by Francesco Cirillo, which uses twenty-five-minute intervals with short breaks and a longer break after four of them. Twenty-five fits better once you're already moving. Fifteen fits better when you're stuck, because the smallness of the number is what makes you willing to begin. Nothing is sacred about either figure. What matters is that the number is fixed before you start and not renegotiated halfway through.

The objections, answered

“My day is nothing but meetings.” Then your blocks are the gaps between them, and those gaps already exist. A call that ends at 10:52 before an 11:00 start is a block. What makes the gap usable is a pre-built list — call it the fifteen-minute list — of tasks already decomposed to that size with the first action written out. Without the list you'll spend the eight minutes deciding, and then do nothing.

“Fifteen minutes isn't long enough to reach flow.” True, and largely beside the point. Flow is a wonderful way to work and a hopeless way to plan, because you cannot schedule it. You can schedule starting. Flow turns up more often for people who start more often.

“I always want to keep going when the timer sounds.” Good sign, and you may continue occasionally — not by default. If you routinely blow past the timer, the willingness-to-start benefit erodes, because you retrain yourself to hear “fifteen minutes” as “an unknown quantity of time.” Stop, write the next-step note, take five, run another block.

“This feels like it's for small things.” A three-hundred-page manuscript is a small-things problem repeated several hundred times. So is a database migration. Project size has almost no bearing on the size of its next useful action.

Failure modes and their fixes

• You spend the whole block deciding what to do. Fix: the deciding was the block. End it with a written first action and count it as a win, because next time you'll start in four seconds.

• The timer goes off and you don't register it. Fix: louder timer, placed in another room, so acknowledging it requires standing up.

• You keep “just quickly checking” something mid-block. Fix: keep a scrap of paper beside the keyboard and write the thing down rather than looking it up. Deal with the whole list afterwards, which usually takes four minutes and settles half of them as unnecessary.

• It works for a week, then quietly stops. Fix: your list has gone stale. Short blocks run on pre-decomposed tasks; left unmaintained, items drift back into vagueness, and vague items don't fit in fifteen minutes.

When the method stops working

Sometimes short blocks stop producing anything at all, and the honest answer isn't a better timer. Three patterns are worth checking, in order.

First, the task is genuinely the wrong size. If four consecutive blocks all end with a note saying “still working out what this involves,” you don't have a focus problem. You have an undefined project. Stop timing, take one uninterrupted hour, and write out what actually has to happen, in sequence, until you have at least six items you could start cold. Then go back to blocks.

Second, you're avoiding a decision rather than a task. Blocks are an execution tool. If the real obstacle is that you haven't decided whether to take the job, kill the feature, or tell your brother-in-law no, timed work won't shift it — you'll just produce adjacent activity. Name the decision, write down what would let you make it, and go get that.

Third, you're tired in a way a five-minute break doesn't touch. Short blocks are unusually good at exposing this, because they strip away every other excuse. If fifteen minutes of undemanding work feels impossible several days running, the problem is upstream: sleep, illness, grief, or eight months at full capacity. That isn't a productivity problem, and productivity tools will not fix it.

The method isn't fragile. It's narrow. It solves one thing — the failure to begin — and it solves it reliably. When your real problem is something else, it will keep reporting that fact to you, once every fifteen minutes, until you listen.

If you want those sessions to count for something beyond the work itself, TaskTreasury lets you run focused blocks against real-life tasks and earn Treasury Credits for the ones you finish.