Meta Pay: Metrics & Prioritization
MetaProduct Manager · OnsiteLast updated
Practice Meta Pay PM metrics and prioritization with North Star definition, metric tree, split-bill versus donations trade-offs, and debugging flat adoption despite lower cost per transaction. The solution covers active payers, transaction success, trust, risk, unit economics, feature strategy, and decomposition analysis.
Question
a. What are the North Star and supporting metrics that define Meta Pay’s success?
b. Next year you can ship only one of two features: (
- a peer split-bill (AA) capability or (
- a donations flow. Which do you prioritize and why?
c. The North Star metric is flat, yet cost per transaction has fallen. How would you investigate and debug this discrepancy?
Hints
Clarify metric definitions (e.g., active payers vs. transaction volume) and link them to business outcomes before deciding trade-offs.
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.