Transformation Politics

Marty Cagan argues that successful product-model transformations deliberately confront political realities rather than avoiding them, since changing how an organization decides and builds is fundamentally a people problem. He covers how product leaders must build trust with executives, how product manager titles and competence protect credibility, and why pilot teams beat gradual change. He also addresses why pilot teams should trust stakeholders on problem identification, why strategy changes should wait until trust is won, and why steady, real business results must be communicated regularly to sustain support over the multi-year timeline.

01Key takeaways

• Build executive relationships through humility and genuine curiosity about each stakeholder's concerns and constraints before pushing change.
• Invest in onboarding that teaches product managers marketing, finance, legal, security and other business topics to protect credibility.
• Launch a small, hand-picked pilot team tied to a meaningful business outcome rather than attempting gradual, widespread change.
• Trust stakeholders' problem identification in pilots and focus discovery time on finding solutions; coach any team stuck on one problem beyond two weeks.
• Delay changing how problems are prioritized until the product teams have won stakeholder trust through consistent delivery.
• Communicate real business results at least monthly, sharing failures as well as successes, rather than reporting activities.

02Key sections

Product leaders and executive relationships

The product leader must build relationships with key executives by showing humility and learning their concerns. Because the leader is judged by the weakest product manager, exposure to the wider organization should be gated by demonstrated business sophistication.

Protecting the product manager role

Stakeholders lose confidence quickly when product people appear unaware of how the business works, so structured onboarding in business viability topics is essential. Titles containing 'product' should be protected and reserved for people who meet a minimum competence bar.

Pilot teams over gradual change

Gradual change tends to stall because the organization runs out of patience, so a small, carefully chosen pilot team should demonstrate what good looks like. Pilots should be kept small, solve a meaningful business outcome, and be well trained and coached.

Discovery and building trust with stakeholders

Stakeholders usually already understand the core problems, so pilot teams should spend limited time on problem discovery and focus on finding solutions. Long stretches without visible progress erode confidence, so teams stuck on one problem for more than two weeks need coaching.

Strategy shifts and sustaining momentum

Changing how problems are chosen feels like a loss of control to stakeholders, so it should follow after trust is established. Teams must also keep the existing operational work running, and regularly communicate real business results rather than activities.

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.