Rollout Plan and Launch Monitoring for Facebook's Expanded Reactions

You are the product manager at Meta who owns Facebook Reactions, the set of emotional responses people can leave on a post in addition to Like. You are responsible for releasing it. Explain your release strategy, and then how you would monitor the release. ### Clarifying Questions - Is this the first release of Reactions, or a change to a set of reactions that already exists? - What is the release meant to achieve: more feedback on posts, more people posting, or richer signals for ranking Feed? - Does the release cover every app and surface at once (mobile apps, web, Pages, ads), or only some of them? - Is there a fixed launch date that limits how long testing can run? ### Part 1 — Release strategy Describe how you would take Reactions from a finished build to everyone on Facebook: the stages, who gets the feature when, what you would test before going wide, and which teams and outside audiences you would prepare. ```hint Others see what you react with A reaction is seen by the person who posted and by everyone else who views the post, so giving the feature to some users affects people who never received it. Let that shape how you stage and test the rollout. ``` #### What This Part Should Cover - Release stages from internal use to full launch, with exit criteria for each stage. - A test design that holds up when the feature is visible across friend networks, and that checks how different cultures read the emotions. - Readiness across apps, older app versions, Pages, advertisers and developers, plus the communication plan. ### Part 2 — Monitoring the release Explain what you would watch during and after the rollout, how often you would look, and what would make you pause, roll back or keep going. ```hint Different signals, different clocks Some problems show up within minutes of a ramp step and others only after the novelty fades. Decide which signals belong to each time frame, and include the people who receive reactions, not only those who give them. ``` #### What This Part Should Cover - Health, adoption and impact metrics, each tied to the release goal. - Guardrails for cannibalization of comments and Likes and for effects on posters, Feed and integrity. - Decision rules agreed before launch, rollback triggers, and how long-term effects are measured. ### What a Strong Answer Covers - A stated goal and hypotheses for both the people who react and the people who receive reactions, driving the rollout and the metrics. - A rollout that manages risk while accounting for network effects and cultural differences. - A metric set that separates health, adoption and impact, with guardrails and pre-agreed decision rules. - Attention to novelty effects and to measuring long-term impact. - Coordination with the teams the change touches: Feed ranking, integrity, Pages and ads, the developer platform, marketing and support. ### Follow-up Questions - In the test, Likes fall while the total of Likes and reactions rises. How do you decide whether that is a good result? - How should Feed ranking weigh each reaction type, and how would you test that choice? - Angry reactions turn out to cluster on news and political posts. What would you do?