Critical Failure of {informativeNotification}
summary
Argues that notifications are often where an application actually occurs for users and lists concrete engineering failures and fixes: misrouted tornado alerts from AccuWeather, a YouTube push 32 minutes late, Plaxo-style “you have a message” anti-pattern, and Calendly-style reminders broken by DynamoDB TTL ~45-minute variance. Recommends instrumenting stages—data received, template compiled, routing, carrier response—adding geo-targeting and user controls, and assigning ownership to product (not marketing/CRM) so notifications are timely and targeted.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:09Where app experience occurs
- 3:49Optimizing user experience
- 5:18Notifications as primary experience
- 8:58Timely notifications matter
- 10:36Targeted user experience
- 13:10Control over notifications
- 16:50Observability for alerts
- 20:31Ownership of notifications
- 22:48Key principles summary
related talks
47mNOTIFICATIONS: Stay Informed
18mBad Metrics and Very Bad Decisions
23mDeciphering Alerts – Why is it so hard to make sense
52mUnderstanding UnHealthy Syndromes of Software Delivery
38mThe Ticking Time Bomb of Observability Expectations
45mHow to Fail Correctly
24mDriving Adoption by Generating High Value Notifications in Backstage
25mEasy notifications for Kubernetes