Question
Ask what each stakeholder can block or enable
Power is task-specific, not only hierarchical.
Before you use it
- Use when
- When influence is being estimated from job titles alone.
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.
A question to ask
What can this person approve? · What evidence or access do they uniquely hold? · What can fail if they disengage? · What can proceed without them?
Why it matters
For each relevant stakeholder, name the resource, approval, information or adoption behavior they can enable or block. This makes influence operational rather than political theater.
An example
A local data lead cannot approve global design but can block a migration by withholding country mapping and validation capacity.
Check your result
The map explains each stakeholder's concrete leverage on the outcome.
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 readingAsk what each stakeholder can block or enable
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaSeparate decision owner from contributors
Evidence and sources
A meta-analysis of 72 independent studies found team information sharing positively related to performance, cohesion, decision satisfaction and knowledge integration, with meaningful moderators.
The useful form and amount of sharing depend on task, discussion structure and how information is distributed.
Information Sharing and Team Performance: A Meta-Analysis · Abstract
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.