Name the breakdown
Use a concrete sentence: “I skip the action when the meeting runs late,” not “I have no discipline.”
Use case: repeated restarts
If the same habit keeps restarting, stop repeating the same method.
A restart can look like a motivation problem when the real issue is that the action, cue, timing, or fallback never changed. Treat the next week as a test of the method, not a verdict on you.
What should you change first?
Change one controllable part of the method: make the action smaller, attach it to a clearer cue, move it to a more realistic time, or define a fallback for difficult days. Test only one version long enough to observe what happens.
A four-step reset
Replace the restart with a weekly experiment.
Choose one smaller method
Select a version that can happen under ordinary conditions, not only on your best day.
Prepare the fallback
Decide the reduced action before friction appears. The fallback is part of the method, not a punishment.
Review the signal
At week-end, ask whether the chosen method fit the real situation and what one variable should change next.
What ChangeLoop 7 constrains
Less room to negotiate with the plan.
| Moment | Product constraint | Reason |
|---|---|---|
| Start | Choose one of three methods | Avoid carrying several competing plans into the week |
| Each day | See only today's action | Keep future planning from replacing present action |
| Missed action | Use a prepared fallback | Learn whether a smaller version can survive friction |
| Week-end | Write one review | Update the next method from the week you actually had |
A restart is data
Test a different method for one cycle.
No seven-day experiment can guarantee a permanent habit. The useful outcome is a clearer next decision supported by what happened.
Start the free cycle