Nobody notices the week a goal dies, because nothing happens in it.
That's the difficulty. There's no failure to point at, no missed deadline, no row. From inside, it's an ordinary week in which a thing you care about didn't come up much. From outside, if anyone could see it, it's the last week the goal was reachable at normal cost.
It does have a shape, though. Once you've seen it a few times it's recognisable, and it's recognisable early enough to matter.
The work changes shape before it stops
The clearest early sign isn't reduced effort. It's effort that has quietly moved sideways.
The hours are still going in, but they've stopped landing on the difficult part. Someone writing a book reorganises their notes. Someone building a product redesigns the landing page for the third time. Someone job-hunting rewrites the CV again rather than sending it anywhere.
None of that is idleness, which is what makes it so effective. It's real work, it produces visible output, and at the end of the evening you have genuinely done something. But the thing you've done is the part that carries no risk of judgement, and the part you're avoiding is untouched — and gets harder every week it stays untouched.
If you want one question for this, it's whether the last three sessions moved the goal forward or merely moved things around inside it.
The language goes past-continuous
Listen to how you describe it.
Early on it's present tense and specific. I'm doing the second chapter. By the last week it's become I've been meaning to get back to that, and the change is invisible to the person saying it. But I'm doing is a sentence about now, and I've been meaning to is a sentence about a period, told from outside it.
Two other phrases turn up in the same week. Once things settle down — which relocates the goal into a future that has no date and never arrives. And I'll pick it up properly — where properly means a substantial session you don't have time for, which quietly rules out all the small sessions you do have time for and would have worked.
Restating instead of doing, and the dread underneath it
This is the most deceptive one, because it looks precisely like commitment.
You rewrite the goal. You clarify the deadline, or split it into better steps, or decide the whole thing needs rethinking, and you spend a productive evening producing a plan you feel good about. Then you don't act on it, and a fortnight later you rewrite it again.
Restating a goal reliably produces the feeling of progress, which is the feeling doing it would have produced, at none of the cost. It's the most efficient avoidance available and the hardest to catch, because a person redesigning their approach for the third time genuinely believes they're taking it seriously.
The tell is simple. If a goal has been reformulated more recently than it's been worked on, the reformulating is the avoidance.
There's often a specific moment a few weeks earlier — an idea that the thing might not be good enough, a piece of feedback, a comparison with someone further along — and afterwards the sessions become harder to start while remaining perfectly normal once you're in them.
That gap between starting and continuing is diagnostic. Work you dislike is unpleasant throughout. Work you're frightened of is fine once you're inside it and almost impossible to approach. If you consistently enjoy a session and consistently can't begin one, the problem isn't the work.
This is also why the goals people care most about go quietest first. There's nothing to fear from a goal you're indifferent to, which means the silence on your list is not distributed by how much things matter. It's distributed by how much they're capable of hurting you, and those are close to opposite orderings.
Where this gets it wrong
An honest caveat, because pattern-matching on yourself has a failure mode.
Every sign above can be innocent. Reorganising notes is sometimes exactly the right task. Once things settle down is occasionally a straightforward description of a genuinely bad month. Rewriting a goal can be real thinking rather than avoidance — sometimes the goal was wrong and the rewrite is the most valuable thing you'll do to it.
Read this list as a hypochondriac and you'll diagnose a dying goal every time you have a slow fortnight, then apply an intervention to something that didn't need one. The signs matter in combination and over time, not individually. One of them in a week means nothing. Three of them over a month is worth taking seriously.
There's also a version of this where the goal really is finishing, correctly. Sideways work, vaguer language and a loss of appetite sometimes mean you've got what you needed from something and are ready to stop. The signs can't tell those apart, and neither can anyone else. What the signs do is tell you to look. What you find is yours.
Twelve days in September
Someone is six months into a side project — a scheduling tool for their partner's clinic, evenings and weekends, and by August it mostly works.
The first week of September has four sessions in it. In two of them he refactors the database layer, which needed doing about as much as anything ever needs refactoring. In one he redesigns the settings page. In the fourth he writes a list of everything left to do, which is a good list.
What none of those touch is the last real task: giving it to the clinic's receptionist and watching her use it. That's been the next step since mid-August.
The second week has two sessions. One is spent reading about a different framework. In the other he decides the tool should probably handle recurring appointments before anyone sees it, which is a new requirement he has just invented, and which pushes the receptionist another month away.
By the third week he's telling people it's nearly there, just tidying a few things, and the sessions have stopped. Nothing failed. The code still works and is sitting on a laptop where it will remain.
Every sign is in that fortnight — sideways effort, an invented requirement, softening language, and dread of one specific fifteen-minute task. Written down it's obvious. Lived through, at an hour a night after work, it felt like a productive September.
The thing that would have caught it
None of this is subtle in hindsight. The problem is entirely that it's invisible from inside, in the moment, week by week.
What makes it visible is a record you can read backwards. Not a tracker — ticks would show four sessions and then two, which reads as a slightly quieter fortnight. Lines would show refactored the db layer, redesigned settings, read about a different framework, and the absence of the receptionist across all of them.
Nobody spots this in the week it's happening. You spot it in October, reading twelve entries in a row, none of which touch the thing that mattered.
Which is the practical use of all this. You're not going to catch the week a goal dies while you're in it — nobody does, and a post telling you to be more self-aware would be useless. What you can do is keep a record honest enough that the pattern is legible later, and look at it often enough that later isn't a year away.
The gap number handles the second part. It puts the quietest thing at the top, so the looking happens without you having to remember to do it. The notes handle the first. Between them, the fortnight in September stops being something you only understand in retrospect.
Related: Goal drift: what it is and why it's invisible · The two-day gap that decides everything · The anatomy of a stuck goal
Share: