Set Notification Preferences by Urgency
Design a preference center that lets people control channels, timing, and topic frequency while protecting truly essential account messages.
The brief
Understand the problem
Background
Preference centers often offer a wall of toggles with unclear consequences. People want fewer interruptions, but products must still deliver security, billing, and service messages that cannot safely be silenced.
User context
Dev receives the same project activity by email, push notification, and in-app alert. He wants immediate notice for assigned blockers, a daily digest for comments, and no promotional messages.
Product problem
People need understandable control over topic, channel, and timing without accidentally disabling critical communications or creating duplicate deliveries.
Objective
Create a preference center with sensible grouping, quiet hours, delivery previews, and protected-message explanations.
What to design
Define the experience
Required experience
- Review current preferences by purpose rather than channel alone
- Set urgency, channel, and frequency for a notification group
- Configure quiet hours with exceptions
- Preview and confirm the resulting delivery plan
Screens and states
- Preference overview
- Topic detail
- Quiet hours
- Delivery summary
Core user flow
Follow the critical path
- 01
Dev opens notification settings and sees activity, account, and marketing groups
- 02
He sets assigned blockers to immediate push and comments to a daily email digest
- 03
He adds overnight quiet hours while allowing verified security alerts
- 04
The summary explains which messages remain mandatory
- 05
Dev saves and receives an accessible confirmation with an undo option
Product rules
Requirements and constraints
Requirements
- Explain notification groups with representative examples
- Support channel availability, frequency, quiet hours, and urgent exceptions
- Prevent equivalent events from producing redundant cross-channel alerts
- Identify legally or operationally required messages and explain why they remain enabled
- Show when changes take effect and where pending digests will go
Constraints
- Available channels depend on verified contact details and device permission
- Security and transaction records cannot be categorized as marketing
- The controls must remain usable with screen readers and keyboard input
Reality check
States worth considering
Finish line
What to deliver
- Four responsive screens covering personalized settings, a protected message, and one unavailable channel
Optional direction
Visual resources
Use these as a starting constraint if you want one. They are not part of the required solution.
Montserrat & Crimson Text
Clear interface writing gives people the confidence to understand what changed and decide what to do next.
Montserrat & Crimson Text
Clear interface writing gives people the confidence to understand what changed and decide what to do next.