Judging When Stakeholder Consensus Helps or Hurts a Product Decision

In a product manager interview you are asked whether it is always a good thing when every stakeholder reaches consensus. Take a position, explain when agreement among stakeholders strengthens a product decision and when it weakens it, and ground your answer in a concrete situation, ideally one from your own work. ```hint Weigh what agreement costs Think about what a decision actually needs from each stakeholder, and what it costs when everyone has to say yes before anything moves. ``` ### Clarifying Questions - Does "stakeholders" mean internal partners (engineering, design, operations, finance, legal, marketing), external parties such as drivers, riders or business partners, or both? - Should I answer as the person who owns the final decision, or as one voice among several stakeholders? - Would you like a general point of view, a story from my own experience, or both? ### What a Strong Answer Covers - A clear position stated early, rather than "it depends" with no conclusion. - The difference between full consensus and alignment or commitment, and why it matters for product decisions. - Specific conditions under which seeking agreement is worth its cost, and conditions under which it slows or dilutes a decision. - Ways to decide without unanimity: a named decision owner, time limits, recorded dissent and a clear escalation path. - A concrete example in STAR form that shows the candidate's own judgment and the outcome. ### Follow-up Questions - Tell me about a time you went ahead with a decision that a senior stakeholder disagreed with. How did you handle it, and what happened? - Everyone in the room agrees with your proposal within minutes. When would that make you suspicious, and what would you do? - How do you decide whether a disagreement between operations and engineering is yours to settle or should be escalated?