Pledge To Stakeholders

Marty Cagan argues that as companies shift from stakeholder-driven feature teams to empowered product teams, the relationship between product teams and stakeholders must change on both sides. Creating a solution customers love is often manageable, but balancing that with marketing, funding, operations, compliance, and other business needs is harder. Because committees rarely innovate, product managers should engage stakeholders directly, learn their constraints, and build trust. The essay frames this as a pledge: prototype solutions for stakeholders before building, correct viability problems quickly, and stay transparent. This matters because it describes how to get business buy-in without sacrificing the innovation that empowered teams are meant to deliver.

01Key takeaways

• Engage each relevant stakeholder directly and learn their constraints before proposing solutions.
• Show stakeholders a prototype of any change affecting their area before the team builds it.
• Expect iteration; a prototype feedback loop often reveals solutions that satisfy multiple parties.
• Pursue business outcomes rather than shipping features, and do not ship what fails critical business needs.
• When a non-viable change ships, fix it fast and investigate how it happened to prevent recurrence.
• Stay transparent by letting stakeholders join user testing and see prototypes and live data.

02Key sections

Why stakeholders still matter

Product teams must solve for customers while also meeting the competing needs of marketing, sales, finance, legal, and operations. Bringing everyone into every decision is too slow and tends to produce uninnovative outcomes.

Product manager's role as partner

Each product manager must understand the business constraints deeply enough to earn stakeholder trust, since few PMs know every relevant dimension in depth. Stakeholders should not be expected to trust a PM without that foundation.

The prototype-first commitment

Before building anything that affects a stakeholder, the PM shows them a prototype for quick feedback. Iterating on prototypes often surfaces solutions that satisfy all parties, including ones no one initially saw as possible.

Outcomes, accountability and transparency

The team commits to pursuing business outcomes rather than shipping features, to fixing non-viable releases quickly and learning from them, and to openly sharing prototypes, testing, and data with stakeholders.

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.