Get fit.
Written in January by someone who knew exactly what they meant. They had a picture in their head — the specific gym, the particular kind of tiredness they were sick of, a memory of how they'd felt three years ago.
By March that picture has gone, and what's left is two words that could mean anything. So on a Tuesday evening in March, faced with get fit and forty free minutes, nothing happens — not because motivation dipped, but because the goal doesn't say what to do and working it out is more effort than it looks.
The goal is a message to someone else
This is the reframe that makes the rest obvious. You are not writing for the version of you who's writing. That person has the whole thing in their head and needs no reminding of anything.
You're writing for a person three weeks from now who has forgotten the specifics, is tired, has forty minutes, and is deciding between this and something easier. That person has no access to the picture in your head. All they have is the text.
Which means every ambiguity you leave is a decision you've deferred onto someone with less energy and less context than you have right now. Vagueness feels harmless when you write it, because you can see through it. Later, nobody can.
This is also why goals feel so much better to write than to do. Writing happens at the peak of your enthusiasm for the thing, with the whole picture vivid, and it produces a document calibrated for a person in exactly that state. Doing happens at the trough, weeks later, and the document turns out to have been written for the wrong reader. Almost every goal that quietly fails was written by someone who couldn't imagine needing more detail.
What makes a goal legible later
Three things, and none of them is about ambition.
An action rather than a state. Get fit is a condition; there's nothing to do to it. Swim on Thursday mornings is a thing a person does. States are useful for describing where you'd like to end up and useless for telling you what happens next, and the goal text needs to do the second job because that's the one you'll need it for at eight on a Tuesday.
Enough specificity to remove the decisions. Swim still leaves which pool, when, and whether you have a bag packed. Swim at Castleton before work, Tuesday and Thursday removes all three, and each removed decision is a place the whole thing could otherwise stall.
And a one-sentence reason, kept short. Not a mission statement — a line that tells later-you what this was for. Because my back stops hurting when I swim. Three weeks on, that sentence is what distinguishes a goal worth returning to from one that turns out to have been a passing mood in February.
The one-sentence why has to stay short
There's a strong temptation to write more here, and it's worth resisting.
A long reason is written for an imagined audience — it's persuasive, and there's nobody to persuade. It also decays badly. A paragraph of motivational reasoning read back in June feels like listening to a slightly embarrassing stranger, and the embarrassment attaches to the goal.
A short concrete reason survives. My back stops hurting. I want to read Márquez in Spanish. So the clinic stops using the paper diary. These are still true in June, they aren't performing anything, and they're specific enough to check against — if your back has stopped hurting, or you no longer care about Márquez, the sentence tells you something important about whether to continue.
Where specificity goes wrong
The honest counter-argument, because this advice is usually given without one.
Over-specifying makes a goal brittle. Swim at Castleton before work, Tuesday and Thursday is excellent until the pool closes for refurbishment, or your Tuesdays change, and then the goal reads as failed when the only thing that's wrong is a detail. People abandon goals over broken specifics far more often than anyone admits — the plan stops being possible, and rather than editing it they quietly stop looking at it.
There's also a class of goal that genuinely resists this. Creative work often doesn't have a knowable next action; the point is partly to find out what the work is. Forcing write a novel into a defined sequence of steps produces an outline you'll abandon, and the specificity ends up being a way of avoiding the uncertainty that the work actually requires.
The compromise that holds: specify the next action, not the whole route. One step, defined enough to start, with the rest left open. And treat the specifics as provisional — a goal is a document, and rewriting it because the pool closed is maintenance rather than failure. The thing to avoid is the other kind of rewriting, where the text changes every fortnight and the work never does.
Same goal, three versions
Learn Spanish. Written in January. By March it means nothing actionable — no next step, no place to start, and any forty-minute window fails to find a use for it.
Learn Spanish, 20 minutes a day. Better, and still missing the parts that matter. Which twenty minutes, doing what? The first evening will be spent choosing an app rather than learning anything, and the second will be spent wondering whether the app was the right choice.
Twenty minutes of Spanish after dinner, working through the Coffee Break podcasts in order. Because I want to read Márquez without the translation. Now tomorrow-you opens this and knows precisely what happens: after dinner, the next episode, twenty minutes. No decisions. And in June, when it's been quiet for a fortnight, the reason line is still there and still means something, which is what determines whether it comes back.
Three versions of one goal. The difference isn't ambition or commitment. It's whether a tired person in March can read it and act.
Worth noting what the third version doesn't contain. No target fluency level, no exam date, no promise about how long it'll be kept up. Those would all sound more serious and none of them help on a Tuesday. The test for anything you're thinking of adding is whether it changes what happens in the next forty minutes — and most of what people add to goals fails that test comfortably.
What this has to do with silence
A vague goal goes quiet faster, and it does so for a reason that has nothing to do with wanting it.
Every time you look at get fit you have to do a small piece of work before any actual work can begin — decide what it means today, and what that implies for tonight. That work is invisible, unrewarded, and easy to defer, so it gets deferred. The goal isn't abandoned; it's just never quite started, over and over, until the gap is six weeks long.
Which is why goaldrift keeps the description and the steps on the goal itself, rather than tucking them away. When a goal surfaces at the top of the list after nineteen days, what you need in that moment isn't encouragement. It's the sentence you wrote in January telling you what you meant and what happens next.
Related: The thirty-minute unstick · The anatomy of a stuck goal · One line is enough
Share: