Map stakeholders before a project starts
Map stakeholders before a project starts. A practical guide to identifying everyone affected by or able to influence a project outcome, then categorising them by interest and influence.
To map stakeholders before a project starts, you must identify every person or group who can affect the outcome or will be affected by it, then categorise them by their level of concern and sway so you can plan the right engagement for each. Without this map, you risk missing someone whose quiet opposition or unmet need can halt the project later.
The core method: Interest, Influence grid
The standard tool is the Interest, Influence grid, often called Mendelow’s Matrix (Aubrey Mendelow, 1991). It places stakeholders into four quadrants based on two variables:
- Interest: how much the stakeholder cares about the project’s outcome, either because they benefit from it or because it affects them directly.
- Influence: how much power they have to shape the project’s direction, approve resources, block progress, or alter its scope.
Plot each stakeholder on a simple 2x2 grid:
| Low interest, low influence | High interest, low influence |
|---|---|
| Low interest, high influence | High interest, high influence |
Engagement cadence and format for each quadrant
The Project Management Institute’s PMBOK Guide (7th edition, 2021) gives practice standards for how often and in what format you engage each group. The cadence and format are not optional suggestions; they are the mechanism that keeps stakeholders aligned and prevents surprises.
High influence, high interest (the “key players”)
- Cadence: at least weekly during active project phases (PMI, 2021).
- Format: face-to-face workshops, steering committee meetings, or co-design sessions. These stakeholders need direct dialogue, not written summaries. They can approve or kill a deliverable; treat them as partners.
High influence, low interest (the “keep satisfied” group)
- Cadence: monthly or at key milestones (PMI, 2021).
- Format: executive summaries, formal briefings, or short status reports. They have power but don’t want detail; give them the minimum they need to stay informed and avoid surprising them at a decision point.
Low influence, high interest (the “keep informed” group)
- Cadence: bi-weekly or monthly (PMI, 2021).
- Format: newsletters, focus groups, or open forums. They are affected by the outcome and may have valuable ground-level insight. Engage them in a way that collects their input without slowing the project.
Low influence, low interest (the “monitor” group)
- Cadence: quarterly or at project start and end (PMI, 2021).
- Format: broadcast emails, public notices, or a project website. They need awareness but not active participation. Over-engaging them wastes time; under-engaging them risks a late objection.
Minimum identification techniques
Do not rely on your own memory. The PMBOK Guide (PMI, 2021) lists four minimum techniques for stakeholder identification:
- Brainstorming with the core team and any known stakeholders. List everyone who could be affected, directly or indirectly.
- Interviews with key decision-makers, sponsors, and subject-matter experts. Ask them who else should be involved.
- Document review of project charters, contracts, organisational charts, and previous project records. Past stakeholders often reappear.
- Expert judgement from people who have run similar projects. They can name stakeholder groups you have not considered.
How to spot missing or overlooked stakeholders
The most common failure is to list only obvious names, the sponsor, the client, the team, and miss the people who can derail the project later. Use the salience model (Mitchell, Agle & Wood, 1997) as a detection method. It classifies stakeholders by three attributes:
- Power: the ability to impose their will on the project.
- Legitimacy: the perception that their claims are appropriate or valid.
- Urgency: the degree to which their claim calls for immediate attention.
If a stakeholder possesses at least two of these three attributes, they must be on your map (Mitchell et al., 1997). For example, a neighbour whose property is affected by a renovation has legitimacy and urgency; a regulatory agency that can issue a stop-work order has power and legitimacy. If you have not listed them, your map is incomplete.
Other overlooked categories, drawn from ISO 26000:2010 and FEMA’s Comprehensive Preparedness Guide 101 (v3.0, 2021), include:
- Indirect users (people who use the project’s output but are not the direct client).
- Regulators and inspectors.
- Future generations (if the project has long-term environmental or social impact).
- Supply-chain tiers (subcontractors, material suppliers, logistics providers).
- Non-human entities (in some contexts, environmental or cultural heritage protections).
The stakeholder register
Once identified, record each stakeholder in a register. The PMI (2021) minimum fields are:
- Name
- Role
- Interest level (low, medium, high)
- Influence level (low, medium, high)
- Expectations
- Engagement strategy (which quadrant format and cadence)
Update the register at each project phase gate or after any significant change (PMI, 2021). For household projects, update when the household composition, tenancy, or renovation scope changes (UK planning portal guidance, 2025). For travel-related projects, update when destination entry rules, airline policy, or personal health status changes (IATA Timatic, 2026).
A worked example: household kitchen renovation
Suppose you are planning a kitchen renovation. Your initial list might be: yourself, your partner, the contractor. That is incomplete.
Apply the identification techniques:
- Brainstorming: add children (if they live in the house), neighbours (noise and dust), the landlord (if you rent), the local council (building permits), the insurer (policy coverage).
- Interviews: ask the contractor who else they need to coordinate with, electrician, plumber, cabinet supplier, appliance delivery team.
- Document review: check your lease (landlord approval required), your home insurance policy (renovation exclusions), and the council’s planning portal (permit requirements).
- Expert judgement: ask a friend who did a similar renovation who they forgot to notify.
Now plot them on the Interest, Influence grid:
- High influence, high interest: yourself and your partner (weekly co-design sessions).
- High influence, low interest: the landlord (monthly one-page update); the council building inspector (briefing only when permit is submitted).
- Low influence, high interest: children (bi-weekly check-in on safety and disruptions); neighbours (open forum before work starts and at each loud phase).
- Low influence, low interest: appliance delivery team (email notification of delivery window).
The salience model catches anyone with two of power, legitimacy, or urgency. The neighbour whose fence you will access during construction has legitimacy and urgency; the council has power and legitimacy. Both must be on the register.
When to re-map
Stakeholder mapping is not a one-time activity. Re-map at:
- Each project phase gate (e.g., design complete, permits approved, construction start).
- Any major change in scope, budget, timeline, or team.
- After any incident or exercise after-action review (FEMA CPG 101, 2021).
- For household projects, when a family member joins or leaves, when you move, or when the project’s nature changes (e.g., renovation becomes a full rebuild).
Common mistakes and how to avoid them
- Focusing only on high-influence stakeholders. Low-influence, high-interest groups can become high-influence if they organise or escalate. Engage them early.
- Confusing influence with formal authority. A quiet subject-matter expert may have more sway than a loud sponsor. Ask the team who they listen to.
- Over-engaging low-interest groups. Sending weekly updates to someone who wants quarterly reports creates noise and erodes trust. Follow the PMI cadence guidelines.
- Not updating the register. A stakeholder map from six months ago may be missing a new regulator, a changed role, or a shifted priority. Re-map at phase gates.
The outcome of proper stakeholder mapping
When you map stakeholders before a project starts, you know exactly who needs what, when, and how. You can plan engagement that matches each group’s level of concern and sway, preventing the two most common project failures: a silent blocker who was never engaged, and a resistant stakeholder who was engaged too late. The map gives you a repeatable method, not a one-time guess.
Stakeholder analysis for projects: moving from identification to action
Stakeholder analysis for projects turns a list of names into a workable plan. Begin by scoring each person or group on two axes: their stake in the outcome and their capacity to shape it. Use a simple low-medium-high scale for both dimensions, then place them on the Interest, Influence grid. The grid does more than sort; it dictates your engagement choices for every phase of the Work and project setup.
Once plotted, ask three questions about each stakeholder:
- What do they expect from the project? Write a single sentence for each.
- What would make them oppose the project? Identify the trigger, such as a missed deadline, a budget overrun, or a scope change that affects them.
- What information do they need, and when? Match the answer to the quadrant cadence and format.
This questioning converts static positions into a dynamic engagement plan. A stakeholder who starts with low concern may shift to high concern if the project begins to affect their daily routine. A person with modest sway may gain more if they become a spokesperson for a larger group. Revisit the questions at each phase gate.
How to map project stakeholders: a step-by-step sequence
How to map project stakeholders begins with a blank grid and a disciplined collection process. Follow this sequence to build a complete map in under two hours for most projects.
- Define the project boundary. Write down what is in scope and what is out. A clear boundary tells you who is inside and who sits outside but still matters.
- Run the four identification techniques. Brainstorming, interviews, document review, and expert judgement. Capture every name, role, or group that emerges. Do not filter yet.
- Apply the salience model check. For each name, ask: Do they have power, legitimacy, or urgency? If they hold at least two, they stay on the list. If only one, decide whether monitoring is sufficient.
- Score interest and influence. Use low, medium, high for each. Base scores on evidence, not assumption. Ask the sponsor or a senior team member to validate your scores.
- Plot on the grid. Place each stakeholder in one of the four quadrants.
- Assign engagement cadence and format. Use the PMI guidelines as a starting point, then adjust for your project’s pace and culture. A fast-moving tech project may need daily stand-ups for key players; a multi-year infrastructure project may use monthly steering committees.
- Build the register. Complete the minimum fields for every stakeholder. Store the register where the core team can access it.
Stakeholder engagement planning: from map to sustained alignment
Stakeholder engagement planning translates the map into scheduled actions. For each quadrant, define the communication channel, the owner (who on the team will manage the relationship), and the check-in rhythm.
- Key players: Assign a senior team member as the relationship owner. Schedule recurring meetings with a fixed agenda: progress, risks, decisions needed. Never cancel a key-player meeting without rescheduling; consistency builds trust.
- Keep satisfied: The project sponsor or a designated lead handles this group. Prepare a one-page status report template that covers milestones, budget, risks, and one ask (if any). Send it on a fixed day each month.
- Keep informed: Rotate ownership among the team to spread the load. Use a mix of written updates and live Q&A sessions. Collect feedback through short surveys or open comment periods, and show how input shaped decisions.
- Monitor: Automate where possible. A project microsite or a quarterly email digest is enough. Review the monitor list at each phase gate and promote anyone whose situation has changed.
Document the plan in a simple table with columns for stakeholder name, quadrant, engagement owner, channel, cadence, and last contact date. Review the table in every team meeting for the first month, then monthly thereafter. The goal is not perfect documentation; it is no surprises.
Work and project setup: embedding the map into your routine
Work and project setup succeeds when stakeholder mapping becomes part of the project’s rhythm, not a one-off exercise. Tie the map to your project calendar:
- Kickoff: Build the first map and register. Share the engagement plan with the team.
- Weekly: Check the register for overdue contacts. Update status for any stakeholder whose position has shifted.
- Phase gate: Re-run identification techniques. Re-score interest and influence. Update the register and engagement plan.
- Closeout: Conduct a final stakeholder review. Document who needs a closeout briefing, a thank-you, or a handoff to an operational team.
For small or personal projects, adapt the rhythm. A household renovation might use a single sheet of paper on the fridge, reviewed every Sunday. A freelance assignment might use a notes app with a checklist of client, editor, and source contacts, updated when the brief changes. The principle stays the same: know who matters, understand what they need, and engage them before they have to chase you.
Frequently Asked Questions
Do I need a stakeholder map for a small personal project?
Yes, but you can use a simplified version. For a solo trip or a one-person move, your stakeholder map might have only three entries (yourself, a travel companion, a landlord). Use the same Interest, Influence grid but reduce engagement frequency to the minimum needed. The principle still applies: identify everyone who can affect the outcome, even if the list is short.
How do I handle a stakeholder who refuses to engage?
Document the refusal and its date in the stakeholder register. Attempt engagement through at least two different formats (e.g., a direct email and a phone call). If they remain unresponsive, note the risk in your risk register and plan a mitigation (e.g., proceed with a default assumption, but escalate if their approval is legally required). The PMI (2021) advises that unresponsive stakeholders are still stakeholders; their silence may signal resistance.
What is the difference between a stakeholder map and a communication plan?
A stakeholder map tells you who the stakeholders are and where they sit on interest and influence. A communication plan takes that information and specifies who sends which message, through which channel, at what frequency. The map is the prerequisite; you cannot build a communication plan without it.
How often should I re-map stakeholders for a long-term project?
Re-map at each phase gate or after any significant change in scope, budget, timeline, or team (PMI, 2021). For projects lasting over a year, schedule a formal re-mapping every six months, and a quick check (does the register still look right?) at each monthly status meeting.
Read next
-
Project kickoff checklist
A project kickoff is not a ceremonial gathering.
-
What a useful meeting needs
A useful meeting exists for one reason: to produce an outcome that cannot be produced asynchronously.
-
Work handover checklist
A work handover is complete only when it transfers four things: state, access, decisions, and risks.
-
Launch readiness review
1. Evidence, every claim about readiness must come from a verified authority (government portal, airline database, health agency) and be checked within the last 72 hours before launch. 2.
-
Documents and records
Documents and records are the legally recognised evidence of identity, relationships, property, and instructions that govern your personal and family life.