Should Messenger Add In-Chat Payments? Making the Go or No-Go Call

Quick Overview

A product strategy question about whether Facebook Messenger should let money move inside a conversation. It tests how a PM sets the goal and scope, weighs user value against regulation, fraud, trust and competition, reaches a clear recommendation with conditions, and plans a pilot to validate it.

Should Messenger Add In-Chat Payments? Making the Go or No-Go Call

Company: Meta

Role: Product Manager

Category: Product Design & Strategy

Difficulty: medium

Interview Round: Other

You are a product manager at Meta, and the team has to decide whether Facebook Messenger should support payments, so that money can move inside a conversation instead of in a separate app. How would you make that decision? Walk through what you would need to know, how you would weigh launching against not launching, what you would recommend, and how you would check that the decision was right. ```hint Fix the goal before you score A payments launch carries real cost and risk, so it is easier to judge once you know what Messenger needs it to achieve. Pick that goal, then compare the options on the same criteria and find the riskiest assumption you would want to test first. ``` ### Clarifying Questions - Does "payments" mean people sending money to friends and family, people paying businesses they chat with, or both? - Which markets are in scope: one country first or a global launch, given that payment regulation, card use and the dominant wallets differ by country? - What should payments do for Messenger: deepen engagement and retention, earn fee revenue, or support business messaging and commerce? - Is Meta willing to hold and move funds itself, with the licensing and fraud liability that brings, or should a licensed partner handle the money? ### What a Strong Answer Covers - A clarified scope (person-to-person, paying businesses, markets) and a goal tied to what Messenger is for - The conversation moments where money comes up today, what people do instead, and how you would check that the demand is real - Explicit decision criteria such as user value, engagement, strategic fit, revenue, build cost, regulation, fraud and scams, privacy and trust, and competition, applied to more options than launch or do nothing - A clear recommendation with the conditions attached to it - A validation plan: a pilot design that handles network effects, success metrics, guardrails and stop criteria ### Follow-up Questions - In a pilot, payment users send more messages, but they were already the heaviest users. How would you separate cause from selection? - Would you build Meta's own payment flow or let people trigger existing payment apps from inside the chat? What do you gain and give up with each? - Scam reports rise sharply in the weeks after launch. What would you change, and what would make you pause the rollout?

Overview: A product strategy question about whether Facebook Messenger should let money move inside a conversation. It tests how a PM sets the goal and scope, weighs user value against regulation, fraud, trust and competition, reaches a clear recommendation with conditions, and plans a pilot to validate it.

Meta logo
Meta
Sep 22, 2024
mediumProduct ManagerOtherProduct Design & Strategy
0
0

You are a product manager at Meta, and the team has to decide whether Facebook Messenger should support payments, so that money can move inside a conversation instead of in a separate app. How would you make that decision?

Walk through what you would need to know, how you would weigh launching against not launching, what you would recommend, and how you would check that the decision was right.

Clarifying Questions Guidance

  • Does "payments" mean people sending money to friends and family, people paying businesses they chat with, or both?
  • Which markets are in scope: one country first or a global launch, given that payment regulation, card use and the dominant wallets differ by country?
  • What should payments do for Messenger: deepen engagement and retention, earn fee revenue, or support business messaging and commerce?
  • Is Meta willing to hold and move funds itself, with the licensing and fraud liability that brings, or should a licensed partner handle the money?

What a Strong Answer Covers Guidance

  • A clarified scope (person-to-person, paying businesses, markets) and a goal tied to what Messenger is for
  • The conversation moments where money comes up today, what people do instead, and how you would check that the demand is real
  • Explicit decision criteria such as user value, engagement, strategic fit, revenue, build cost, regulation, fraud and scams, privacy and trust, and competition, applied to more options than launch or do nothing
  • A clear recommendation with the conditions attached to it
  • A validation plan: a pilot design that handles network effects, success metrics, guardrails and stop criteria

Follow-up Questions Guidance

  • In a pilot, payment users send more messages, but they were already the heaviest users. How would you separate cause from selection?
  • Would you build Meta's own payment flow or let people trigger existing payment apps from inside the chat? What do you gain and give up with each?
  • Scam reports rise sharply in the weeks after launch. What would you change, and what would make you pause the rollout?