Purpose, Goals and Success Metrics for the Notifications Bell in Meta's Mobile App

Meta's mobile app has a bell icon that opens the user's notifications. Explain why Meta built it, then set goals for it and describe how you would measure whether it succeeds. ### Clarifying Questions - Which app is in scope? The Facebook app is the natural candidate, since its bell opens the notifications list. - Does the bell's scope include push alerts sent to the phone, or only the in-app list and its unread badge? - Am I explaining the original decision to build the bell, or owning it today and setting goals for the coming year? - Should the goals center on what users get from notifications, on Meta's retention and ad business, or on both? ### Part 1 — Why Meta built the bell What user and business problems does the bell solve, and why was one notifications entry point in the app's main navigation worth the space it takes? ```hint Picture the app without it Suppose a friend replies to your comment while you scroll the feed. Without a dedicated place for activity aimed at you, where would you learn about it, and what would that mean for you and for the friend who replied? ``` #### What This Part Should Cover - The needs of people who receive activity and of people who post and wait for responses - How the bell supports Meta's mission and its ad-supported business - Why a persistent icon with an unread badge was chosen over relying on the feed or on push alerts alone ### Part 2 — Goals and success metrics Set goals for the bell and define how you would measure its success, including the signals that would tell you it is causing harm. ```hint Separate a tap from value A red badge earns taps from curiosity and from annoyance alike. Look for measures showing that an opened notification led to something the user valued. ``` #### What This Part Should Cover - A goal stated as user value and a primary metric that reflects it - Supporting metrics along the path from badge shown to notification opened to a meaningful action - Guardrails for notification fatigue and for time pulled away from other surfaces - A way to attribute outcomes to the bell rather than to users who were already engaged ### What a Strong Answer Covers - A clear line from the purpose described in Part 1 to the goals and metrics in Part 2 - Attention to both people in a notification: the recipient and the person whose action triggered it - A primary metric that rewards relevant notifications rather than raw badge taps - Guardrails covering fatigue, opt-outs and cannibalization of other surfaces - A method that establishes causal impact instead of correlation with active users ### Follow-up Questions - After a change adds new notification types, bell opens rise but daily active users stay flat. What would you investigate? - How would you decide which notifications earn a badge count and which appear in the list silently? - Leadership proposes moving the bell into a secondary menu to free navigation space. How would you evaluate that proposal?