A system you build in one sitting doesn’t automatically survive real life. The Foundation Phase Planner is the first of three steps for giving it enough structure to actually be tested.
Why most new systems collapse within a month
In program delivery work, from Enactus and AMIDEAST to Millennials Consulting, I learned the same lesson every time. A plan survives its first month by design, not by luck.
The plans that fell apart weren’t badly conceived, they just had no built-in moment for adjusting the one thing that was actually broken.
Who this is for, and how long it takes
About 7 minutes. Needs a system already designed, from whichever exercises you’ve completed.
What’s inside
- A field for reconfirming intention.
- A field for the rhythm you’re running.
- A field for logging misses without judgment.
How to get the most out of it
Decide how you’ll log a miss before you have one. It’s harder to think clearly about it in the moment.
What changes if you actually do this
The output is a foundation plan. The outcome is a system that’s actually being tested, not just hoped for. The impact is fewer systems abandoned after the first bad week.
Download The Foundation Phase Planner
Next step: The One-Variable Adjustment Plan, for deciding what you’ll change before you need to.
FAQ
How is this different from the full 90-Day Implementation Plan?
The full plan covers all three phases, Foundation, Adjustment, Autonomy, in one document. This is just the first phase.
Do I need a fully built system to use this?
You need at least a rough intention and a rhythm. It doesn’t have to be polished.
What counts as a “miss”?
Any day the action didn’t happen as planned. Log it plainly, without a story attached.
![Why Does Your System Only Work When You Feel Like It? (The Two Parts Every System Actually Needs) Every system that holds has the same starting point: a fixed trigger and one small, defined action. The Trigger-Action Designer builds both in about 7 minutes, the two parts most plans skip in favor of just deciding to try harder. A system is a structure, not a feeling At IBM, we didn’t manage large accounts by hoping the team felt inspired on a given Tuesday. We built fixed checkpoints, specific and repeatable. I didn’t think of that as a life skill at the time. It is one. A trigger has to be fixed, never “whenever I feel like it,” and an action has to be small enough to do without deciding. Who this is for, and how long it takes About 7 minutes. For anyone who has an intention but no system carrying it yet. What’s inside A trigger field. An action field. A worked example. How to get the most out of it Resist making the action bigger than it needs to be. Small enough to do without deciding is the whole point. What changes if you actually do this The output is one designed system start. The outcome is that the action becomes something you don’t have to decide on. The impact is that your intention gets a structure to run on. Download The Trigger-Action Designer [Download button placeholder, to be added.] Next step: The Follow-Through Tracker, which adds the part most systems skip and runs the whole thing for the first time. FAQ How is this different from the full Continuity Design Template? The full template includes the follow-through step too, in one sitting. This is the first half, for a quick start. What if I can’t think of a good trigger? Anchor it to something that already happens every day, closing your laptop, making coffee, a specific time. Consistency matters more than cleverness. Does this work for team systems, not just personal ones? Yes. The same trigger-and-action logic applies to a team habit as much as a personal one.](https://yassinebentaleb.com/wp-content/uploads/2026/07/Why-Does-Your-System-Only-Work-When-You-Feel-Like-It-The-Two-Parts-Every-System-Actually-Needs-350x250.png)
