Stakeholder Management for Product Teams: Show Your Work, Don't Sell Your Conclusions

Teresa Torres argues that product teams are sliding back into feature-factory habits as AI tools make shipping faster, and that stakeholders often arrive with solutions rather than problems. Her core advice is to stop presenting conclusions, which invites opinion battles that a product team usually loses, and instead show the discovery work behind them. She recommends walking stakeholders through an opportunity solution tree from outcome to opportunities, prioritization, solutions, and assumption tests, while inviting their input at each step. She also covers tailoring detail to each audience and avoiding trust-destroying habits such as telling instead of showing and dismissing ideas outright. The piece matters because it reframes stakeholder management as co-creation rather than persuasion.

01Key takeaways

• Stop leading with your roadmap; lead with the shared outcome and check whether it has changed.
• Bring new information from interviews and assumption tests, since that is the only reliable lever against senior opinions.
• Ask stakeholders what opportunities you may have missed, and capture their suggestions to test later with customers.
• Walk the opportunity solution tree with stakeholders and invite them to say whether they would have made a different decision at each step.
• Share short, frequent updates instead of batching everything into one comprehensive presentation.
• Map a stakeholder's idea onto your assumptions together rather than telling them why it is wrong.

02Key sections

Identify the influential stakeholders

Stakeholders are anyone who influences or is affected by product decisions, and some hold veto power while others only offer input. Teams should focus energy on the relationships that matter most, and bring those stakeholders along even though they sit outside the product trio.

Avoid the conclusions trap

Presenting finished roadmaps invites stakeholders to compare their preferences with the team's, producing HiPPO-driven opinion battles. Under the current AI hype, the only real lever is bringing new information gathered through discovery.

Show your work with the opportunity solution tree

The tree becomes a walkthrough tool: start with the outcome, share the opportunity space and ask what was missed, explain prioritization, deepen the target opportunity with interview snapshots, invite solution ideas, and share assumption tests. Repeat this continuously rather than in one big reveal.

Tailor communication to each audience

Busy stakeholders need filtered detail, but the same outcome, opportunity, solution, and evidence structure still applies at every level. Even a brief elevator summary can walk the tree in a few sentences.

Anti-patterns that erode trust

Teams should avoid telling instead of showing, which the curse of knowledge makes tempting; shooting down ideas rather than mapping their assumptions together; saving updates for a big reveal; and fighting ideological battles about how decisions should be made.

03From the post

“Everyone I talk to is rushing to add AI features to their roadmap. And every stakeholder has an opinion about what they should be building. The challenge is we are forgetting our discovery fundamentals. We are reverting back to a feature factory. Delivery is getting faster and easier, so it”

04Frameworks mentioned

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