Most systems don’t fail because they were wrong. They fail because nobody decided, in advance, what to do the first time it stopped sticking. The One-Variable Adjustment Plan makes that decision now, before it’s needed.
Change one thing, never the whole system
Most people only ever run the foundation phase, then quietly stop the first bad week and read that as proof the plan didn’t work. It usually just means no one had decided what to adjust.
The fix is smaller than people expect: change the trigger or the action, never the whole system at once.
Who this is for, and how long it takes
About 7 minutes. Works best after The Foundation Phase Planner.
What’s inside
- A pre-decision field.
- A signal field.
How to get the most out of it
Write this down even if nothing feels wrong yet. It’s much harder to think clearly about it once something actually slips.
What changes if you actually do this
The output is a pre-decided adjustment. The outcome is a specific, calm response instead of a panicked restart. The impact is fewer systems abandoned at the first real test.
Download The One-Variable Adjustment Plan
[Download button placeholder, to be added.]
Next step: The Autonomy Checkpoint, for defining what running without you actually looks like.
FAQ
How is this different from the full 90-Day Implementation Plan?
The full plan covers all three phases in one document. This is just the middle phase, Adjustment.
What if I don’t know what to change yet?
Start with the trigger. It’s the most common point of failure, and the easiest to test.
Can I use this more than once for the same system?
Yes. Systems usually need more than one adjustment before they hold.
