Product Critique: Diagnose a Flaw in a Facebook Feature and Propose a Fix

You are a product manager candidate at Meta. Choose one Facebook feature that you personally dislike and talk it through: what the feature is supposed to do, what exactly bothers you about it, which users the problem affects and why it matters, and what you would change. ```hint Turn a gripe into a product problem A personal annoyance is only the starting point. Pick a feature you know well, show that the flaw hurts a group of users you can name, explain why Meta may have built it this way, and only then propose a change. ``` ### Clarifying Questions - Should I stay inside the main Facebook app (Feed, Groups, Marketplace, Events, Notifications), or is Messenger, which runs as its own app, also in scope? - Should I critique the feature as an everyday user, or from the side of a group with different needs, such as Group admins or Marketplace sellers? - Do you want only the critique, or also a prioritized fix and a plan for measuring whether it worked? ### What a Strong Answer Covers - A deliberate choice of feature, with a short account of its purpose and who depends on it. - A concrete diagnosis that names the affected users, the moments where the flaw shows up and how serious it is, kept separate from personal taste. - A fair explanation of the business or technical reasons the feature works the way it does. - Prioritized changes that target the root cause, with the trade-off against Meta's goals stated openly. - Metrics for judging the change, including guardrails on whatever the current design protects. ### Follow-up Questions - How would you check that many users share your complaint, not only you? - Your change improves satisfaction surveys but lowers time spent in an experiment. Would you ship it, and how would you make the case? - The team that owns the feature is measured on the metric your change would lower. How would you bring them along?