Product Metrics and Prioritization Prompt: Meta Pay
Assume you are the PM for Meta Pay, the consumer payments system used across Meta apps such as Messenger, Instagram, and Facebook. Meta Pay powers peer-to-peer payments and on-platform checkouts.
Answer:
-
What North Star and supporting metrics define Meta Pay's success?
-
Next year you can ship only one of two features: a peer split-bill capability or a donations flow. Which do you prioritize and why?
-
The North Star metric is flat, yet cost per transaction has fallen. How would you investigate and debug this discrepancy?
Constraints & Assumptions
-
Clarify whether Meta Pay's strategic goal is P2P network growth, commerce checkout, creator monetization, or platform trust.
-
Define metrics precisely before prioritizing features.
-
Include risk, fraud, compliance, transaction success, and unit economics.
-
Do not optimize cost per transaction in isolation if adoption or payment value is flat.
Clarifying Questions to Ask
-
Which Meta Pay surface is most important: P2P, marketplace checkout, Instagram commerce, donations, or creator payments?
-
Is direct revenue a goal, or is Meta Pay mainly an enabler of commerce and engagement?
-
Which markets and payment rails are in scope?
-
Are split-bill and donations both technically and legally feasible next year?
-
What is the current bottleneck: activation, trust, frequency, transaction success, or cost?
Part 1 - Metrics
Define North Star and supporting metrics for Meta Pay.
What This Part Should Cover
-
North Star such as Monthly Active Payers or successful payment volume, with a clear definition.
-
Activation, instrument add, first payment, transaction frequency, retention, success rate, and TPV.
-
Trust and risk metrics such as fraud loss, chargebacks, disputes, KYC pass, and account takeover.
-
Unit economics such as cost per transaction and contribution margin.
Part 2 - Feature Prioritization
Choose between peer split-bill and donations flow, and justify the decision.
What This Part Should Cover
-
Target users, jobs to be done, reach, impact, confidence, effort, risks, and strategic fit.
-
Network effects and frequency for split-bill.
-
Social good, creator/nonprofit fit, and trust implications for donations.
-
Recommendation tied to the chosen North Star and current product bottleneck.
Part 3 - Debug Flat North Star with Lower Cost
Investigate why the North Star is flat while cost per transaction fell.
What This Part Should Cover
-
Metric definition and instrumentation checks.
-
Volume, active payers, transaction mix, geography, payment method, and merchant/P2P split.
-
Cost component decomposition.
-
Whether lower costs came from mix shift, vendor savings, routing changes, or fewer high-cost transactions.
-
Whether user value, activation, or retention is still blocked.
What a Strong Answer Covers
A strong answer builds a metric tree, makes the feature decision based on user value and strategic goals, and debugs the cost/North-Star discrepancy by decomposing adoption, frequency, transaction mix, and unit economics.
Follow-up Questions
-
When would donations beat split-bill?
-
How would you measure trust in payments?
-
What if split-bill increases transactions but also fraud?
-
How would you improve activation?
-
How would you design a holdout or experiment for the chosen feature?