A goal has been silent for three weeks and you know exactly what it needs. It needs a proper session — three or four hours, a clear head, no interruptions.
You've known that for three weeks. The session hasn't happened, and it isn't going to, because the thing you're waiting for is a rare and specific set of conditions, and rare things are rare.
The move that will actually restart it is much smaller than the one you've been failing to start.
Why the big session never arrives
Three reasons, and they reinforce each other.
The conditions don't turn up. A free four-hour block with energy attached happens perhaps twice a month for most people, and both times something else claims it. Planning around a resource that scarce means planning to do nothing.
The size is itself the deterrent. A four-hour task can't be started casually — it needs deciding on, cleared for, prepared for. Every one of those is a moment where it can be deferred, and deferral is free. A twenty-minute task has one decision in front of it. A four-hour one has five.
And the size is often doing a job. If a goal is frightening, defining the next move as enormous is an extremely effective way of never reaching it, while remaining someone who takes it seriously. Nobody does this deliberately. But if you find your next step keeps growing each time you think about it, that's worth noticing.
The rule: thirty minutes, and one of them
The next move should be finishable in half an hour, by you, on a normal evening, without preparation.
Half an hour, because it fits in the days you actually have rather than the ones you're hoping for. It survives being tired. It can start at nine at night. And crucially it can be finished, which matters more than its size — a finished small thing changes the state of a goal, and an unfinished large one leaves it exactly where it was.
One of them, singular, because a list of five thirty-minute tasks is a two-and-a-half hour session wearing a disguise, and it will be deferred like one. The output of this exercise is a single next action, and everything else stays where it is until that's done.
The test for whether you've got it: could you start it in the next ten minutes if you had to? If the answer involves finding something out, deciding something, or getting into the right frame of mind, it's still too big.
People resist this, and the resistance is worth naming, because it usually sounds like thirty minutes won't achieve anything. Which is true and beside the point. The purpose of the move isn't the output. It's to change the goal's state from untouched to touched, and to leave your head containing the work again, because the next session is enormously easier when you're returning to something warm rather than excavating something cold. Judged as production, half an hour is negligible. Judged as the thing that determines whether there's a session on Thursday at all, it's most of what matters.
How to shrink it
Take the thing you've been failing to start and apply whichever of these fits.
Cut it to its first physical action. Write the chapter becomes open the file and read the last two pages. Not a portion of the work — the physical act that precedes it, which is nearly always smaller than any fraction of the work itself.
Remove the judgement. If the goal is frightening, find the version nobody sees. Send the draft to my agent becomes read the draft. Nothing is exposed, so nothing can go wrong, and the point is contact rather than progress.
Convert it into a decision. Plenty of stuck goals are stuck behind an unmade choice — choose between Substack and Ghost is thirty minutes and unlocks a month of work that couldn't begin without it.
Or make it the chasing rather than the work. If you're waiting on someone, the thirty minutes is the follow-up email and setting the date you escalate. The work is blocked; the chasing never is.
Where this advice fails
It would be dishonest to pretend this always works, and there are two situations where it plainly doesn't.
Some work genuinely doesn't decompose. Deep analytical work, complicated debugging, a difficult piece of writing that needs the whole shape in your head — these have a warm-up cost, and thirty minutes can be entirely consumed by getting back to where you were, producing nothing. For that kind of task, small sessions can be worse than none, and the honest answer is that you do need the long block and should be defending it in your calendar rather than shrinking it away.
The other failure is subtler and more common. Thirty-minute moves can become their own avoidance. Someone can spend two months making small safe moves on a goal — tidying, reading round it, adjusting things — while the one uncomfortable task sits untouched. The counter never rises, so nothing looks wrong, and the small moves supply exactly enough progress to prevent the question being asked.
The guard against that is to know which task you're avoiding, and to check that your thirty minutes is walking towards it. Small steps in the wrong direction are still the wrong direction, just harder to notice.
Three goals on a Tuesday evening
An hour and a half free, three stalled goals, one move each.
Pension consolidation, quiet 34 days. The real task is enormous and ill-defined. The move is find the login for the old provider, which needs no decisions, no courage, and takes eleven minutes including hunting for the paperwork. The goal now has an actual first step visible for the first time in a month.
Second chapter, quiet 12 days, and this one is fear. The real task is to write four thousand difficult words. The move is open the file, read what's there, add one sentence at the end. Twenty minutes, no judgement anywhere in it, and the value isn't the sentence — it's that the file is open, the material is back in his head, and Wednesday's session now starts from somewhere rather than from nothing.
Ship the beta, quiet 19 days, blocked on a signed build. Nothing can be built. The move is the follow-up email and a note saying if not by Friday, build it unsigned and test locally. Six minutes.
Three goals moved in under forty minutes, and none of them were the session anyone had been waiting for. Two of them will need a real session eventually. But a goal with something written on it this week is in a different condition from one that's been silent since the third, whatever the size of the thing written.
What this has to do with the gap
The number tells you which goal to point this at. That's its only job here — the goal at the top of the list has been quiet longest, so it's the one that needs a move, and you don't have to decide which because the sorting already did.
And a thirty-minute move resets the counter exactly as thoroughly as a four-hour session would. The system doesn't grade effort. It records contact, and eleven minutes of contact on a Tuesday is the difference between a goal that's still alive and one that's on its way out.
Related: The anatomy of a stuck goal · Stalled vs blocked: the difference that changes what you do next · The two-day gap that decides everything
Share: