Product Sense: Posting Updates for Contacts to View in WhatsApp

Quick Overview

A product sense question asking a PM to design WhatsApp's Status feature, where people post updates for their contacts to view. It tests choosing users and goals for a private messenger, audience and privacy decisions, viewing and reply flows, and metrics that protect core chat use.

Product Sense: Posting Updates for Contacts to View in WhatsApp

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

Design the Status feature for WhatsApp: a place where people post updates that their contacts can view, instead of sending a message to each person or group. Explain whom it serves, what problem it solves for them, what the first version includes and how you would measure success. ```hint Start from how people share today Think about how someone shares a photo from their day with family and friends using only chats and groups. What does that cost the sender and the people receiving it, and what has to stay true for a private messenger built around phone contacts? ``` ### Clarifying Questions - Are we designing Status from scratch for a WhatsApp that has only chats, groups and calls, or improving the Status that exists today? - What is the main goal: more everyday sharing between people who know each other, keeping pace with stories on other social apps, or giving businesses a way to reach customers? - Which users and markets matter most, for example people on low-cost Android phones with expensive mobile data? - Must updates have the same end-to-end encryption as chats, and who should be allowed to see them? ### What a Strong Answer Covers - A goal that fits a private messenger, and a reasoned choice of user segment. - Pain points of sharing through chats and groups today, for both the people posting and the people viewing. - A prioritized first version covering posting, audience control, viewing and replies, with trade-offs such as whether updates expire and whether posters see who viewed them. - Success metrics for posting, viewing and conversations, with guardrails that protect core chat use, privacy and data cost. - Risks: misinformation, privacy surprises, harassment, and the limits end-to-end encryption puts on moderation. ### Follow-up Questions - A user's contacts include their boss, their landlord and their customers. How do you keep posting comfortable without making audience settings a chore? - How would you tell whether Status adds engagement rather than moving time out of chats, given that a poster's contacts are connected to each other? - Businesses want to post promotions to Status. Would you allow it, and with what limits?

Overview: A product sense question asking a PM to design WhatsApp's Status feature, where people post updates for their contacts to view. It tests choosing users and goals for a private messenger, audience and privacy decisions, viewing and reply flows, and metrics that protect core chat use.

Meta logo
Meta
Jun 10, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

Design the Status feature for WhatsApp: a place where people post updates that their contacts can view, instead of sending a message to each person or group.

Explain whom it serves, what problem it solves for them, what the first version includes and how you would measure success.

Clarifying Questions Guidance

  • Are we designing Status from scratch for a WhatsApp that has only chats, groups and calls, or improving the Status that exists today?
  • What is the main goal: more everyday sharing between people who know each other, keeping pace with stories on other social apps, or giving businesses a way to reach customers?
  • Which users and markets matter most, for example people on low-cost Android phones with expensive mobile data?
  • Must updates have the same end-to-end encryption as chats, and who should be allowed to see them?

What a Strong Answer Covers Guidance

  • A goal that fits a private messenger, and a reasoned choice of user segment.
  • Pain points of sharing through chats and groups today, for both the people posting and the people viewing.
  • A prioritized first version covering posting, audience control, viewing and replies, with trade-offs such as whether updates expire and whether posters see who viewed them.
  • Success metrics for posting, viewing and conversations, with guardrails that protect core chat use, privacy and data cost.
  • Risks: misinformation, privacy surprises, harassment, and the limits end-to-end encryption puts on moderation.

Follow-up Questions Guidance

  • A user's contacts include their boss, their landlord and their customers. How do you keep posting comfortable without making audience settings a chore?
  • How would you tell whether Status adds engagement rather than moving time out of chats, given that a poster's contacts are connected to each other?
  • Businesses want to post promotions to Status. Would you allow it, and with what limits?