How do you align stakeholders when they disagree on the roadmap?
Model answer
Model answerDisagreement about roadmap is usually disagreement about strategy — people are optimizing for different goals. My first move is to surface that explicitly: 'It sounds like we're prioritizing different things. Can we align on what our #1 goal is this quarter before we discuss features?' Once there's strategic alignment, feature prioritization becomes easier. If stakeholders still disagree, I'd propose a time-boxed experiment: 'Let's test both approaches in 2 weeks and let data decide.'
Framework · Alignment Framework
- SSurface the real disagreement
Feature disagreements are usually strategy disagreements in disguise - AAlign on goals first
Get agreement on Q1 priority before discussing any features - DData as arbiter
Propose experiments to test competing hypotheses — removes ego from the room - EEscalate clearly
If truly stuck, escalate with a clear recommendation — don't present problems without solutions
Related questions
- How would you prioritize building for power users vs. new users?
- A major competitor just launched a feature you were building. What do you do?
- How would you evaluate the ROI of a product investment before building it?
- How would you evaluate a potential acquisition target from a product perspective?
- How do you decide when to kill a feature?