Amey-Thakur Stakeholder management
Decisions get reopened because someone with influence was not consulted and finds out late. Stakeholder management is unglamorous and prevents most of the rework that plagues cross-functional projects.
Method
- Map who is affected and who can block. Influence and interest are different axes, and the person who can stop you is not always the one most affected.
- Understand what each actually needs. Not their stated position but the outcome they are accountable for, which is usually satisfiable without giving them what they asked for (see negotiation-fundamentals).
- Consult before deciding, inform after. Consultation after a decision is theatre and is recognised as such, which costs more trust than not consulting.
- Match communication to stake. Deeply affected stakeholders need conversation; peripheral ones need a summary. Treating everyone alike overwhelms some and neglects others (see status-updates).
- Surface disagreement early and explicitly. Unresolved objections resurface at the worst moment, and naming them lets them be addressed while it is cheap.
- Record decisions and who was consulted. It ends the relitigation that consumes cross-functional projects (see agent-decision-log).
- Keep them updated through delivery. Alignment decays, and silence is interpreted as either failure or exclusion.
Boundaries
Management of stakeholders is not manipulation; the goal is genuine alignment, and consultation that never changes anything is quickly seen through. Some conflicts are real and must be escalated rather than managed. Too many stakeholders is itself a structural problem (see organizational-design).