Stakeholder Management
A deliberate practice for understanding, involving, and communicating with people who influence a product or are affected by its outcomes.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/stakeholder-management/
01What it means
Stakeholder management is the ongoing work of identifying relevant people and groups, understanding their interests and influence, and designing appropriate ways to involve them. It is not a campaign to keep everyone pleased. Good practice makes disagreement visible, brings useful expertise into decisions, and gives affected groups a fair opportunity to shape outcomes.[1][2]
- 01Identify
- Influence, knowledge, authority, or experienced effects
- 02Understand
- Interests, concerns, preferred involvement
- 03Involve
- Update, consult, workshop, co-decide, approve
- 04Record
- Decision, tension, rationale, follow-up
- 05Review
- Relationships and needs as context changes
Interests, influence, decision rights, and communication needs change over time, so engagement plans and shared records must evolve.
02Why it matters
Products depend on coordinated choices across customers, executives, engineering, design, sales, support, legal, and operations. Without deliberate engagement, teams discover constraints late, confuse silence with agreement, or let the loudest voice dominate. Thoughtful stakeholder management improves decision quality while protecting the product team’s ability to lead.
03When to use it
Use it continuously, with extra attention when strategy changes, risk is high, teams are interdependent, or a decision creates material consequences for customers or internal groups. Reassess the stakeholder map as influence, knowledge, and impact change.
04How it works
- Identify people who influence the work, hold relevant knowledge, or experience its effects.
- Map their interests, concerns, decision authority, influence, and preferred level of involvement.
- Choose engagement methods proportionate to impact, from updates to workshops or formal approval.
- Make decisions, unresolved tensions, and follow-up actions visible in a shared record.
- Review relationships and communication needs as the product context changes.
05A practical example
A team changing merchant payout timing interviews support and finance, consults compliance before selecting an option, and gives executives a short decision brief. Merchants test the proposed explanation. The team records who decided, which risks remain, and when results will be reviewed.
06Where it breaks
Stakeholder maps simplify relationships and can reinforce existing power if impact is treated as less important than authority. Excessive consultation slows work and can imply consensus is required. Engagement must have a clear purpose, honest boundaries, and routes for less powerful groups to be heard.
Common mistakes
- Treating stakeholders only as people who can block delivery.
- Using status meetings instead of purposeful involvement.
- Promising influence when a decision has already been made.
- Failing to revisit the map after circumstances change.
07Sources
- Stakeholder EngagementAssociation for Project Management · Professional institution guidanceStakeholder Engagement
- What Is Stakeholder Management?Association for Project Management · Professional body of knowledgeWhat Is Stakeholder Management?