What Is Stakeholder Management? Process, Tools and Project Example

Stakeholder management is the continuous process of identifying the people and groups who can influence a project or be affected by it, understanding their interests and impact, and planning how to involve them in decisions and delivery.

It is not simply a communication schedule. Effective stakeholder management connects relationships with project choices: who must approve an outcome, whose knowledge is needed, who may experience disruption, where resistance could arise and who is accountable for each engagement action.

The process should begin before major decisions are fixed and continue throughout the project. Stakeholder priorities, influence and attitudes can change as scope develops, risks emerge and outcomes become visible.

In practical terms, stakeholder management helps a project team answer six questions:

1. Who can affect the project or be affected by it?
2. What matters to each person or group?
3. How much influence and impact do they have?
4. Which decisions or activities require their involvement?
5. How should the relationship be managed and by whom?
6. What has changed since the assessment was last reviewed?

A stakeholder can be an individual, group or organisation with an interest or role in the project, or one affected by its outcome. The Association for Project Management notes that stakeholders commonly exist both inside and outside the organisation funding the work.

This means a project team must look beyond the sponsor and customer. Employees, users, suppliers, regulators, local communities and operational teams may hold essential knowledge or experience consequences even when they have little formal authority.

These terms are related but not interchangeable.

Management establishes the structure; engagement is how the relationship works in practice; communication supports both. Sending a monthly report may meet a communication commitment, but it does not prove that the recipient was heard, understood the implications or contributed to the decision.

The word “management” should not imply control over people. Project managers often have no authority over many stakeholders and must rely on credibility, listening, evidence and influence. APM therefore places strong emphasis on engagement and relationship building alongside the management process.

Stakeholders should be identified according to their relationship with the work, not only their job title.

One person may belong to more than one category. An operations manager, for example, may provide requirements, approve readiness and later own the new process. Record these different interests rather than reducing the person to a single label.

The process is iterative. A six-step sequence provides enough structure without treating the stakeholder assessment as a one-off administrative exercise.

1. Identify stakeholders early

Start by reviewing the business case, project charter, contracts, organisational structure, regulatory requirements and planned benefits. Then ask the sponsor, delivery team and subject specialists who is missing.

Useful prompts include:

• Who funds, approves or can stop the work?
• Who supplies knowledge, people, systems or materials?
• Who will use, operate or support the outcome?
• Whose role, workload or authority will change?
• Who may experience unintended effects?
• Who represents people that are rarely consulted directly?

Record confirmed stakeholders in a register. Avoid relying on one senior person’s list, as it may overlook operational users, external groups or dissenting perspectives.

2. Analyse interests, influence and impact

Stakeholder analysis should explain behaviour, not merely assign a score. For each important stakeholder, explore:

• Their expected benefits and potential losses.
• Their authority over funding, scope, resources or acceptance.
• How strongly the project affects them.
• Their current understanding and attitude.
• Knowledge or resources the project needs from them.
• Relationships with other decision-makers.
• Preferred ways to participate and receive information.

Use evidence from interviews, workshops, previous projects and observed decisions. Assumptions about motivation should be labelled and tested rather than presented as fact.

3. Prioritise without ignoring affected groups

A power–interest grid is a useful starting point for deciding where management attention is needed.

The grid has limits. Low formal power does not mean low impact, and a large affected community should not be ignored because it lacks decision authority. Influence can also change quickly during a dispute, regulatory review or public campaign.

Use the grid to allocate attention, not to decide whose interests matter.

4. Plan engagement around decisions and outcomes

For each priority stakeholder, define what the project needs from the relationship and what the stakeholder reasonably needs from the project.

A useful plan records:

• The decision, contribution or outcome involved.
• Current and desired level of support or participation.
• Key concerns and information needs.
• Engagement method and frequency.
• Relationship owner.
• Actions, due dates and escalation route.
• Evidence that the engagement is working.

Planning around decisions is stronger than writing “send a monthly update”. A sponsor may need to approve a scope change, users may need to test a prototype and a regulator may need evidence before a release. Each requires a different form of engagement.

5. Engage, listen and follow through

Engagement can include interviews, workshops, demonstrations, consultations, negotiations, briefings and informal conversations. Select the method according to the stakeholder, decision and level of impact.

The quality of the interaction matters more than the number of meetings. Good engagement should:

• Explain the purpose and boundaries honestly.
• Ask for input while it can still influence the outcome.
• Make technical information understandable.
• Record decisions, commitments and unresolved concerns.
• Clarify what happens next and who owns the action.
• Report back on how feedback was used or why it could not be adopted.

The last point prevents consultation from feeling performative. The APM’s principles of stakeholder engagement emphasise consulting early and often, understanding people and taking responsibility for engagement.

6. Monitor relationships and update the strategy

Review the stakeholder picture at project milestones and whenever there is a material change in scope, leadership, risk, delivery approach or external conditions.

Ask:

• Has anyone gained or lost influence?
• Have expectations or concerns changed?
• Are decisions being delayed by missing input?
• Are agreed actions being completed?
• Is resistance increasing, decreasing or shifting?
• Have new affected groups emerged?
• Does the current engagement method still work?

Update the register, map and plan together. A current contact list attached to an outdated engagement strategy is not effective stakeholder management.

These tools serve different purposes and should not be merged into one overloaded document.

Protect personal and sensitive information. A register may contain views about influence, resistance or relationships and should have appropriate access controls rather than being distributed as a general contact sheet.

Copyable stakeholder register fields

Use these fields as a practical starting point:

Worked Example: Introducing a New Procurement System

Imagine a company replacing its purchasing system. The objective is to improve control and reduce processing time, but the change affects approvals, supplier information, finance controls and daily work across several departments.

An initial stakeholder plan could look like this:

Suppose department approvers resist the new workflow because they expect slower purchasing. Labelling them “difficult stakeholders” would not solve the problem. The project team should measure the expected additional time, demonstrate the control requirement, test simplified approval rules and agree which purchases genuinely need senior approval.

The engagement outcome is not that everyone likes the system. It is that valid concerns shape the design, constraints are understood and accountable decisions are made before launch.

Resistance is information. It may reveal a misunderstood benefit, a genuine operational risk, loss of authority, competing priorities, poor timing or lack of trust.

Use a structured response:

1. Describe the behaviour and impact: Separate observable facts from assumptions about attitude.
2. Listen for interests: Ask what outcome, risk or constraint is driving the position.
3. Clarify fixed and flexible elements: Identify what cannot change and what can be negotiated.
4. Develop options: Compare effects on value, risk, cost, schedule and affected groups.
5. Use agreed decision rights: Confirm who recommends, approves and must be consulted.
6. Document the decision: Record rationale, actions, owners and review conditions.
7. Escalate proportionately: Escalate when authority, risk or unresolved impact exceeds the team’s limits not simply because a conversation is uncomfortable.

Listening does not mean accepting every request. It means understanding the concern well enough to make and explain a defensible decision.

Avoid relying only on the number of emails, meetings or attendees. These measure activity, not relationship quality or project value.

Better indicators include:

• Time taken to obtain critical decisions or approvals.
• Percentage of engagement actions completed on time.
• Number and age of unresolved stakeholder issues.
• Late requirement changes caused by missed involvement.
• Rework resulting from misunderstood expectations.
• Participation from required groups at key reviews.
• Change in support, confidence or understanding at defined points.
• Quality and timeliness of stakeholder contributions.

Select a small set connected to the project’s risks. For example, a regulated project may track approval evidence and unresolved compliance issues, while a service redesign may focus on user participation, acceptance and late rework.

Stakeholder management becomes effective when project structure is combined with communication, listening, negotiation and responsible follow-through. A register and map can guide attention, but the project team still needs the judgement to build trust, surface disagreement and turn engagement into timely decisions.

LOTC’s Project Leadership and Communications Management course develops project leadership, communication planning, stakeholder relationship management, conflict resolution and team collaboration. The five-day classroom-based programme is suitable for project managers, project leaders and professionals responsible for delivery through diverse teams and stakeholders.

Review the course outline or contact LOTC on WhatsApp to discuss individual or tailored corporate training requirements.