We scan new podcasts and send you the top 5 insights daily.
In legacy companies, evangelizing product jargon like 'discovery' or 'iteration' is alienating and can seem arrogant. Product managers gain more traction by using stakeholders' own language, focusing on solving their problems, and reframing product processes as simple, tangible requests for feedback, not philosophical debates.
Many PMs crave validation for their craft, leading them to explain processes like discovery or agile to executives. This is ineffective because executives don't care about the 'how'. Communication should focus on financial results, not methods.
The skill of storytelling isn't just for marketing or user narratives. Its most powerful application in product management is internal: convincing diverse stakeholders and team members to rally behind solving a specific problem. It's a tool for alignment and motivation before a single feature is built.
Instead of preaching an abstract 'product model,' find a single, tangible project to demonstrate immediate value. This 'show, don't tell' approach builds trust and makes subsequent, larger changes easier by proving the method's worth on a small scale.
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.
Product managers can reframe stakeholder management by applying their user discovery skills internally. Get curious about stakeholders' goals, pains, and worldviews to build trust and influence, just as you would with customers.
To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.
Instead of 'selling' product management methodologies, influence other leaders by understanding their incentives and goals. Frame product initiatives in terms of how they help other departments succeed. This requires product leaders to be deeply commercial, not just feature-focused.
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.
Go-to-market executives are wired to think in currency. To be heard and get buy-in, product managers must translate concepts like tech debt or user joy into revenue, cost savings, or other financial metrics.
Product managers often fail to get ideas funded because they speak about user needs and features, while executives focus on business growth and strategic bets. To succeed, PMs must translate user value into financial impact and business outcomes, effectively speaking the language of leadership.