Reminders Without Nagging: The Ethics of Notifications
By Maksym Bardakh · Co-founder & President
In short
A notification interrupts a person’s life, so the ethical bar is whether it serves the user rather than the product’s engagement numbers. Helpful notifications are timely, relevant, and respectful of frequency; manipulative ones manufacture urgency to pull the user back. The honest standard is to send only what the user would thank you for, and to make control easy.
A notification is borrowed attention
Every notification is an interruption. It takes a person away from whatever they were doing and asks for their attention, attention that belongs to them, not to the product. This framing sets the ethical bar. A notification is justified when it returns more value to the user than the interruption costs them, and it is not justified when it serves the product’s metrics at the user’s expense.
The distinction between a reminder and a nag is exactly this. A reminder helps the user do something they wanted to do. A nag pulls the user back to the product for the product’s benefit, dressed up as help. The difference is whose interest the notification serves.
The patterns that cross the line
Manipulative notification design has recognizable patterns, and naming them helps avoid them. Manufactured urgency, badges and alerts for things that are not time-sensitive, pressures the user with false stakes. Engagement bait, notifications whose real purpose is to reopen the app, wastes the user’s attention. High frequency trains the user to either obey or ignore, neither of which respects them.
- Do not manufacture urgency for things that are not actually urgent.
- Do not send notifications whose real goal is to drive the user back into the app.
- Do not normalize a high volume that the user must either obey or learn to ignore.
What a helpful reminder looks like
A genuinely helpful notification is timely, relevant, and rare enough to be trusted. It arrives when it is useful, concerns something the user actually cares about, and does not compete with a flood of others for the user’s attention. When notifications are kept to those that matter, each one carries weight and the user learns that an alert from this product is worth reading.
Control belongs to the user
Even well-intentioned notifications should be under the user’s control, because needs differ and change. Granular settings that let a user choose what to be notified about, sensible defaults that do not over-notify, and an easy path to reduce or stop notifications are all expressions of respect. A product confident that its notifications are valuable does not fear giving the user the power to turn them off.
For software meant to support people, especially those for whom attention is already strained, this matters even more. The goal of a reminder is to help the user act on their own intentions, not to capture their attention for the product. Designed honestly, notifications become something the user welcomes rather than something they brace against.
Key takeaways
- A notification borrows the user’s attention and must return more value than it costs.
- A reminder serves the user; a nag serves the product while pretending to help.
- Avoid manufactured urgency, engagement bait, and high frequency.
- Helpful notifications are timely, relevant, and rare enough to be trusted.
- Give the user easy, granular control and defaults that do not over-notify.
Frequently asked questions
- What separates a reminder from a nag?
- Whose interest it serves. A reminder helps the user do something they wanted to do, while a nag pulls the user back to the product for the product’s benefit, dressed up as help.
- How do I know if a notification is ethical?
- Ask whether the user would thank you for it if they understood exactly why it was sent. If the honest answer is no, it is serving the product rather than the person.
- Should users be able to turn notifications off easily?
- Yes. Granular controls, sensible defaults, and an easy path to reduce or stop notifications respect the user, and a product confident in its notifications does not fear giving that control.
References
About the author
Maksym Bardakh
Co-founder & President
Maksym is a software engineer and product strategist focused on executive-function and behavioral system design. At BBMM he leads product direction across Flowo, TextPack, and Pillow, working at the intersection of human cognition and durable interface design.