Stakeholder Mapping Template: Power, Interest, Evidence and Engagement
A stakeholder map should help a team decide who must be involved, what decision each person can affect, what evidence they need and who owns the next engagement. A two-by-two power–interest grid is a useful first view, but it is not a complete working plan.
This article provides a reusable eight-field template, a scoring method and a worked example.
Why maps fail in practice
The UK Government Analysis Function's stakeholder-mapping guidance uses power and interest to shape engagement and stresses involving the right people at the right time. The common failure is to stop after plotting names. The map becomes a workshop artefact rather than a management control.
Three gaps usually cause that failure:
- “power” is scored without naming the decision or resource controlled;
- “interest” is assumed rather than supported by observed behaviour;
- no owner, next action or review date is assigned.
The STAKE-8 register
Create one row per stakeholder or coherent stakeholder group.
| Field | Question | Minimum evidence |
|---|---|---|
| Stakeholder | Who is affected or can affect the outcome? | Named role, group or external party |
| Trigger decision | Which decision, approval, resource or behaviour matters? | A specific decision or dependency |
| Affected outcome | What changes for this stakeholder? | Benefit, cost, risk or workload |
| Key power | How strongly can they change the result? | 1–5 score plus reason |
| Expressed interest | How much attention are they actually giving? | 1–5 score plus observed evidence |
| Evidence needed | What would let them make a sound decision? | Metric, prototype, case, policy or forecast |
| Engagement action | What is the next useful interaction? | Inform, consult, co-design, decide or monitor |
| Owner and review | Who acts, and when is the map reconsidered? | One accountable owner and date |
A practical prioritisation calculation
Use the grid for orientation, then calculate a review priority:
Priority = Power × Impact × Uncertainty
Score each factor from 1 to 5. Impact measures how strongly the proposed change affects the stakeholder. Uncertainty measures how weak the team's evidence is about the stakeholder's position or needs. Do not include interest in the multiplication: a low-interest stakeholder with high power and high impact may need earlier engagement, not less.
Interpretation:
- 50–125: engage before the next irreversible decision;
- 20–49: include in the current planning cycle;
- 1–19: monitor or communicate routinely.
The thresholds are management rules, not statistical cut-offs. Teams should calibrate them to the cost and reversibility of the decision.
Worked example: a customer-onboarding redesign
| Stakeholder | Decision / dependency | Power | Impact | Uncertainty | Priority | Evidence needed | Next action |
|---|---|---|---|---|---|---|---|
| Head of Sales | Approves new handoff controls | 5 | 4 | 3 | 60 | Delay rate by handoff completeness | Decision workshop |
| Implementation team | Adopts new queue rules | 4 | 5 | 2 | 40 | Workload simulation | Co-design pilot |
| Compliance | Confirms data fields and retention | 5 | 3 | 2 | 30 | Data-flow map | Written review |
| New customers | Supply technical-owner information | 3 | 4 | 4 | 48 | Five interview summaries and form test | Prototype test |
| Finance | Reviews implementation cost | 3 | 2 | 2 | 12 | Cost and payback estimate | Routine update |
The table changes the conversation. “Customers are high interest” is not an action. “Test the form with five new customers before freezing the workflow” is.
Engagement rules by quadrant
| Power / interest | Default action | Important exception |
|---|---|---|
| High / high | Co-design and maintain frequent decision contact | Avoid meeting overload; request decisions explicitly |
| High / low | Keep satisfied with concise, decision-ready evidence | Escalate early when impact or uncertainty is high |
| Low / high | Consult, test and use as an early-warning network | Do not imply decision rights that do not exist |
| Low / low | Monitor with low-cost communication | Re-score when the change affects them materially |
A 30-minute mapping workflow
- Write the decision and its boundary at the top of the page.
- Generate stakeholders from the process, not from the meeting invitation list.
- Complete the decision and affected-outcome fields before scoring.
- Score power, impact and uncertainty independently, then discuss differences.
- Assign evidence, action, owner and review date to every priority above 20.
- Ask a missing-voice question: whose costs, risks or constraints are represented only indirectly?
- Revisit the map after a scope change, failed assumption, new regulation or material stakeholder response.
Quality gate
A usable map passes four tests: every high-priority row names a decision; scores have written reasons; engagement requests evidence or a decision; and every action has an owner and date. If any test fails, the map is still a picture, not a management tool.
Managers and analysts who want to deepen stakeholder discovery, requirements, solution evaluation and evidence-led change can continue with MTF Institute's Professional Certificate in Business Analysis programme.
The practical principle is simple: map influence to a decision, and map engagement to evidence. That is what turns stakeholder analysis into execution.