Protocol
Map the decision, not just the stakeholders
Stakeholder work becomes useful when it is anchored to a decision.
Before you use it
- Use when
- When many people are involved but it is unclear what decision actually needs their attention.
Keep this limit in mind
- Formal governance and accountability still apply. Stakeholder analysis should expose constraints and decision rights, not justify bypassing them.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Write the decision in one sentence, then map who decides, who supplies evidence, who is affected and who can block implementation. This prevents a contact list from masquerading as a decision model.
Steps
- Write the decision and deadline.
- Name the decision owner and required contributors.
- Mark blockers, implementers and affected groups.
- Remove people who have no decision-relevant role.
An example
A master-data change has twelve meeting attendees; the map shows one process owner decides, two countries provide constraints and security can block deployment.
Check your result
The map names one decision, one owner and each participant's decision-relevant role.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingMap the decision, not just the stakeholders
Evidence and sources
A meta-analysis of 65 independent studies found team cognition positively related to team behavioral process, motivational states and performance, with moderation by task and team characteristics.
Shared cognition is not identical to unanimous opinion; teams may need differentiated expertise as well as common understanding.
The Cognitive Underpinnings of Effective Teamwork: A Meta-Analysis · Abstract
Edition and review
Version 0.1.0
No review details are supplied for this edition.