Autonomy isn’t the absence of effort. It’s the point where a system has carried you through at least one genuinely hard week without you forcing it. The Autonomy Checkpoint makes that specific, and puts an actual date on your calendar.
A vague plan to revisit this sometime
Vague plans to revisit something sometime are exactly the kind of intention this whole approach is built to catch.
Setting a real date matters more than it sounds like it should. Autonomy is a specific, checkable thing, not a feeling, and it deserves a specific, checkable moment to confirm it.
Who this is for, and how long it takes
About 7 minutes. Works best after The Foundation Phase Planner and The One-Variable Adjustment Plan.
What’s inside
- A definition field.
- A date field.
How to get the most out of it
Put the date somewhere you’ll actually see it, not just in this worksheet.
What changes if you actually do this
The output is a defined finish line and a real date. The outcome is a concrete way to know the system is holding, not a guess. The impact is that the system gets checked instead of quietly forgotten.
Download The Autonomy Checkpoint
Next step: My Shift Wheel, the one-page document that compiles everything from this whole library.
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 final phase, Autonomy.
What if my check-in date arrives and the system isn’t running on its own yet?
That’s useful information. Go back to The One-Variable Adjustment Plan and adjust again.
How long should I wait before setting this checkpoint?
Long enough to include one genuinely hard week, often around 4 to 6 weeks from when you start the Foundation phase.
