Template
Define a fallback and its trigger
A backup plan is useful only when you know when to use it. Link the fallback to an observable trigger, preserve what must remain true, and avoid maintaining expensive Plan Bs for every trivial uncertainty.
Before you use it
- Use when
- Failure of one dependency would materially block an important plan.
Keep this limit in mind
- Contingency planning has a cost. Do not create redundant alternatives where failure is cheap and easily reversible.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
A template to use
Primary plan: ___. Failure signal: ___. Latest safe decision point: ___. Fallback: ___. What the fallback preserves: ___.
Why it matters
A backup plan is useful only when you know when to use it. Link the fallback to an observable trigger, preserve what must remain true, and avoid maintaining expensive Plan Bs for every trivial uncertainty.
Check your result
The fallback has a concrete trigger and a latest useful decision point.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingDefine a fallback and its trigger
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaMake accountability about observable work
Evidence and sources
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
Always Have a Backup Plan · data/life-os-content/plan-b-habit-tracker.json
First-party source of this practical exercise.
Provenance for selected structured fields. The exercise is editorial practice; this link supplies no efficacy finding.
Prepare for the Worst While Working Toward the Best · data/life-os-content/minimax-plan-b-playbook.json
Edition and review
Version 0.1.0 · Published
Edition checked · 2026-11-12