Reminders and Habit Anchors
Tie the action to a moment the user already has, then remind them there.
The problem it solves
People intend to use the product and forget. A reminder detached from context gets dismissed. A reminder tied to an existing routine gets acted on.
An anchor is an existing, reliable event in the user's day: morning coffee, the commute, sitting down at the desk, lights out. The pattern is to attach the new behaviour to the anchor and use the reminder as a cue at that moment, rather than at a time the product finds convenient.
The difference in practice is who chooses the time. A product that picks 7pm because that is when engagement peaks is sending an interruption. A product that asks when the user wants to be reminded and then honours it is sending a cue they set for themselves, which is a different thing arriving through the same channel.
Asking well during setup
- 1Ask what they want to do, in their words, before you ask when.
- 2Ask for the anchor rather than the clock time: after I brush my teeth beats 22:30.
- 3Convert the anchor to a time and show it, so it is editable.
- 4Confirm the first reminder will arrive tomorrow, and let them change or cancel from inside it.
- 5After several ignored reminders in a row, ask whether the time is wrong instead of sending more.
That last step is the one that separates a habit tool from a nagging one. A reminder ignored five times is data. The right response is to offer to change or stop it. Sending a sixth, louder, is treating the user's silence as a problem with their compliance rather than with your timing.
A cue only works if it reliably precedes the behaviour. Place it at the moment of decision, not at the moment of convenience.
Worked example
Same reminder, two designs
A medication app could fire at 9am because that is a common time. Or it could ask what the user does every morning without fail, hear coffee, and set the reminder for when their phone typically becomes active. The second version is acted on because it arrives inside a routine that already exists. The user has to build one fewer new thing.
When it fits
- The desired behaviour is short and repeatable, so it can genuinely attach to an existing moment.
- The user has a stable routine to anchor to, which most people do for morning and bedtime.
- You can let them set, move, and cancel the reminder from inside the reminder itself.
- Missing one occurrence has no penalty attached.
When it backfires
- The time is chosen by the product to hit an engagement peak. The reminder is then marketing wearing the costume of a personal cue.
- Ignored reminders trigger escalation rather than a question. Repeating a cue someone has declined five times teaches them to disable the channel.
- Reminders carry guilt copy. You missed yesterday, do not fall behind, aimed at someone with a health goal is pressure applied to a vulnerable moment.
- The anchor is fictional. Reminding a shift worker at 8am because the average user is awake then produces an alert that is always wrong and never adjusted.
Products using it
Headspace
Asks the user to choose a daily meditation time during onboarding and sends the reminder at that chosen time.
Apple Reminders
Supports location and time triggers, letting a cue fire on arriving somewhere rather than on the clock.
Streaks
Lets each tracked task carry its own reminder time and repeat schedule, set per habit by the user.
The psychology under it
The takeaway
A reminder the user scheduled around their own routine is a cue; the same message sent at your peak engagement hour is an interruption with better copy.
Finished the teardown? Bank it and the day counts toward your run.