...
Review design from Notification consolidation design (Nikodem)
Requirements: Customizable notifications
Digest Configuration message - review question from Nikodem and decide next steps
Simplify design to implement by Sprint 121 (are there other options? admin UI flexibility?)
...
Time | Item | Presenter | Notes | Questions |
|---|---|---|---|---|
Notifications design overview - Opt in | Nikodem |
|
| |
Alternative approach - Opt out |
|
Examples
Message behavior today: All messages are sent as one-offs today.
Consolidated message
User takes an action to consolidate their messages, to receive something such as:
There are 5 requisitions waiting for your approval, click here to approve them <--- this link would just be to the approve page
Consolidated Message Opt-out
User takes an action to opt-out of messages (groups/types/classifications/tags)
User sees ^, they can either opt-out or receive of single messages or consolidated messages: none, per-change message, consolidated or per-change & consolidated.
What we want
Desire is to change the default system behavior so that the ‘default’ for a user is to get fewer messages.
Thoughts:
First option might be more in-line with user feedback
Second option isn’t precluded, however does it have shorter lifespan
We don’t have new notification message requirements from stockmangement, CCE, etc (Sam I got behind here) that describe frequency, digest preferences
Action items
- Nikodem Graczewski (Unlicensed) LOE for both options, loop Josh Zamor in