How long does it take you to come back? Count that, not the streak

Last time: The catch up plan is the reason you have not come back yet.

Day 63 of the language app. Then a flu, four days in bed, and the little flame on the screen is grey. The counter says 0. You feel worse than if you had never started, and the app is now one more thing on the phone you avoid touching.

A streak measures how long you lasted. It says nothing about the moment that decides whether a system survives: what happens after it stops. And something always stops it. Illness, travel, a rush at work, a family emergency. A measure that resets to zero every time is pointing at the wrong moment.

There is another number worth watching. It is less satisfying to look at, and much more useful.

Restart latency

Restart latency is the time from noticing that a system has lapsed to reaching a state you trust again. A trusted state means you know three things: what matters now, what to do next, and what can wait without harm.

Notice what it leaves out. The time until you are fully caught up does not count. Neither does the time until the system looks the way it did before. Only the time until you can act again with confidence.

Two weeks and ten minutes

When You Lose Track has a character called Priya who ran her work notes and home admin from one planner, every day, for months. Then a two word message from her manager asked to talk. It turned out to be about a schedule change. In the two days before the meeting she could not bear to open a tidy planner listing everything she had fallen behind on, so she left it shut.

Her restart latency was two weeks. Almost all of it was dread. When she finally opened the planner, the work inside was small.

A streak counter would file that as a failure and a reset. Restart latency shows where the cost actually sat: in the gap between noticing and acting. That gap is the part to work on.

Reading your own number

You do not need an app or a spreadsheet. A rough estimate in hours or days is enough. The last time this system lapsed, how long did it take you to get back to a state you trusted?

Then let the number point at a fix. The book offers a rough rule of thumb, which is a starting guess rather than a diagnosis:

• Four hours to get back into your finances suggests the system wants one view of balances, one place for bills and a faster way to see what is due.
• Two days to get back into a project suggests the notes you leave when you stop are not doing their job.
• Two weeks of dread before a short piece of work, Priya's pattern, suggests the task is fine and the way back in is not. Shame, uncertainty and backlog are standing at the door.

Each answer leads somewhere different. A streak counter only ever says try harder.

Shortening it

Most of what shortens restart latency is done before the interruption, while things are still running.

Leave a state note when you stop. Three lines. Current, what is true now. Next, one visible action. Check, when you will look again. It takes a minute or two, and it spares you the slowest step of most returns, which is piecing together what was happening.

Choose a restart marker. The place your eyes go first when you come back: the top of a document, a sticky note on the laptop, the lock screen of your phone. Put the note there.

Make a small return count. If the only legitimate return is a full one, every return is large. Opening the system and reading the current state should count.

Let missed days stay missed. One review of the present, not a repayment of the past.

These will not keep you from drifting away. They make the way back shorter, and for some systems that will be enough, while for others the note will sit unread and you will learn that the delay lives somewhere else.

Try it this week

Pick one system you care about and estimate your restart latency for it, honestly. Then ask what filled most of that time: dread, rebuilding context, finding things, or the work itself.

The restart latency reflection on the site helps you estimate it and name what would shorten it. It is a practical model, not a clinical measure, and it does not treat anything. The only test it has to pass is whether your next return comes sooner.

As for the grey flame on the language app: one lesson today does not bring the 63 back. It does tell you your latency was four days, which is a number you can work with.

Next time: the planner that works beautifully, as long as you use it perfectly.