# Stakeholder Management

A deliberate practice for understanding, involving, and communicating with people who influence a product or are affected by its outcomes.

- Type: practice
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/stakeholder-management/>)

## What 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.

## Why 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.

## When 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.

## How it works

1. Identify people who influence the work, hold relevant knowledge, or experience its effects.
2. Map their interests, concerns, decision authority, influence, and preferred level of involvement.
3. Choose engagement methods proportionate to impact, from updates to workshops or formal approval.
4. Make decisions, unresolved tensions, and follow-up actions visible in a shared record.
5. Review relationships and communication needs as the product context changes.

## A 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.

## Where 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.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/stakeholder-management/#visualization-stakeholder-management>)

## Sources

1. [Stakeholder Engagement](<https://apm.org.uk/resources/find-a-resource/stakeholder-engagement>) — Association for Project Management · Professional institution guidance
2. [What Is Stakeholder Management?](<https://apm.org.uk/body-of-knowledge/delivery/integrative-management/stakeholder-management>) — Association for Project Management · Professional body of knowledge

## Related topics

- [Decision Rights](<https://wiki.soroush.uk/topic/decision-rights/>)
- [RACI](<https://wiki.soroush.uk/topic/raci/>)
- [Roadmap Communication](<https://wiki.soroush.uk/topic/roadmap-communication/>)
