Nine weeks since you touched it, and the reason you haven't gone back isn't reluctance.
It's that going back means finding out where you were. What state the work is in, what you'd decided, what the next thing was going to be. That's an hour of excavation before any real work starts, and an hour of excavation is a much bigger ask than an hour of work.
Which means most of what stops people returning is a problem that could have been solved in advance, in about nine seconds, nine weeks ago.
What the gap actually takes
Not the skill, and not the desire. The working state.
You lose where you'd got to, which options you'd already ruled out, what was blocking you, and what you'd resolved to try next. All of it lives in short-term memory and none of it survives a month.
The consequence is that the return has an entry cost, and the entry cost scales with the length of the absence — which is exactly the wrong shape, because the longer you've been away the more the thing has become a symbol rather than a piece of work, and the less appetite there is for an evening of archaeology.
A lot of goals die in that space. Not because anyone decided against them, but because the price of re-entry stayed slightly above what was available on any given Tuesday.
The note that removes it
One line, written when you stop rather than when you return.
Stopped halfway through the costs section, need the Q2 figures. Was on the F barre chord, still can't get the third string. Tried the queue-based version, doesn't handle retries. Next: look at the webhook approach.
Each of those does the same thing: it means the person who comes back in nine weeks doesn't have to reconstruct anything. They open it, read one sentence, and know precisely what to do.
The value is entirely asymmetric. Nine seconds to write, and it converts an hour of unappealing excavation into an evening that starts with a task. That ratio is the best available anywhere in this practice.
And it can only be written at the time. You are the only person who knows this, and you only know it for about ten minutes after you stop.
That window is the reason this habit is worth building deliberately rather than relying on good intentions. Nobody sits down three weeks later and thinks to record where they were, because by then they don't know. The note exists or it doesn't, and which one is decided in the ten seconds after a session ends.
What to put in it
Three things, and one of them matters most.
Where you stopped, physically. Which file, which page, which section. Concrete enough that you could point at it.
What you'd decided. This is the one people skip and pay for. Six months on you'll re-explore approaches you already ruled out, and the re-exploration will feel like fresh thinking. Ruled out X because Y saves an evening a year later.
And what was next. Even a rough version. Something specific enough to start with rather than a decision to make.
Not a summary of your feelings, not an assessment of the session. Descriptions are easier to write and vastly more useful later.
A note only works if something brings you back to it, and nothing about a file on a hard drive does that.
That's the job the number does. A goal that says 63 days quiet, sitting at the top of the list, is what makes you open the thing at all — and once you've opened it, the note is what makes the next hour possible.
Neither works alone. A number with no note tells you something is wrong and leaves you facing an hour of reconstruction. A note with no number sits in a file that nothing brings you back to.
Where it doesn't help
The honest limits.
Some absences aren't about reconstruction. If a goal is quiet because you're frightened of it, a perfect note about where you stopped won't do much — the obstacle is the exposure, not the excavation, and the move there is to shrink the step until it carries no judgement.
It also doesn't help with goals you've stopped wanting. A clear next action on something you're relieved to imagine abandoning just makes the wrongness more legible, which is useful information but not a restart.
And a note six months old is sometimes wrong. The situation has moved, the decision you'd recorded no longer applies, the approach you were about to try has been superseded. It's still better than nothing, but it's a starting point rather than instructions, and treating it as instructions occasionally sends people down a path they'd have abandoned had they thought about it fresh.
Six months and forty minutes
The report was due in March. She stopped in February, three sections in, and it's August.
She doesn't reread it for six months, because rereading means finding out how bad it is and how much is left. The goal sits at 187 days, top of the list, unopened.
When she does open it, with no plan beyond looking, there's a line at the bottom of the file that she wrote in February: three sections done, need the Q2 figures before the costs section.
The Q2 figures have existed since April.
The whole thing that stopped a report for six months was one small blocked task, recorded at the time, resolvable in eleven minutes. Without that line she'd have spent the evening reading three sections trying to work out where she was, and she might well not have started at all.
The reading takes forty minutes. The costs section is drafted the following Tuesday.
The cheapest thing in the practice
Ten seconds at the end of a session, and it's the part that determines whether the goal survives its next long absence.
Which is why the timer asks for a line when it rings — at the one moment when what happened is still in your head and costs nothing to record. And why ticking a step off writes the note for you, since you've already said what you did.
The note isn't for you. It's for the person who comes back, who won't remember any of this, and who deserves better than an hour of digging.
Related: Coming back after six months away · One line is enough · Logging beats tracking
Share: