Stakeholder Map

Purpose

A Stakeholder Map helps teams identify, categorize, and prioritize every person or group who has an interest in, influence over, or is affected by a project. The resulting visual guide informs communication plans, change-management strategies, and decision-making processes so that no critical voice is overlooked.

At a glance

• Group size: 4–12
• Duration: 30 minutes
• Difficulty: Beginner
• Facilitation style: Guided collaborative mapping
• Setting: In-person or virtual

How to run

1. Frame the project (3 min). State the initiative, decision, or product the map is for. Write it in the centre of a large canvas.
2. Brainstorm stakeholders (7 min). Silent sticky-note generation. Each participant lists every person, role, team, or external group that comes to mind.
3. Place on the map (5 min). Use a 2×2 grid of *Influence* (high/low) vs *Interest* (high/low). Participants place their notes in the appropriate quadrant.
4. Discuss and adjust (10 min). Review placements as a group. Move notes where consensus shifts them. Identify any missing stakeholders.
5. Define engagement strategy (5 min). For each quadrant, agree on the engagement approach: *Manage closely* (high influence, high interest), *Keep satisfied* (high influence, low interest), *Keep informed* (low influence, high interest), *Monitor* (low influence, low interest).

Materials needed

• Large whiteboard or digital canvas
• Sticky notes and markers
• Pre-drawn 2×2 matrix template

Pitfalls & common mistakes

• Listing only obvious stakeholders. Dig into indirect stakeholders — regulators, end-user communities, support teams.
• Treating the map as static. Revisit and update the map at each project phase.
• Ignoring low-influence groups. They may become vocal detractors if not kept informed.

Inclusion & accessibility

• Invite diverse voices to the mapping session — not just senior leaders.
• Ensure the matrix labels are clearly visible and explained for newcomers.
• Offer asynchronous input for stakeholders in different time zones.

Variations

• Power-Interest Grid (Mendelow): Classic version focused on power and interest axes.
• Stakeholder Onion Diagram: Concentric circles showing proximity to the project.
• RACI-linked map: Combine with a RACI chart to assign responsibilities directly.

When NOT to use this

• For very small, self-contained projects with only one or two known stakeholders — a simple list suffices.
• When stakeholder analysis has already been completed and validated recently.

Source & further reading

• Mendelow, A. L. (1991). Stakeholder Mapping. *Proceedings of the 2nd International Conference on Information Systems.*
• Mitchell, R. K., Agle, B. R., & Wood, D. J. (1997). Toward a Theory of Stakeholder Identification and Salience. *Academy of Management Review.*
• Gamestorming (2010). Stakeholder Analysis. gamestorming.com.