We scan new podcasts and send you the top 5 insights daily.
To manage conflicting opinions from numerous stakeholders, the Winnebago team used a clear set of customer use cases as their North Star. Any proposed change, whether for cost or manufacturing ease, was evaluated against its impact on fulfilling a core customer job-to-be-done.
Don't make high-stakes decisions in a silo. Involve stakeholders throughout the discovery and analysis process. Having finance review your P&L or sales weigh in on customer pain builds shared context and turns your recommendation from 'your bet' into 'our bet.'
When a stakeholder proposes a specific feature (a "form factor"), don't debate it directly. Instead, "ladder up" the conversation by asking a series of "why" questions to uncover the user behavior, desired outcome, and ultimately, the root problem being solved.
Product managers frequently receive solutions, not problems, from stakeholders. Instead of saying no, the effective approach is to reframe the solution as a set of assumptions and build a discovery backlog to systematically test them. This builds alignment and leads to better outcomes.
IBM uses a visual artifact called the "Golden Thread"—a living document showing product vision, value, and a feedback loop. This low-cost tool aligns diverse stakeholders, from the boardroom to developers, around outcomes instead of features, thereby de-risking innovation.
Stakeholders respond to the language of business impact. Instead of pitching an initiative to "improve the onboarding experience," frame it as a way to "grow our business customers in this sector." This small change in communication connects your work directly to the goals stakeholders care about.
The debate between being product-led vs. sales-led is a false dichotomy that creates friction. Instead, frame all functions as fundamentally 'customer-driven.' This reframing encourages product teams to view sales requests not as distractions, but as valuable, direct insights into customer needs.
To avoid appearing self-serving or political, anchor every decision and debate to a specific customer problem. This shifts the focus from defending your idea to collectively solving a shared challenge. It frames your advocacy as being on behalf of the user, not your ego or career.
When narrowing down ideas, replace generic dot-voting with prompts tied to strategic goals. Ask participants to vote based on criteria like "potential to generate X million in revenue" or "ability to increase customer retention." This ensures the winning ideas directly address core business objectives.
To avoid bias and misalignment, collaboratively create a weighted decision-making rubric with stakeholders *before* evaluating options. This ensures everyone agrees on the evaluation criteria, making the final decision easier to accept and implement.
When building a product with multiple funding customers and stakeholders, use a structured workshop process. Present a proposal, clarify questions, gather reactions, amend, and then vote. This formal process forces alignment and achieves consensus, even with competing interests.