Stakeholder Management

Marty Cagan argues that stakeholder management is a frequent pain point for product managers, but it can be substantially improved. He defines stakeholders narrowly as people who hold veto power over launching work, typically executives, finance, legal, compliance, and business development. The product manager's job is to understand each stakeholder's constraints and convince them, sincerely, that solutions will work for their concerns too. Success depends on being a competent PM, sharing learning openly, meeting stakeholders one-on-one, previewing solutions during discovery rather than after building, and moving debates from opinions to evidence. The approach matters because late surprises erode organizational confidence in the product team.

01Key takeaways

• Identify who truly holds veto power over your launches and prioritize understanding their constraints.
• Learn the customer, data, technology, and business deeply so stakeholders trust your judgment.
• Preview solutions with key stakeholders during discovery, before anything goes onto the backlog.
• When opinions clash, run a quick test and bring evidence to move the debate from opinion to data.
• Meet stakeholders one-on-one on a regular cadence rather than in large group meetings.
• Be patient in explaining the product role to stakeholders who may not understand or may feel threatened by it.

02Key sections

Who counts as a stakeholder

Cagan separates casual opinion-givers from true stakeholders, defined by the power to veto or block a launch. He lists common stakeholder roles across large companies, with fewer in startups.

The PM's responsibilities

The product manager must understand stakeholder constraints and build trust that solutions will serve the business as well as customers. Without that trust, stakeholders escalate or try to take control.

Earning trust through competence

Stakeholders respect PMs who deeply understand customers, analytics, technology, and the business. Sharing what you learn openly is the main way to demonstrate that expertise.

Preview solutions during discovery

Showing stakeholders a finished solution is a common and costly mistake. Previewing ideas during continuous discovery ensures they are viable as well as valuable and feasible.

Individual meetings over group meetings

Cagan recommends a few hours a week of short one-on-one sessions, such as recurring lunches, rather than group meetings that tend to devolve into design by committee.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

04Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.