Missed one day, then quit entirely
Eleven days of running, one genuinely bad Tuesday, then nothing for a month. The streak was the reason you were going, so breaking it removed the reason.
Disclosure. We make Commit, and it appears in one section near the end. Everything before that works without it, and without any app at all.
The short answer
The skipped day is not the damage. The zero on the counter is. So the repair is structural: restart today at a fraction of the size, and track your rate, not your longest run.
Why one day takes the whole thing
Eleven days in, the number is the reason you go. Nothing has visibly changed about your body yet, so the counter is the only feedback there is. Then Tuesday brings a nine o'clock finish and it reads zero.
Dieting researchers named what comes next the “what the hell” effect: once people believe the rule is already broken, they overshoot rather than return to baseline (Polivy & Herman, 1985). The rule was doing the restraining, so breaking it removes it.
Eleven consecutive days is a good month. To an all-or-nothing standard it reads as a failed attempt, and the honest response to a failed attempt is to stop.
Count the rate, not the run
A streak counter withdraws every bit of motivation it has built at the exact moment you need it most. Its value lives entirely in its continuity.
One caveat: where consecutive days are the outcome — nicotine, alcohol, medication — the run really is the measure.
What a system needs to survive day twelve
- A finite allowance for bad daysGrace has to cost something, or it stops being grace and becomes the absence of a rule.
- Recovery framed as normalA day marked skipped should not feel identical to a day marked missed.
- Something outside your own headPeople who notice you are missing, on a schedule your motivation does not control. A feed of thousands notices nobody.
- A rate as well as a runSo one miss lands as a data point rather than a verdict.
What to do the morning after a miss
- 01Restart today, at a quarter of the sizeFive minutes, one page, one set. You are closing the gap, not making up ground — the gap is the part that grows.
- 02Do not make up the sessionDoubling up turns a bad day into a punishment, which makes the next miss easier to hide.
- 03Name the cause, change one thingNot “no motivation” but “worked until nine, kit in the wash”. Most misses are logistics.
- 04Write the recovery rule now“If I miss a day, I do the five-minute version next morning.” An if-then plan hands the decision to a trigger rather than to the judgement that just failed (Gollwitzer, 1999).
- 05Restart the count, keep the recordDelete nothing, and tell one person the same day. It moves the miss out of your own head.
How Commit handles the twelfth day
Our answer is a grace token, and the design choice that matters is that they are finite: ten to start, one more at 7, 14, 21 and 30 days.
- It works after the break, not only before itSpend one within 48 hours and the day is marked skipped, the eleven days stay, and any stake is reversed.
- The day is not written off at the deadlineA 30-minute grace window before anything is marked, then several hours more to submit late proof.
- A shared group streak freezes rather than breaksIt holds while anyone's proof is waiting on review, so a slow reviewer cannot end a run others showed up for.
- Tokens cannot be boughtTen makes a bad day forgivable. Ten spent on ten consecutive Tuesdays is not bad luck, it is a commitment you do not want.
Common questions
Should I restart at zero or keep the old number?
Restart the count and keep the log. Twenty-nine completions with one gap keeps the only thing worth keeping: evidence that you did it twenty-nine times.
I stopped three weeks ago. Is it too late?
Nothing expires. What changes is the starting size: restart at the level you could have managed on your worst day of those three weeks.
How many days can I miss?
Pick a band, not a number. A rolling 85 percent allows four missed days a month. What matters is how many you miss in a row.