Maintenance Is a Different Game: Design for the Lapse + the Honest Ceiling

Reviewing over a hundred theories of how behavior change is sustained, researchers found that the motives that maintain a behavior differ from the motives that initiate it. You start something on excitement, a goal, a fresh token, the novelty bonus. None of those last, by design (that's the whole cliff). What actually sustains a behavior is a different, more boring set of forces: automaticity (the cue→behavior wire from 8.1-8.3, named in that review as "the most sustainable mechanism for maintenance"), a stable supportive context ("stable contexts make behaviour and habits easier to sustain"), and other people (you're more likely to maintain a behavior when you feel connected to and supported by a trusted group). Notice what's not on that list: more willpower, more motivation, more wanting it. Maintenance was never going to come from grit, grit is the starter fuel, and starter fuel runs out. So you stop trying to re-motivate yourself into keeping a habit and instead lean on the three things that actually carry it: the cue you built, the context you protected, and a person who's in it with you. Now the rule that makes all of it survivable, and it pays off the promise from 8.2: design for the lapse, because the lapse is coming. Remember Lally's finding, missing one day did not materially impair habit formation. The curve is robust to a slip. This matters enormously for your brain specifically, because the ADHD failure mode isn't usually the missed day, it's the story about the missed day: "I broke the streak, so it's over, so why bother," and one skipped Tuesday becomes three skipped weeks. The rule that defuses that is simple and you should write it down: a missed day is data, not a verdict, never miss twice. One miss is the curve; two misses in a row is the start of a new (bad) habit. So the only rule you have to actually hold is: get back on the cue at the very next opportunity. That's the rule that survives the storm, because the storm will take a day, the question was never whether you'd lapse, it's whether you'd designed for it. Now the honest ceiling, named straight because that candor is the brand. Look again at the maintenance list: automaticity, stable context, and people. This format can hand you the first two, the mechanism, the cue, the design. It cannot be the third. And the research is uncomfortable here: the same EF deficits that make these systems necessary are the ones that make them hard to sustain, the documented reasons people drop behavioral programs are forgetting to use the skills, losing the materials, not following through. A self-paced course is, structurally, asking the exact part of your brain that struggles with follow-through to carry its own follow-through. That's the format's honest limit. The most reliable patch for it is the one that keeps showing up across this whole course: a person. Someone who shares the cue, notices the lapse, asks how week three went. On the evidence that social carrier is among the strongest maintenance forces there is, and it's the one piece this page genuinely can't install for you. So the highest-leverage thing you can do for everything you've built in this module is to recruit one. We'll build that layer properly in Module 10. For now, name them.