Facebook Feed Test Moving Post Actions into the Overflow Menu: Metrics and Launch Call

Facebook is testing a change to the News Feed: the row of like, comment and share buttons that normally sits under every post is removed, and those actions are moved into the three-dot (overflow) menu in the post's corner. The aim is a denser feed, with more posts fitting on the screen at once. You are the product manager reviewing this test. ### Clarifying Questions - Does the test run on the mobile apps, desktop or both, and does it cover every post type, including Pages, groups and ads? - Are the reaction and comment counts still shown on each post, or does that summary disappear along with the buttons? - Beyond fitting more posts on screen, what outcome is the team after: more content consumed, more ad impressions, or a cleaner look? - How are users assigned to the test, and how long has it been running? ### Part 1 — Metrics you expect to move Name the metrics you expect this change to affect, the direction you predict for each, and your reasoning. Separate the metrics the change is meant to improve from the ones it puts at risk. ```hint Follow the extra tap Every reaction, comment and share now takes an extra step. Trace that friction past the person scrolling to the people who wrote the posts. ``` #### What This Part Should Cover - Consumption metrics tied to density, such as posts viewed per session, and their expected direction. - Viewer interaction metrics broken out by action type, with a reason some fall harder than others. - Second-order effects on creators, feed ranking, the overflow menu's other actions, and ads. - Long-term health metrics such as daily usage and retention, where the direction is uncertain. ### Part 2 — Deciding on full rollout The results are in. Explain how you would decide whether to ship the change to everyone: what counts as success, what would block a launch, how you would confirm the result is trustworthy, and what you would do with a mixed outcome. ```hint Price the trade-off The change buys density with lost interactions. Decide before reading the results how much interaction loss a given gain is worth, and over what time horizon you will judge it. ``` #### What This Part Should Cover - Launch criteria set in advance: a primary metric plus guardrails with thresholds. - Validity concerns specific to a social feed, such as novelty or learning effects and interference between test arms through shared creators. - Options beyond a yes or no, such as design variants, a partial rollout and a long-term holdback. ### What a Strong Answer Covers - The goal of the change stated up front, with the core tension between more content seen and fewer active interactions. - Recognition that likes and comments also drive creator motivation and feed ranking, so losses spread beyond the viewer. - A concrete, pre-agreed decision rule rather than a list of metrics to watch. - Short-term versus long-term effects, with a way to measure the long-term ones after launch. ### Follow-up Questions - Posts viewed per session rose 8 percent but comments per user fell 15 percent. Would you launch? - How would you measure the effect on people who post when their audience is split across both test arms? - The feed's ranking model learns from interactions. How would you keep the test from distorting what it learns?