The Product Manager's Guide to Smart Notifications

Notifications are the most abused feature in modern product design. Every app wants your attention, and most of them have no business demanding it.

Smart notifications aren’t about clever algorithms or machine learning models. They’re about respecting user attention as the finite, valuable resource it is. Get this wrong and you’re not just annoying — you’re actively damaging your relationship with users.

The Current State of Notification Design

Let’s be honest about where we are. Most notification strategies follow this depressing pattern: blast everything to everyone, then maybe personalise later once engagement drops. It’s backwards, and it’s killing products.

What Users Actually Experience

Open your phone right now. How many notification badges do you see? How many of those notifications actually matter to you? I’d bet the ratio is dismal.

Slack’s team figured out early that notification overload would kill them. They invested heavily in notification controls — granular settings for channels, keywords, mentions. It’s not perfect, but it shows they understood the problem. Compare that to nearly any consumer app that treats every user action as equally worthy of interruption.

Instagram sends you a notification when someone you barely know likes a post from three days ago. LinkedIn wants you to know your connection’s work anniversary. Twitter — sorry, X — will invent reasons to notify you just to goose engagement metrics. Even if you have your notifications turned off, they will “scream” to enable these notifications. It’s… exhausting.

The Technology We Have Now

Modern platforms give us sophisticated tools: ML models for predicting notification relevance, delivery time optimisation, rich notification formats, intelligent grouping and summarisation.

Gmail’s nudge feature actually works because it’s selective. “You haven’t responded to this email” only appears when the algorithm is confident you meant to reply. It’s useful because it’s rare. If every email got nudged, the feature would be worthless.

The technology isn’t the problem. It’s how we use it. Or more precisely, how we abuse it.

Where Smart Notifications Actually Work

Let me show you what good looks like, then we’ll talk about why it’s rare.

Context-Aware Timing

Duolingo is famous for persistent reminders, but they’re not stupid about it. They learn when you typically use the app and notify you then, not at 3am when you’re asleep. If you keep ignoring notifications, they back off. Eventually, they send a guilt trip from their mascot, which somehow works better than nagging.

I mean, no one with a clear heart wants Duo to freeze.

Contrast that with Booking.com, which will email you fifteen times about a hotel search you did once. No learning. No adaptation. Just spam with extra steps. Maybe they changed this already, but the wound is still there and it hurts!

Also, just now I got a notification from Ring. Ring that I have disabled a year ago.

Actual Urgency, Not Manufactured Urgency

Your bank notifications when your account balance drops below a threshold? That’s genuinely useful. Uber telling you your driver is 2 minutes away? Perfect timing, directly relevant.

Your meditation app telling you it misses you? That’s manipulation pretending to be helpfulness. I don’t need fake emotional manipulation from software trying to hit engagement targets.

Amazon’s delivery notifications get this right. “Your package has arrived” is information I want exactly when I want it. “Would you like to review this product?” three days after delivery is fine as an email. As a push notification, it’s intrusive.

User Control as a Feature

YouTube’s notification system lets you choose precisely which creators trigger notifications and for what type of content. This level of control respects that users have different relationships with different channels.

Superhuman’s approach to email notifications is instructive. Default is zero. You have to opt into notifications explicitly, and they’re structured around importance, not recency. The assumption is that most email doesn’t require immediate attention, and they’re right.

Building Technology That Respects Users

If you’re adding notifications to your product, or trying to fix a system that’s currently broken, here’s what actually matters.

Start With “Should We?”

Before you build intelligent notification routing, ask whether you should be notifying at all. What’s the user’s actual need here? What problem does this solve for them, not for your engagement metrics?

At one fintech startup my colleague worked for, product wanted to notify users about every account activity. Security’s impulse was right — fraud prevention matters. But notifying about every coffee purchase creates notification fatigue. When a genuinely suspicious transaction happens, users have trained themselves to ignore alerts.

I suggested they implement a tiered system: high-value transactions get immediate notifications, routine purchases get summarised daily, tiny charges (like subscription renewals) don’t notify unless they fail.

Fraud detection would improve because users actually paid attention to alerts that mattered.

Make Silence the Default

Here’s a controversial take: most notifications should be opt-in, not opt-out. Yes, this will reduce your notification send volume. That’s the point. Quality over quantity.

Hey, the email service, sends almost no notifications. You get email, you check it when you want. Groundbreaking concept, apparently. And yet their users are more engaged than platforms that interrupt constantly, because when Hey does notify you, it’s actually important.

Learn and Adapt

If users consistently dismiss a certain type of notification, stop sending it. This should be automatic, not something you analyse quarterly and maybe adjust.

Netflix used to notify about every new show or movie that matched your interests. It was overwhelming. Now they’ve pulled back significantly, focusing on major releases and shows from creators you’ve watched extensively. The reduction in noise makes remaining notifications more effective.

Provide Granular Controls

Don’t make users choose between “all notifications” and “none.” Give them actual control over what they want to hear about and when.

Signal handles this beautifully for a messaging app. You can mute individual conversations, set custom notification schedules, even customise sounds per contact. Privacy-focused products often get UX right because they can’t fall back on dark patterns.

What’s Coming Next

The technology is evolving, and some of it is genuinely promising rather than just more sophisticated manipulation.

Predictive Notification Intelligence

We’re moving toward systems that understand not just what to notify about, but when you’re receptive to different types of information. Your calendar is free for 30 minutes? Maybe now’s good for that newsletter. Driving? Everything waits except true urgency.

Apple’s Focus modes are a step in this direction, though implementation is still clunky. The idea is sound: context should determine what breaks through, and users should control the rules.

Cross-App Notification Management

Currently, every app manages notifications independently. The platform provides some grouping, but it’s basic. We’re headed toward smarter intermediation—notification managers that understand your patterns across all apps and surface what matters when it matters.

This requires platforms to provide better APIs and users to trust an intermediary with access to their notification stream. Both are happening gradually.

Preparing Your Team

If you’re building notification features now, design for a future where users expect intelligence and control. That means:

Building robust preference systems from the start, not bolting them on later
Collecting data about notification effectiveness and user response
Creating feedback loops so your system learns from user behaviour
Defaulting to less rather than more

The bar for good notifications is rising. Users tolerate less nonsense every year. Build with that trajectory in mind.

Key Takeaways

Here’s what matters for smart notifications:

Default to silence: Only notify when you have information the user actively needs right now. Wants and needs are different, and most notifications are wants disguised as needs.
Respect context: The same notification might be valuable at 9am and intrusive at 9pm. Time, location, and user state should inform delivery.
Learn from behaviour: If users consistently ignore a notification type, stop sending it automatically. Don’t wait for them to disable notifications entirely.
Provide genuine control: Granular settings aren’t extra work—they’re respect for user autonomy. Build them from the start, not after users revolt.

The Real Test

Here’s how you know if your notification strategy is good: ask your team if they have notifications enabled for your own product. If the answer is no, you’re doing it wrong.

I keep notifications on for maybe six apps. Gmail (with strict filters). Messages from actual humans. Banking alerts. Calendar reminders. Navigation when active. That’s it.

Everything else either respects me enough not to interrupt constantly, or I’ve trained myself to ignore it. Your product falls into one of those categories. Choose wisely.

Have questions or thoughts? Get in touch - I’d love to hear from you!