Facebook product critique: explain why a feature works and propose an improvement

Quick Overview

A two-part product sense interview question about Facebook: name a feature you like and explain why it works for users and for the company, then propose how to improve it. It tests feature analysis, segment choice, pain-point ranking, prioritization of solutions and success metrics with guardrails.

Facebook product critique: explain why a feature works and propose an improvement

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Name a Facebook feature that you personally like and explain why it works. Then describe how you would make that feature better. ### Clarifying Questions - Is the scope the Facebook app only, or may the feature come from Messenger or other Meta apps? - Should the improvement serve the feature's users first or Facebook's engagement and revenue goals, and how should I weigh them when they conflict? - May the improvement add a new surface built on the feature, or should it change only the existing feature? ### Part 1 — Choose a feature and explain why it works State which feature you picked, who uses it and for what, and why it succeeds both for those users and for Facebook. ```hint Two kinds of value Separate what the feature does for the person using it from what it does for Facebook, and tie each to a specific design choice. ``` #### What This Part Should Cover - A specific feature, defined precisely enough to analyze - The users it serves and the need it meets for them - Why it works, linked to concrete design choices and to Facebook's goals ### Part 2 — Improve the feature Set a goal for the improvement, choose which users of the feature to focus on, find their biggest problem, propose and prioritize solutions, and explain how you would measure success. ```hint Follow one session Walk through a single visit by the user you chose and mark the moment they leave without getting what they came for. ``` #### What This Part Should Cover - A goal for the improvement and a user segment chosen with reasoning - Pain points ranked by severity for that segment - Several solutions compared on explicit criteria, with one prioritized - Success metrics with guardrails ### What a Strong Answer Covers - An improvement that builds on the strengths named in Part 1 rather than jumping to an unrelated problem - The tension between user value and Facebook's engagement or revenue goals, made explicit - Risks such as privacy, integrity or misuse, with mitigations - A clear structure and a firm recommendation ### Follow-up Questions - How would you test your improvement before a full rollout, and what result would make you stop? - If your change made the feature more useful but reduced time spent on Facebook, how would you make the case for shipping it? - How could bad actors misuse your improvement, and how would you prevent it?

Overview: A two-part product sense interview question about Facebook: name a feature you like and explain why it works for users and for the company, then propose how to improve it. It tests feature analysis, segment choice, pain-point ranking, prioritization of solutions and success metrics with guardrails.

Meta logo
Meta
Jan 7, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Name a Facebook feature that you personally like and explain why it works. Then describe how you would make that feature better.

Clarifying Questions Guidance

  • Is the scope the Facebook app only, or may the feature come from Messenger or other Meta apps?
  • Should the improvement serve the feature's users first or Facebook's engagement and revenue goals, and how should I weigh them when they conflict?
  • May the improvement add a new surface built on the feature, or should it change only the existing feature?

Part 1 — Choose a feature and explain why it works

State which feature you picked, who uses it and for what, and why it succeeds both for those users and for Facebook.

What This Part Should Cover Guidance

  • A specific feature, defined precisely enough to analyze
  • The users it serves and the need it meets for them
  • Why it works, linked to concrete design choices and to Facebook's goals

Part 2 — Improve the feature

Set a goal for the improvement, choose which users of the feature to focus on, find their biggest problem, propose and prioritize solutions, and explain how you would measure success.

What This Part Should Cover Guidance

  • A goal for the improvement and a user segment chosen with reasoning
  • Pain points ranked by severity for that segment
  • Several solutions compared on explicit criteria, with one prioritized
  • Success metrics with guardrails

What a Strong Answer Covers Guidance

  • An improvement that builds on the strengths named in Part 1 rather than jumping to an unrelated problem
  • The tension between user value and Facebook's engagement or revenue goals, made explicit
  • Risks such as privacy, integrity or misuse, with mitigations
  • A clear structure and a firm recommendation

Follow-up Questions Guidance

  • How would you test your improvement before a full rollout, and what result would make you stop?
  • If your change made the feature more useful but reduced time spent on Facebook, how would you make the case for shipping it?
  • How could bad actors misuse your improvement, and how would you prevent it?