Two people are trying to swim more.
The first uses a habit tracker. Tuesday, tick. Thursday, tick. The following Tuesday, tick. By March there are twenty ticks and a grid that looks quite satisfying.
The second writes a line each time. Twenty lengths, felt heavy, left shoulder complained on the last five. Thirty-five and could have done more — first time that's happened. Went, hated it, did fifteen and got out.
Both have a record. Only one of them has anything to read.
A tick is a receipt
A checkmark answers exactly one question — did it happen — and it answers in a form you can't do anything with later.
Forty ticks won't tell you the shoulder started complaining in February and never stopped. They won't tell you every miss came after a Thursday night out. They won't tell you the sessions got shorter from January onwards while the grid stayed reassuringly green.
That last one is the real cost. A tracker looks identical whether you're improving or quietly getting worse, because it isn't measuring the thing. It's measuring your attendance at the thing. Forty ticks is equally compatible with forty good swims and forty half-hearted ones, and it will never once mention the difference.
There's a version of this in every kind of work. Fifteen ticks on work on the book concealing eleven sessions of rereading the same chapter. A green grid of commits that were mostly config changes. Attendance is the easiest thing to record and the least informative thing to know.
What one line buys you
It says what actually happened. Not that you worked on the report, but that you drafted the section on costs and discovered you don't have the Q2 numbers. The record now contains the thing you'd otherwise have to remember.
It carries the next move without trying to. Most honest notes end up pointing forwards — realised I don't have the Q2 numbers is a note about the past that hands tomorrow-you a task. Ticks never do this. A tick is finished the moment it's made.
And it's evidence against your own memory, which is the part people underestimate. When something is going badly, memory is confidently and uselessly wrong. You'll swear you've made no progress on the book in months, and the log will show eleven entries since January, four of them substantial. Memory reports the mood. The log reports the work. On bad days the gap between those two is worth a great deal.
One line is genuinely enough
The reason people don't keep logs is that they picture a journal — a full page, a reflection, twenty minutes at the end of a day that has already gone on too long.
That's a different practice, and the ambition is what kills it. Journals get abandoned in February.
The bar here is a sentence. Sometimes six words. Sent the invite email, waiting on Priya now. Two hours, got the auth flow working. Didn't. Too tired. Under ten seconds each.
The short version isn't a degraded form of the long one. For the purpose of seeing what happened across months, it's most of the value at a fraction of the cost, and a log you keep beats a journal you don't by an enormous margin.
The entry about nothing
Didn't. Too tired.
That looks like a wasted line. It's the most valuable one in the file.
One of those is nothing. Four in a fortnight, all saying tired, is a finding — and one you'd never reach by remembering, because each individual tired evening is unremarkable and instantly forgettable. The pattern exists only in aggregate, and the aggregate exists only if you wrote the boring ones down.
Trackers structurally cannot hold this. A miss in a tracker is an absence, a blank square, indistinguishable from every other blank square. It can't record why, so the difference between four evenings missed from exhaustion and four missed from dread never enters the record at all. Those are completely different problems and the tracker gives them the same appearance.
Write the misses. Skipped, dreading the feedback. Skipped, was at the hospital. Two months later that's a diagnosis, sitting there in your own handwriting.
The case for the tick
Ticking is faster, and that matters more than it sounds. A checkbox takes half a second. A line takes ten. Multiply by a daily habit across a year and the tick wins on effort by a wide margin — and a record you actually keep beats a better one you abandon.
Ticks are also easier to read at a glance. Forty marks in a grid show you a shape immediately: dense in January, patchy in March. Forty lines of prose need reading. If all you want is am I doing this or not, the tracker answers faster and the log makes you work for it.
And for genuinely simple things, there's nothing to write down. Took the tablets. Did the stretches. The activity doesn't vary, so a line would say the same words every day, and the log becomes a slower checkbox with extra steps.
The argument here isn't that ticking is useless. It's that ticking suits work where every instance is the same, and most of what people care about isn't like that. Two hours on a first draft is not interchangeable with two hours on another first draft, and the moment the instances differ, the tick throws away the only part worth keeping.
Reading it back in October
Someone has been trying to finish a portfolio site since February. In October they open the log, expecting to find almost nothing, because that's what it feels like.
There are thirty-one entries. The first fourteen are dense — rebuilt the nav, wrote the about page, swapped the type to something less shouty. Then a run of shorter ones through April. Fiddled with spacing. Changed the type again. Moved the case studies around.
Then nothing for five weeks, and when it picks up in June the entries have changed shape entirely. Reordered the projects. Not sure the blue is right. Looked at other people's sites for an hour.
The log makes something visible that no amount of remembering would have. The work stopped being building and became rearranging, and it turned at the point where the next real task was writing the case studies — the part where you have to say what you did and whether it worked. Every entry after April is a way of being at the site without writing those.
Nobody decided that. It isn't in any single entry either; entry twenty-two looks like a perfectly reasonable evening's work. It's only visible in thirty-one of them read together, which is the one thing a column of ticks can never give you.
Why goaldrift runs on notes
The counter runs on what you write, not on what you tick. Write something and the goal goes to zero days quiet. That's the whole mechanism.
It could have been a button — touched this today — and it would have been less effort to use. We didn't, because a button records that you showed up and a line records what you found. The first produces a number. The second produces something you can read in October and learn from.
Two things follow. Ticking a step off writes the note for you, because you've already said what you did by ticking it. And the focus timer asks for a line when it rings — a small friction, deliberately placed, because that's the moment what happened is still in your head and costs nothing to record. Ten seconds later it's gone, and the session becomes another undifferentiated tick.
The days-since number tells you a goal has gone quiet. The notes are what tell you why, and what to do about it.
Related: The anatomy of a stuck goal · The case against streaks · Stalled vs blocked
Share: