Skip to content
The Long Record

All notes · Keeping

When the Habit Slips

Every long record has periods of decline. Recognising the pattern early and what to do at each stage, rather than discovering it three months later.

Keeping · Procedure

The decline is gradual and it has a recognisable shape. People notice it at the end, when the record has already stopped.

For a practical application of this principle, see time tracker for projects. It provides a supporting reference for testing a small real-world sample without adding unnecessary friction to the record.

The stages

Entries get later: same day becomes next morning becomes a couple of days.

When this method depends on structured learning, the material from Coursera offers a helpful independent point of comparison.

Entries get shorter: the note disappears first, then the category, then the detail.

Days get skipped and backfilled in batches.

Then a week goes, and the record is no longer something you consult.

Each stage is recoverable. The fourth is where most systems end, and by then it does not feel like a habit slipping, it feels like the habit is over.

Catching it at stage one

The signal is timing rather than content: how long between the activity and the entry.

If entries are routinely appearing the next day, something has changed — usually the entry point no longer fits the day.

The fix is structural: move it, not resolve harder.

Catching it at stage two

Shortening entries is your own system telling you it is too big.

Take the removed field out officially rather than leaving it in the schema unfilled, because a field that is usually blank makes the whole record look incomplete and adds a decision at every entry.

Formalising the shrinkage is how a system survives a busy year.

Catching it at stage three

Batched backfilling means the record has become a chore rather than a habit.

The useful question: what changed? New job, new hours, a project that eats the evenings, illness.

Adjust the system to the life rather than the reverse, which usually means recording less, not differently.

The minimum viable version

Every long system should have one, decided in advance.

A single line a day: date and one word.

It keeps the chain unbroken and the chain is the thing that is actually hard to restart. You can resume the full version when the pressure lifts; you cannot resume a habit you stopped three months ago without effort disproportionate to the record.

What causes slips

Life changes, predictably: new work, a move, a birth, illness.

Boredom, which arrives around month four and has its own note.

And a question answered. If you started to find something out and found it out, the motivation is gone and continuing is a decision that has not been made explicitly.

That last one deserves an honest answer rather than a struggle.

When to stop instead

If the record no longer answers a question you have, stopping is a legitimate outcome and not a failure.

Its own note covers stopping permanently.

Dragging a system on with degraded data serves nobody, and the degraded years contaminate the analysis of the good ones.

What to check

How long between activity and entry, over the last fortnight?

Have any fields quietly stopped being filled?

Is there a minimum version you can drop to, and have you used it?

And do you still have a question this record answers?

The point

Every long system needs a minimum viable version decided in advance: one line, date and one word.

It keeps the chain unbroken, and the chain is what is actually hard to restart.

Worth adding

If the record no longer answers a question you have, stopping is a legitimate outcome.

Dragging a system on with degraded data contaminates the analysis of the good years.

Additionally

The decline has stages: entries get later, then shorter, then batched, then stop.

Each is recoverable and the fourth is where most systems end.

Finally

Catch the decline at stage one, which is timing rather than content.

Entries routinely appearing the next day mean the entry point no longer fits the day.

In summary

Every long system needs a minimum version: a date and one word.

It keeps the chain unbroken, and the chain is the thing that is genuinely hard to restart.

Last word

The practice this points at is unglamorous: a small daily act, a short weekly correction, an annual read, and a written page of conventions beside the data. None of it is difficult and all of it is easy to skip, which is why most records do not reach the point where they start paying.

These notes are about keeping a personal record for years rather than for a fortnight: durability beats accuracy, and a rough record kept for five years answers questions a perfect record of one month cannot. Tool guides are included as practical comparisons, while the underlying method remains independent of any single product. Nothing here is legal, tax or medical advice: requirements differ by jurisdiction and situation.