Why streaks fail, and a kinder way to count them

Updated 7 October 2026

The short answer: a streak that resets to zero punishes the one bad day more than it rewards the fifty good ones. Count "days on course" instead, let planned rest days pause the count, and earn an aid station every seven days to cover a miss.

The problem with zero

Day 47 of a streak and you're ill, or travelling, or just exhausted. The counter goes to zero. For most people the motivation goes with it; the app gets deleted within the week. The streak was supposed to build consistency, and instead it taught all-or-nothing thinking.

A better rule in three parts

1. Define a good day generously. In KeepCourse a day is "on course" when you've done your morning standup and kept at least half of that day's commits. One missed commit doesn't lose the day.
2. Rest days pause, they don't break. A planned rest day, a sick day, a travel day: the count holds. Recovery is part of training, not a failure of it.
3. Earn cover for the unplanned miss. Every seven days on course earns an aid station, like the water stops on a marathon course. Miss a day with one in hand and it's used automatically. You can hold two.

Keep the personal best

Even if the current count breaks, the best run you've ever had stays on the screen. People don't come back to a zero; they come back to beat a 47.

Celebrate the return, not just the run

The day after a break is the most important day in any habit. Treat "back on the line" as a win, with the same celebration as a milestone, because that's the behaviour you actually want to reinforce.

What to measure instead of the streak

Your month as a line: which days were on course, where you drifted, and whether the drift is random or always on Mondays. Patterns are fixable; a number isn't.

How KeepCourse helps

Days on course, aid stations, rest days and personal best are built in, and your week is drawn as a line against the plan so you can see the drift instead of a counter.