Your Reminders Aren't Working. Here's Why.
The Reminder You Dismissed This Morning
There it is. 9:15am, you're making school lunches, a reminder pings for something vague. "Call the plumber." You're busy. You swipe it away. By 9:30 you've forgotten what it was. By next week you'll wonder why the boiler still sounds like it's suffering.
The reminder didn't fail because you're forgetful. It failed because it arrived at a time when you couldn't act on it, without enough context to know what to do, and there was no friction to dismissing it. Those are design failures, not personal ones. And they're fixable.
The Timing Problem
The most common reason reminders don't work is that they fire at the wrong moment. A reminder to buy milk that goes off when you're in a meeting is useless. You dismiss it. You don't go back to it. The milk isn't bought. Exactly the same reminder going off when you're getting in the car to go out — ideally to the supermarket — is genuinely useful.
Think about when you're most likely to be able to act on a specific task, and set the reminder for that moment. This requires a small amount of thought upfront but it dramatically increases the reminder's effectiveness.
For anything involving shopping, a reminder that fires when you're near a relevant shop is far better than a time-based one. If you drive past a particular supermarket on the school run, that's when you want the reminder about the things you need — not at 7am when you're nowhere near one.
For household tasks, think about which part of the day you actually have time to deal with them. A reminder about a phone call makes no sense if it arrives during the school run. It makes a lot of sense if it arrives during the twenty minutes between drop-off and your first meeting.
The Vagueness Problem
"Sort out the car" is not a reminder. It's a source of low-grade anxiety that you'll dismiss every time it appears because you don't know what to do with it.
"Book MOT before end of month — garage number in contacts as 'Hills Auto'" is a reminder. It tells you exactly what to do, and it removes the search step that often causes task avoidance. The difference in compliance between a vague reminder and a specific one is significant.
When you capture a task, take the extra ten seconds to make it actionable. Not just the what, but the how, or at least enough context to make starting easy. A reminder that gets dismissed because it's unclear what it requires is just noise.
The Volume Problem
If you have fourteen reminders set for tomorrow, you will develop reminder blindness. Each one becomes slightly less likely to be acted on, and you start dismissing them reflexively. Prioritise ruthlessly. A small number of well-timed, specific reminders is worth far more than an exhaustive list of things someone might possibly need to do at some point.
A useful filter: is this reminder time-critical? Will something go wrong if this doesn't happen today? If yes, it earns a reminder. If it's just "it would be nice to do this sometime," it belongs on a task list rather than as a time-based notification.
Building a System You Trust
The underlying goal of a reminder system isn't the reminders themselves — it's the ability to put a thought down with confidence that you'll be prompted to act on it at the right time. When you trust the system, you stop trying to hold everything in your head. The constant background anxiety of "don't forget the thing" goes quiet, because you know it's captured.
Noa handles reminders as part of the broader task and calendar system, which means they exist in context rather than in isolation. You can add them by voice or WhatsApp the moment something comes up, with whatever context is relevant, and they'll surface at the time you set them. Both partners see the same picture, so nothing falls through the gap of one person having captured it but the other not knowing about it.
The reminder that works is specific, timely, and few enough in number to be taken seriously. It's not complicated to set up — it just requires thinking about the moment of action rather than the moment of capture.
Share this post