Stakeholder Identification

A stakeholder is anyone who can affect or be affected by the project — its decisions, activities, or outcomes. Identifying stakeholders early and thoroughly is one of the most critical activities in project initiation. Missing a key stakeholder can lead to late-stage surprises, resistance, and project failure.

Who Are Stakeholders?

Stakeholders are not just the people paying for the project. They include a much wider circle:

Internal Stakeholders Project sponsor, project team, department heads, executives, employees affected by the change, PMO

External Stakeholders Customers, end users, vendors, suppliers, regulators, government agencies, partners

Positive Stakeholders Those who benefit from the project's success — sponsors, users, team members gaining new skills

Negative Stakeholders Those who may be adversely affected — employees displaced by automation, competitors, resistant departments

How to Identify Stakeholders

1. Start with the Obvious

Begin with stakeholders explicitly named in the project charter: the sponsor, project manager, and any specifically mentioned departments or clients. Then expand outward.

2. Ask the "Who" Questions

Who requested this project?
Who is funding it?
Who will use the deliverables?
Who will maintain it after delivery?
Who has authority to approve or reject work?
Who could block or delay the project?
Who will be affected by the change — positively or negatively?
Who has done similar projects before and has relevant experience?

3. Use Organizational Charts

Walk the org chart systematically. For each department, ask: does this project touch their work, data, processes, or people? If yes, someone from that department is a stakeholder.

4. Check External Boundaries

Don't forget people outside the organization: regulatory bodies, vendors, customers, partner organizations, and community groups that may be affected.

5. Ask Existing Stakeholders

"Who else should be involved?" — this simple question, asked to each identified stakeholder, often uncovers people you'd otherwise miss. It's a snowball technique that expands your stakeholder map organically.

The Power/Interest Grid

Once identified, stakeholders need to be classified to determine the right engagement strategy. The Power/Interest Grid (also called Mendelow's Matrix) is the most widely used tool:

Low Interest

High Interest

High Power

Keep Satisfied Powerful but not deeply interested. Keep them informed to avoid surprises. Don't overwhelm with details.

Manage Closely Your most critical stakeholders. Engage actively — regular meetings, early input on decisions, proactive communication.

Low Power

Monitor Low power, low interest. Keep an eye on them but don't over-invest in engagement. Status updates suffice.

Keep Informed Interested but not powerful. Keep them updated — they can be advocates or early-warning systems for issues.

The Stakeholder Register

Document your findings in a stakeholder register — a living document that tracks all identified stakeholders and their attributes:

Field	What to Capture
Name & Role	Who they are and their position in the organization
Department / Org	Where they sit — internal department or external organization
Interest	What they care about — cost, schedule, quality, specific features?
Power / Influence	Their ability to affect the project — decision authority, budget control, political influence
Attitude	Supportive, neutral, or resistant? This shapes your engagement strategy
Engagement Strategy	How you'll engage them — frequency, channel, level of detail
Communication Needs	Preferred communication method — email, meetings, dashboards, reports

Common Pitfalls

Identifying too late: Discovering a key stakeholder midway through execution is far more disruptive than identifying them during initiation.
Ignoring negative stakeholders: People who oppose the project are still stakeholders. Understanding their concerns early gives you a chance to address resistance proactively.
Treating it as one-time: Stakeholder identification is ongoing. New stakeholders emerge as the project progresses — team changes, organizational shifts, new regulations.
Focusing only on seniority: An end user with no formal power can derail adoption. A junior developer may hold critical technical knowledge. Look beyond the org chart hierarchy.

Stakeholder identification feeds directly into your communication plan, risk register, and change management strategy. The Power/Interest Grid is your starting point — but the real work is building relationships over time. A stakeholder who feels heard and respected is far more likely to support the project when tough decisions arise.