How to prioritize growth bets in a product strategy case
Prioritize growth bets using a common outcome, explicit assumptions and delivery constraints. Practice a worked comparison and defend what you would test first.
PMMockr.comQuick answer
Prioritize growth bets using a common outcome, explicit assumptions and delivery constraints. Practice a worked comparison and defend what you would test first.
Compare growth bets on the same outcome and horizon
New signups, activated users and retained customers are different quantities. Convert each proposal into the outcome relevant to the goal before ranking it. Use a common cohort and time horizon, then account for uncertainty and cost. A referral program that adds signups cannot be compared directly with onboarding that adds activated users.
Separate reach, conversion and retained value
Write a short impact chain for each bet: eligible reach × exposure or participation × conversion to the desired behavior. Add retention if the goal is durable growth. Explain where the assumptions come from and how you will test them. Avoid counting the same users twice when two bets affect overlapping cohorts.
Choose a first experiment rather than a complete growth roadmap
Name the most uncertain assumption that could reverse your choice. If your onboarding opportunity depends on users understanding the first task, prototype that change before a large rollout. If referral intent is uncertain, test participation and qualified activation before projecting a viral loop. Explain what you will stop doing to free capacity.
Avoid chasing every growth idea
A common mistake in product strategy interviews is to list every possible growth lever—new features, viral loops, pricing tweaks—without a clear method for picking the best one. This approach overwhelms both you and the interviewer, making it hard to see what actually matters. Prioritization is about focus: choosing where to invest limited resources for maximum impact, not covering every possibility.
Start with explicit assumptions and constraints
Before ranking options, clarify key assumptions and constraints. For example, are you optimizing for revenue, user acquisition, or engagement? What is your time horizon—one quarter or two years? Are there technical or regulatory constraints?
Stating these up front frames the rest of your reasoning. If you assume the product has strong retention but slow acquisition, your growth bets should focus on top-of-funnel. If resources are tight, bets requiring heavy engineering may be deprioritized. This context keeps your choices realistic and testable.
Segment users to clarify impact
Growth opportunities rarely affect all users equally. By segmenting users—such as new vs. existing, power vs. casual—you can estimate which bets move key numbers for which groups. For example, a referral program might mostly bring in new users, while a premium upsell helps monetize existing ones.
This segmentation clarifies which metrics a bet is likely to move, and helps avoid double counting impact. It also exposes blind spots, such as neglecting churn among high-value users if you only look at acquisition.
Estimate impact, effort, and risk for each bet
Prioritization means more than listing bets: you must compare them on impact, effort, and risk. For each bet, make rough but explicit estimates. For example, assume a new onboarding flow could increase activation from 40% to 50% for new users (impact), takes two engineers for a month (effort), but has modest risk of backfiring.
Contrast this with a new market expansion: potential for 50% more users, but large engineering and marketing costs, and higher uncertainty. By stating estimates and their rationale, you show structured thinking and openness to correction.
Worked example: Prioritizing growth bets for a language learning app
Illustrative teaching example. All people, figures, results and thresholds below are hypothetical, not PMMockr customer data or a story to claim as your own.
Illustrative teaching inputs for one monthly cohort, not observed product results. A language-learning app has one million existing active users and 300,000 new signups. Consider referrals, an additional language and better onboarding.
Referral assumption: 5% of existing users invite one friend, 40% of friends sign up and 40% of those activate. That yields 8,000 activated users (1,000,000 × 0.05 × 0.4 × 0.4). New-language assumption: an eligible audience of 200,000, 10% signup and 40% activation yields 8,000 activated users. Onboarding assumption: raising activation from 40% to 50% for 300,000 signups yields 30,000 additional activated users. All three now use the same outcome.
These inputs are uncertain. Compare development cost, reach and retention before committing. Onboarding is the first test under these assumptions; a smaller achievable lift, heavier engineering cost or weaker retained value could change the decision. Run a properly planned experiment rather than imposing a universal two-week duration or treating an arbitrary percentage threshold as established evidence.
Comparing alternatives: When a competing bet looks attractive
Suppose an interviewer suggests the referral program (A) might have network effects and long-term compounding value not captured in your one-quarter estimates. You acknowledge that if referrals increase not just new users but also engagement and retention, their impact could multiply over time.
However, with the current assumptions—limited marketing bandwidth, risk of low referral rates, and the need for short-term wins—you maintain onboarding is the better first bet. You propose instrumenting the referral program in parallel to gather data, but not allocating full resources until initial results from onboarding are in.
Spotting weak reasoning: Avoid vague impact estimates
A weak answer might claim, "Referral programs are always high-impact; look at how other apps have grown." This is a tempting shortcut, but ignores context—user motivation, product fit, and resource constraints differ widely.
A stronger approach is to ground estimates in plausible, transparent calculations. For example, estimate referral rates based on similar apps, but adjust for your app's unique user base and incentives. Show your math and be explicit about uncertainty, inviting correction and further discussion.
Check your recommendation with a practical experiment
Any prioritization should include a concrete way to check your assumptions. In the example, proposing an A/B test for onboarding improvements gives you a way to validate or refute your forecasted impact. Specify the metric (activation rate), the expected change (10 percentage points), and the time frame (two weeks).
If results fall short, commit to re-evaluating the next-best bet. This approach shows not just decisiveness but adaptability—crucial for product management.
Practice exercise: Prioritize three hypothetical growth bets
Set a timer for 15 minutes. Imagine a music streaming app with flat user growth. You have three options: launch a student discount, improve playlist recommendations, or partner with a hardware maker to preinstall the app. Assume 2 million active users, 20% are students, and the team has 3 engineers for a quarter. For each bet, estimate impact, effort, and risk, then choose one to prioritize. Specify what evidence would shift your recommendation.
After you finish, review using the checklist below. Practice this drill twice per week, using different app scenarios, to build speed and rigor.
Self-review checklist
- Did you state clear assumptions and constraints?
- Did you segment users to clarify which groups each bet would affect?
- Did you estimate impact, effort, and risk for each option, with explicit numbers?
- Did you compare alternatives head-to-head and explain your trade-offs?
- Did you propose a concrete experiment or validation step?
- Did you specify what new evidence would change your recommendation?
- Did you avoid vague generalizations or ungrounded claims?
FAQ
How do I compare growth ideas in a PM case?
Define the goal and common time horizon, translate each idea into the same outcome, state assumptions and compare costs and risks. Pick a first test that can invalidate the riskiest assumption.
How do I handle uncertainty in my estimates during an interview?
State your assumptions clearly, use rough numbers where needed, and explain the sources of uncertainty. Propose experiments or data sources to validate your estimates, and specify what results would lead you to reconsider your recommendation.
What if the interviewer pushes back on my chosen growth bet?
Acknowledge their perspective, revisit your assumptions, and compare the alternatives using explicit criteria. If their information changes your view, explain how you would update your recommendation and what new data you would seek.
How many growth bets should I discuss before making a recommendation?
Discuss two to four well-considered options, but focus on depth rather than breadth. Prioritize one with a clear rationale, and be ready to discuss trade-offs and how you would validate your choice.