Strategy interview mistakes that make answers feel hand-wavy
Build credibility in strategy interviews by grounding every recommendation in clear assumptions, trade-offs, and practical validation steps. Avoid vague generalities: specify user segments, quantify impact, and connect choices to measurable outcomes. Demonstrate ownership of reasoning—even under uncertainty—by making and defending explicit decisions.
PMMockr.comSpotting the hand-wavy answer
A hand-wavy strategy answer sidesteps concrete choices, glosses over trade-offs, or stays at the 10,000-foot view without actionable detail. For example, responding to "Should we expand into a new market segment?" with "We should consider user needs and business goals" avoids the heart of the decision.
These answers frustrate interviewers because they signal a reluctance to commit or a lack of structured thinking. Instead, strong strategy responses identify specific user groups, state assumptions, and spell out what would trigger a different recommendation. This builds trust in your judgment, even when information is limited.
The importance of explicit assumptions
In strategy interviews, incomplete data is the norm. Avoiding clear assumptions often leads to answers that meander or hedge excessively. Instead, make your key assumptions visible. For instance, if you're projecting revenue from a new feature, say, "I'm assuming 10% of our active users would adopt this feature within the first quarter."
This approach demonstrates structured thinking and invites productive challenge. If your estimate is off, the interviewer can correct the assumption, not your entire framework.
Worked example: Prioritizing a self-serve onboarding flow
Suppose you're asked: "Should our B2B SaaS product invest in a self-serve onboarding flow or double down on white-glove onboarding for enterprise clients?"
First, segment users: assume 70% of current signups are small businesses (SMBs) with under 50 employees, and 30% are large enterprises. SMBs have higher churn during onboarding—assume 30% drop off, compared to 10% for enterprises. Each SMB brings $2,000 ARR, each enterprise brings $60,000 ARR (all invented for this exercise).
If you invest in self-serve onboarding, you estimate a 10-point drop in SMB churn (to 20%), adding 70 new retained SMB customers per 1,000 signups, or $140,000 ARR. If you focus on white-glove enterprise onboarding, you estimate a 3-point drop in enterprise churn (to 7%), retaining 9 more enterprise customers per 1,000 signups, or $540,000 ARR.
However, self-serve onboarding is expected to cost $200,000 to build, while improved enterprise onboarding costs $120,000. The payback periods are 1.4 years for SMB self-serve, and about 0.22 years for enterprise white-glove. Given the faster payback and larger immediate dollar impact, you recommend focusing on enterprise onboarding. You note that this depends on the assumption that enterprise demand is not saturated and that additional retained customers are possible.
To validate this, you propose a small pilot: offer an enhanced onboarding concierge to 50 enterprise prospects and measure conversion and retention. If you see less uplift than projected, or if the SMB churn reduction is higher in a lightweight self-serve test, you would revisit your recommendation.
Why specificity matters—weak vs. strong reasoning
A weak answer might state, "Both segments are important, and we should optimize for growth." This skips over how to choose, what growth means here, and what trade-offs are involved.
A stronger response, as in the worked example, quantifies segment sizes, revenue contributions, and expected outcomes. It specifies a decision (enterprise onboarding) and explains what evidence would cause a change. This doesn't require perfect data—just the discipline to anchor reasoning in explicit numbers and testable hypotheses.
Making and defending a choice
Strategy is about making bets under uncertainty. Avoid the temptation to hedge endlessly or propose doing everything. Make a recommendation, state your logic, and own the decision.
If you choose to prioritize enterprise onboarding, say so clearly: "Given the larger revenue impact and faster payback, I recommend investing in enterprise onboarding, assuming we can still grow this segment." Invite correction to your assumptions, not to your willingness to decide.
Competing options and trade-offs
Consider the alternative: investing in SMB self-serve onboarding. The trade-off here is a longer payback period and lower immediate revenue impact, but possibly more scalable growth and reduced support costs later. Acknowledge this, but explain why your chosen option wins under current assumptions.
This demonstrates you have considered the full landscape, but are not paralyzed by it. If new evidence emerges—like unexpectedly high demand from SMBs—you’re ready to shift.
Practical validation and course correction
Every strategy recommendation should include a way to test its underlying assumptions. Propose a small, time-bound experiment: for example, run a two-month pilot of enhanced enterprise onboarding, or A/B test a lightweight self-serve flow for SMBs.
Set clear success criteria: e.g., "If we see less than a 2-point improvement in enterprise retention, we will revisit the SMB option." This makes your answer actionable and credible, not theoretical.
Practice exercise: timed strategy scenario
Set a timer for 15 minutes. Choose a hypothetical scenario: "Should our mobile banking app prioritize developing a budgeting tool for Gen Z or a new fraud detection feature for high-net-worth users?"
Outline:
- Assume user base splits, revenue, and current churn rates. - Quantify impact for each option. - Make an explicit recommendation and defend it with numbers and assumptions. - Identify one key risk or assumption and propose a validation step.
Afterward, check your work against the self-review checklist.
Self-review checklist and practice cadence
Use this checklist after each practice round:
- Did I state clear, explicit assumptions for user segments and impact? - Did I quantify outcomes and connect them to business goals? - Did I make a specific recommendation with a clear rationale? - Did I acknowledge a competing option and its trade-off? - Did I propose a concrete validation step?
Aim to practice 2–3 scenarios per week, reviewing your answers critically and iterating. For additional structure, consider submitting one answer per week for external feedback, such as through PMMockr.
FAQ
What makes a strategy answer feel 'hand-wavy'?
A hand-wavy answer avoids specifics, fails to quantify impact, skips over trade-offs, or does not commit to a clear recommendation. It often relies on generalities or buzzwords without connecting reasoning to measurable outcomes.
How should I handle uncertainty or missing data in my answer?
State your assumptions explicitly and explain how they drive your recommendation. Propose a way to validate the most critical assumption through a pilot or experiment, and say what evidence would cause you to reconsider.
Is it better to hedge or to make a firm recommendation in strategy interviews?
It's better to make a firm recommendation, supported by clear logic and assumptions. Acknowledge uncertainty, but don't avoid deciding. Invite correction to your assumptions if new data emerges, showing openness to course correction.