The Built to Restart Method
A system is notfinished until itincludes the way back.
Most advice covers the good days. Reliability is not never leaving. It is having a known way back. This is the method from When You Lose Track, explained in full.
How are you operating today?
Not a test, a score or a diagnosis. It picks the right-sized tool.
Low Power
Protect what matters.
The smallest version that still protects the most important outcome and reduces tomorrow's damage.
You are here when
You can do one defined action at a time, but open-ended work or many choices cause stalling.
Example from the book
Open the account, read the balance out loud, scan only what is due in the next seven days. Ninety seconds.
Write your minimum dayThree operating modes, not three grades.
Full Power does not make you good. Low Power does not make you weak. Restart does not mean you failed. Low Power keeps a running system alive at reduced capacity. Restart recovers orientation after the system has stopped: a different job.
- 1
Full Power
Build and progress.
The complete useful version for ordinary or higher-capacity days.
- 2
Low Power
Protect what matters.
The smallest version that protects the most important outcome and reduces tomorrow's damage.
- 3
Restart
Find your way back.
The shortest procedure for getting back to a trustworthy current state after a system has been ignored, buried or abandoned.
Six parts make each gear usable.
- 1Trigger
- What observable event begins it. After I make coffee on the first workday is visible. Remember on Sunday is weak.
- 2Next visible action
- What the body can actually do. Put every tax document into one folder, not work on taxes.
- 3Home
- Where the current state lives. Without one named home, every session starts with reconstruction.
- 4Friction
- What makes the useful action easier or harder: the password, the missing cable, the six-step login.
- 5Stop rule
- What counts as enough for this session: a time, a number of items or a visible stopping point.
- 6Restart marker
- Where the returning person looks first. The place the state note lives.
Design the gears in order. Start with the protected outcome: what must still be true after a bad week. Build Low Power around it, add depth for Full Power, and build Restart around the shortest path back to a state you can trust.
A worked example from the book
Marcus and the app he will not open.
Marcus is a composite character, not a real person. This is an administration example, not financial advice.
- Protected outcome
- No essential payment fails silently, and I never go more than a week blind.
- Full Power
- A good Sunday: open the account, categorize the week, check every upcoming bill, cancel one thing I do not use.
- Low Power
- Open the account, read the balance out loud, scan only for anything due in the next seven days. Ninety seconds.
- Restart
- Do not read a month of transactions. Check only that rent and the two essential bills are covered. Write down today's balance. Close it.
- Stop rule
- The moment the next seven days are checked. Not one transaction more.
- Restart marker
- The phone lock screen, carrying the date of the last money check.
Abandonment by design
Imagine it ignored for fourteen days.
Run this test on any system that matters. Ask: what damage accumulates, what information goes stale, what expires, what becomes hard to look at, what single safeguard would reduce the damage, and what would get me back to a trustworthy state in ten minutes?
The standard is not zero interruption. It is low return cost.
Build your three gears