How do you build organizational buy-in for a product strategy that leadership is skeptical of?
Model answer
Model answerSkepticism from leadership usually means either the strategy isn't clear enough or the evidence isn't compelling enough. I'd start by truly understanding the objection — is it about the destination, the path, or the team's ability to execute? Then I'd build a structured case: here's the problem, here's the evidence, here's what we'd learn in 90 days, here's what we'd need to invest. I'd ask for a small experiment, not full commitment. Proof of concept beats persuasion.
Framework · Stakeholder Alignment
- SSurface the real objection
What exactly is leadership skeptical of? Destination, path, or execution? - EEvidence-first framing
Customer data and market signals speak louder than internal conviction - TTime-boxed experiment
Ask for 90 days and a small bet — not a multi-year commitment - AAlign on what success looks like
Get leadership to define what would change their mind — then go prove it
Related questions
- How would you decide whether to enter the European market?
- How would you build the case for a multi-year product investment that won't show ROI for 18 months?
- How do you set product strategy when the CEO keeps changing their mind?
- How would you approach building a product in a regulated industry (fintech, health, etc.)?
- How do you create a product culture in a team that's historically been execution-focused?