Stakeholder Identification, Mapping, and Prioritisation

Introduction

Projects are temporary systems of interdependent relationships. Their success depends not only on scope, schedule, cost, and technical quality, but also on the expectations, decisions, resources, legitimacy, and reactions of people and organisations affected by the project. Stakeholder engagement therefore begins before communication planning: the project team must first determine who matters, why they matter, how they may influence outcomes, and how their interests may change over time.

Stakeholder identification, mapping, and prioritisation are especially important in crisis communication. During a disruption, the project team may have limited time, incomplete information, and competing demands from regulators, sponsors, employees, customers, communities, suppliers, and the media. A stakeholder who appears peripheral during normal operations may become decisive during a crisis. Effective prioritisation must therefore be dynamic rather than a one-time administrative exercise.

This chapter examines internal and external stakeholders and applies six complementary approaches: the power–interest grid, influence–impact matrix, stakeholder salience model, network analysis, stakeholder personas, and the stakeholder register. No single model captures the full complexity of stakeholder relationships. Professional judgement is required to combine them, challenge assumptions, and revise priorities as the project develops.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Distinguish internal, external, primary, secondary, and intermediary stakeholders.
2. Identify stakeholders systematically across the project life cycle.
3. Apply power–interest grids and influence–impact matrices appropriately.
4. Use the salience model to assess power, legitimacy, and urgency.
5. Explain how network analysis reveals indirect influence and communication bottlenecks.
6. Construct evidence-based stakeholder personas and a useful stakeholder register.
7. Integrate multiple tools to prioritise engagement in complex projects.
8. Recognise ethical, cultural, governance, and data-protection issues in stakeholder analysis.

1. Understanding Stakeholders

A stakeholder is an individual, group, or organisation that can affect, be affected by, or perceive itself to be affected by a project, decision, or outcome. This broad definition is strategically useful because perceived effects can influence behaviour even when a project team believes that an effect is minor or indirect.

Stakeholders differ from customers. A customer purchases or receives a product or service, whereas a stakeholder may provide resources, grant approval, impose constraints, bear risks, advocate for a cause, or influence public acceptance. A stakeholder may also occupy several roles simultaneously. For example, a government department may be a regulator, funder, landowner, and future user of a project.

1.1 Internal and external stakeholders

Internal stakeholders are located within the project organisation or its sponsoring enterprise. They commonly include:

• project sponsors and steering committees;
• project managers, team members, and functional managers;
• employees and employee representatives;
• portfolio, programme, finance, legal, procurement, risk, and information-security functions;
• owners, directors, and internal audit teams.

External stakeholders are outside the project organisation but may influence or experience its consequences. They may include:

• customers, users, and beneficiaries;
• suppliers, contractors, consultants, and alliance partners;
• regulators, public authorities, and emergency services;
• local communities, citizens, and advocacy groups;
• lenders, insurers, investors, and rating agencies;
• competitors, professional bodies, media organisations, and non-governmental organisations.

The distinction is not always stable. A contractor embedded in the project team may be operationally internal but legally external. Similarly, a joint-venture partner may share governance rights with the sponsoring organisation. The analysis should therefore record the relationship and decision rights rather than rely only on organisational boundaries.

1.2 Primary, secondary, and intermediary stakeholders

Primary stakeholders have a direct stake in project decisions or outcomes. Secondary stakeholders may not transact directly with the project but can influence its acceptance or consequences. Intermediary stakeholders transmit information, resources, or pressure between other parties. Examples include trade associations, community leaders, professional advisers, elected representatives, and journalists.

Stakeholder categories should not be treated as rankings. A small community group may have limited formal power but substantial legitimacy and the ability to mobilise public opposition. Conversely, a powerful executive may have low day-to-day interest but can make a decision that changes the project immediately.

2. The Identification Process

Identification is a structured process, not a brainstorming event completed at project initiation. A robust process normally combines documentary review, interviews, workshops, process analysis, network exploration, and ongoing environmental scanning.

2.1 Sources of identification

Useful sources include:

• the business case, charter, contract, benefits map, and procurement documents;
• organisational charts, governance terms of reference, and decision-rights matrices;
• regulatory approvals, licences, impact assessments, and compliance obligations;
• work breakdown structures and process maps;
• risk, issue, assumption, and dependency logs;
• customer research, complaints, service data, and user journeys;
• previous project lessons and stakeholder registers;
• interviews with sponsors, subject-matter experts, frontline workers, and community representatives;
• analysis of professional networks, partnerships, and informal influence.

A useful identification prompt is: “Who can stop, delay, enable, reshape, legitimise, fund, use, suffer from, or publicly interpret this project?” The question should be applied separately to normal operations, benefits realisation, and crisis conditions.

2.2 A practical identification sequence

First, define the project boundary and intended outcomes. Second, list parties connected to authority, resources, delivery, use, regulation, risk, and social acceptance. Third, identify representatives of affected or less visible groups. Fourth, examine indirect relationships and dependencies. Fifth, validate the list with people who possess local, technical, cultural, or operational knowledge. Finally, record uncertainty rather than forcing premature certainty.

Stakeholder identification should be repeated at stage gates, after major scope changes, following incidents, and when external conditions change. A new technology, regulator, supplier failure, election, merger, or public controversy may alter the stakeholder system substantially.

3. Mapping and Prioritising Stakeholders

Mapping translates a long stakeholder list into a decision-support view. Prioritisation determines where scarce engagement time, senior attention, information, and relationship-building effort should be concentrated. It does not mean that low-priority stakeholders can be ignored. It means that the form, frequency, and ownership of engagement should be proportionate to the stakeholder’s relevance and the project’s obligations.

3.1 Power–interest grid

The power–interest grid classifies stakeholders according to their ability to influence project decisions and their level of concern about project outcomes.

Power may be formal, resource-based, expert, relational, reputational, or coercive. Interest may reflect exposure, benefits, values, professional responsibility, or political incentives. A low-interest stakeholder can become highly interested after a safety incident or public announcement.

The grid is simple and communicable, but it has limitations. It can imply that power and interest are fixed, conceal differences within stakeholder groups, and privilege formal authority over moral legitimacy. It should therefore be used as an initial map rather than a final decision rule.

3.2 Influence–impact matrix

The influence–impact matrix separates a stakeholder’s capacity to shape the project from the magnitude of the project’s effects on that stakeholder. This distinction is valuable when affected groups have little formal power.

For example, a transport infrastructure project may have high influence and high impact for the transport authority, but low influence and high impact for residents whose homes experience construction disruption. The second group requires meaningful consultation and mitigation, not merely a newsletter.

3.3 Stakeholder salience model

The salience model, associated with Mitchell, Agle, and Wood, assesses three attributes:

• Power: the capacity to impose or obtain outcomes.
• Legitimacy: the perceived validity or appropriateness of the stakeholder’s relationship with the project.
• Urgency: the degree to which a claim requires immediate attention because of time sensitivity or criticality.

Stakeholders possessing one attribute are often described as latent stakeholders; those possessing two are expectant stakeholders; and those possessing all three are definitive stakeholders. The model identifies combinations such as dormant, discretionary, demanding, dominant, dangerous, and dependent stakeholders.

The model is not a numerical scoring formula. It is a conceptual classification device. Its value lies in asking three different questions rather than collapsing all importance into one score. A dependent stakeholder may have legitimate and urgent claims but little power, requiring the project organisation to provide support or representation. A dangerous stakeholder may have power and urgency but questionable legitimacy, requiring careful governance and risk controls.

Salience is contingent. A community group can gain urgency after an environmental incident; a regulator can gain power through a new legal instrument; and a previously legitimate representative may lose credibility if conflicts of interest emerge.

3.4 Network analysis

Stakeholder relationships form a network rather than a list. Network analysis examines who is connected to whom, through which channels, and with what strength or direction. It can reveal brokers, isolated groups, communication bottlenecks, coalitions, and hidden dependencies.

A network can be represented as a graph G = (V, E), where V is the set of stakeholder nodes and E is the set of relationships or ties. A tie may represent information exchange, authority, funding, trust, dependency, or conflict. The meaning of the tie must be specified before analysis.

For a stakeholder i, degree centrality in an unweighted network is:

where deg(i) is the number of direct ties connected to stakeholder i. In a directed network, in-degree counts incoming ties and out-degree counts outgoing ties. In a weighted network, degree may be replaced by the sum of tie weights, provided the weights are defined consistently.

Betweenness centrality assesses how often a node lies on shortest paths between other nodes:

Here, σ_st is the number of shortest paths from stakeholder s to stakeholder t, and σ_st(v) is the number of those paths passing through stakeholder v. The measure is meaningful only when “shortest path” represents a defensible interpretation of access, communication, or influence. A high-betweenness stakeholder may act as a broker, but centrality does not automatically imply trust, legitimacy, or positive influence.

Network analysis is particularly useful for crisis communication. It can identify who receives information quickly, who connects disconnected communities, and where misinformation may spread. Ethical use requires transparency, respect for privacy, and avoidance of surveillance beyond the project’s legitimate purpose.

3.5 Stakeholder personas

A stakeholder persona is a structured, evidence-based representation of a stakeholder type. It should not be a fictional stereotype. A useful persona may include:

• role and relationship to the project;
• objectives, benefits sought, and concerns;
• decision rights and constraints;
• preferred language, channels, and information needs;
• likely reactions to delay, failure, or uncertainty;
• accessibility, cultural, or safeguarding considerations;
• trusted sources and potential barriers to participation.

Personas help teams design communication that is relevant rather than organisation-centred. For example, an emergency-services persona may prioritise interoperable data, response times, and clear escalation routes, whereas a resident persona may prioritise disruption, safety, compensation, and credible evidence. Personas must be validated with real stakeholders and reviewed when evidence changes.

3.6 The stakeholder register

The stakeholder register is the operational record that connects analysis to action. It commonly includes:

The register should be access-controlled because it may contain personal data, sensitive judgements, or commercially confidential information. It should record evidence and uncertainty, not unsupported labels such as “difficult” or “unreasonable.”

4. Integrating the Models

The models answer different questions and should not be treated as competing substitutes.

A practical integrated method is as follows:

1. Build a broad stakeholder inventory.
2. Segment groups where interests, exposure, or influence differ.
3. Assess power, influence, impact, legitimacy, and urgency with evidence.
4. Map relationships and identify brokers, coalitions, and isolated groups.
5. Develop personas for strategically important or highly affected groups.
6. Set engagement objectives, owners, channels, and escalation routes.
7. Record the result in the register.
8. Test the analysis with stakeholders and independent reviewers.
9. Reassess at agreed triggers and during crises.

Engagement priority and proportionality

Prioritisation should consider at least four dimensions: consequence of stakeholder action or inaction, consequences experienced by the stakeholder, legitimacy of the claim, and time sensitivity. A high priority does not necessarily mean daily meetings. It may mean rapid notification, formal consultation, executive sponsorship, independent representation, or enhanced monitoring.

The project team should distinguish between engagement priority and communication frequency. A stakeholder may need infrequent but high-quality decision briefings, while another may need frequent operational updates but have limited decision authority.

5. Worked Application: Regional Hospital Information-System Project

The following is an illustrative case.

Background

A regional health authority is implementing an integrated electronic patient-record system across three hospitals, community clinics, and emergency services. The project promises improved continuity of care, reduced duplication, and better reporting. It also involves privacy risks, workflow disruption, training demands, and dependence on a technology supplier.

Problem

The initial project plan identifies the health authority, software supplier, and hospital executives but gives limited attention to nurses, patients, disability advocates, emergency responders, privacy regulators, and clinicians working across organisational boundaries. A pilot reveals resistance among nurses and concern from patient representatives about consent and data access.

Analysis

The power–interest grid places the health authority and privacy regulator in the high-power, high-interest category. Hospital executives have high power and high interest during deployment. The software supplier has high influence over technical delivery but may have lower legitimacy regarding patient-data policy. Nurses and physicians have high impact from workflow changes and significant informal influence, even where their formal authority is limited.

The influence–impact matrix identifies patients with complex care needs as low formal influence but high impact. This requires accessible consultation, testing with representative users, and safeguards against exclusion. Emergency responders have high influence and high impact because system failure could affect urgent care.

The salience model identifies the privacy regulator as definitive: it has power, legitimacy, and urgency when compliance issues arise. A patient advocacy organisation may be dependent: its claims are legitimate and sometimes urgent, but it has limited direct power. It should not be dismissed; the project may need to create participation mechanisms that strengthen its voice.

Network analysis shows that senior clinicians connect hospital leadership, frontline staff, and professional bodies. These clinicians are potential brokers. It also reveals that the supplier’s technical team communicates directly with only a small group of project managers, creating a bottleneck and a risk that frontline problems will be filtered or delayed.

Personas are developed for a ward nurse, a patient with limited digital access, an emergency dispatcher, and a privacy officer. Each persona identifies different information requirements and failure concerns. The register assigns an engagement owner to each group and records desired engagement states, including “actively involved” for clinical representatives and “consulted with documented response” for patient advocates.

Approach and solution

The project establishes a clinical design council, a patient and carer advisory panel, privacy-by-design reviews, and a supplier escalation protocol. It uses demonstrations rather than only written updates, provides training during paid working time, offers non-digital participation routes, and publishes a decision log explaining how feedback was handled. A crisis communication protocol specifies that suspected data exposure is reported immediately through the regulator-approved route, while affected patients receive clear, factual, and accessible information.

Outcome

The pilot is delayed by four weeks but achieves higher adoption in the second test cycle. Several workflow defects are corrected before full deployment. Patient representatives identify confusing consent language, and the project changes the design. The register is updated to reflect that frontline clinicians have become more influential than originally assessed.

Learning points

1. Formal authority alone does not explain implementation success.
2. High-impact, low-power stakeholders require protection and voice.
3. Network brokers can accelerate or distort communication.
4. Personas are useful only when based on evidence and validated.
5. Stakeholder priorities change as the project moves from design to deployment and crisis readiness.

6. Governance, Ethics, and Contemporary Practice

Stakeholder analysis has ethical consequences. Labelling a group as low power or low interest can become a self-fulfilling justification for exclusion. Engagement should respect dignity, informed participation, accessibility, cultural difference, and the right to challenge project assumptions. Consultation is not meaningful if decisions have already been fixed or if inconvenient feedback is merely recorded and ignored.

Projects should distinguish legitimate confidentiality from secrecy. Commercial, personal, security, and legal information may require restricted access, but confidentiality should not be used to prevent affected people from understanding material risks. Registers containing personal data should follow applicable data-protection law, data minimisation, retention, access-control, and accuracy principles.

Artificial intelligence can support stakeholder analysis by clustering feedback, detecting emerging topics, identifying sentiment shifts, or summarising large consultation datasets. However, automated classification may reproduce bias, misinterpret sarcasm or cultural meaning, and infer sensitive characteristics without consent. AI outputs should be treated as decision support, not as authoritative judgements about legitimacy, trustworthiness, or priority. Human review, explainability, audit trails, representative training data, and clear governance are essential.

Contemporary projects increasingly operate through ecosystems rather than single organisations. Platform partners, online communities, regulators, citizen groups, and distributed workforces may influence outcomes across geographical boundaries. Social media can shorten the time between an incident and public reaction, making network awareness and pre-agreed escalation routes important. Nevertheless, speed should not replace accuracy. During a crisis, the project should communicate what is known, what is unknown, what is being done, and when the next update will occur.

7. Challenges and Limitations

Stakeholder mapping involves judgement. Power may be hidden, contested, or temporary. Interest may be inferred incorrectly. Groups may contain conflicting subgroups, and representatives may not speak for everyone. Networks are difficult to measure because relationships are private, informal, and context-dependent. Salience can privilege actors who already possess institutional recognition unless legitimacy is critically examined.

Other common problems include:

• treating the register as a static compliance document;
• confusing communication activity with genuine engagement;
• using a single score that conceals ethical distinctions;
• failing to identify indirect or future stakeholders;
• underestimating internal stakeholders who control implementation;
• neglecting language, disability, digital access, or cultural barriers;
• collecting stakeholder data without adequate governance;
• allowing senior voices to dominate workshops;
• assuming silence indicates agreement;
• failing to document how stakeholder input changed decisions.

These limitations do not make the tools useless. They indicate that mapping should be triangulated, participatory, documented, and regularly challenged.

Best-Practice Checklist

Before approving a stakeholder engagement approach, the project team should be able to answer yes to the following questions:

• Have internal and external stakeholders been identified across the full life cycle?
• Have affected but low-power groups been included?
• Are formal authority and informal influence assessed separately?
• Have legitimacy and urgency been considered, not just power?
• Are stakeholder groups segmented where their interests differ?
• Have key relationships, brokers, conflicts, and communication gaps been mapped?
• Are personas based on evidence and validated?
• Does the register contain owners, actions, evidence, and review dates?
• Are privacy, accessibility, cultural, and safeguarding requirements addressed?
• Are crisis-specific stakeholders and escalation routes identified?
• Is there a clear process for revising priorities after change or new evidence?

Chapter Summary

Stakeholder identification is the foundation of purposeful engagement and crisis communication. Stakeholders may be internal or external, direct or indirect, powerful or marginalised, and their relevance can change over time. The power–interest grid offers a simple prioritisation view; the influence–impact matrix distinguishes capacity to shape outcomes from exposure to consequences; and the salience model adds legitimacy and urgency. Network analysis reveals indirect influence, brokers, and communication pathways. Personas translate analysis into stakeholder-sensitive communication, while the stakeholder register converts judgements into accountable actions.

No model should be used mechanically. Effective practice combines methods, records evidence and uncertainty, validates assumptions, protects stakeholder rights, and reviews priorities at defined triggers. In complex and crisis-prone projects, the most responsible approach is both strategically selective and ethically inclusive: scarce attention must be prioritised, but affected people must not be made invisible simply because they lack formal power.

Key Terms

Stakeholder: An individual, group, or organisation that can affect, be affected by, or perceive itself to be affected by a project.

Internal stakeholder: A stakeholder within the sponsoring or delivering organisation.

External stakeholder: A stakeholder outside the sponsoring or delivering organisation.

Primary stakeholder: A party with a direct stake in project decisions or outcomes.

Secondary stakeholder: A party with an indirect stake or indirect influence.

Power: The capacity to obtain or impose an outcome.

Interest: The degree of concern or involvement a stakeholder has in project outcomes.

Influence: The ability to shape decisions, behaviour, or perceptions.

Impact: The magnitude of effects experienced by a stakeholder or project.

Legitimacy: The perceived appropriateness or validity of a stakeholder’s relationship or claim.

Urgency: The time sensitivity or criticality of a stakeholder claim.

Salience: The prominence a stakeholder has for managerial attention, based on power, legitimacy, and urgency.

Stakeholder register: The controlled record of stakeholder identities, characteristics, engagement needs, owners, and actions.

Stakeholder persona: An evidence-based representation of a stakeholder type used to design engagement.

Network analysis: The study of relationships and connections among stakeholders.

Broker: A stakeholder that connects otherwise weakly connected groups or pathways.

Engagement: The process of building and managing relationships and participation with stakeholders.

Crisis communication: Planned and responsive communication during events that threaten project objectives, safety, legitimacy, or continuity.

Review Questions

Short Answer Questions

1. Distinguish between internal and external stakeholders, giving one example of each.
2. What are the two dimensions of a power–interest grid?
3. Define legitimacy and urgency in the stakeholder salience model.
4. What is the purpose of a stakeholder persona?
5. Why should a stakeholder register be reviewed throughout the project life cycle?

Long Answer Questions

1. Compare the power–interest grid, influence–impact matrix, and salience model. Explain when each is most useful.
2. Explain how network analysis can improve crisis communication planning.
3. Describe a systematic process for identifying stakeholders in a complex programme.
4. Discuss the ethical risks of classifying stakeholders according to power and influence.
5. Explain how a stakeholder register can convert analysis into accountable engagement actions.

Analytical / Application Questions

1. A renewable-energy project has strong government support but opposition from local residents and environmental groups. Use the influence–impact matrix and salience model to design a differentiated engagement approach.
2. A supplier’s system failure disrupts a public-service project. Explain how stakeholder priorities and communication channels should be reassessed during the first 24 hours.
3. Construct a stakeholder register outline for a university-wide digital transformation project. Include at least six stakeholder groups, their likely interests, engagement priority, and an appropriate engagement response.

Multiple Choice Questions with Answers

Question 1

Which stakeholder is most likely to require protection and meaningful participation in an influence–impact analysis?

A. High-influence, low-impact stakeholder

B. Low-influence, high-impact stakeholder

C. High-influence, low-impact supplier

D. Low-influence, low-impact observer

Correct Answer: B. Low-influence, high-impact stakeholder

Question 2

Which three attributes form the stakeholder salience model?

A. Power, interest, and cost

B. Influence, impact, and risk

C. Power, legitimacy, and urgency

D. Authority, budget, and schedule

Correct Answer: C. Power, legitimacy, and urgency

Question 3

What is the principal purpose of a stakeholder register?

A. To replace the project schedule

B. To record stakeholder information and assign engagement actions

C. To calculate project profitability

D. To approve technical designs

Correct Answer: B. To record stakeholder information and assign engagement actions

Question 4

In an unweighted network, degree centrality measures the:

A. Number of direct ties connected to a stakeholder

B. Number of project risks owned by a stakeholder

C. Strength of stakeholder legitimacy

D. Time required to communicate with a stakeholder

Correct Answer: A. Number of direct ties connected to a stakeholder

Question 5

A stakeholder with high power and low interest should generally be:

A. Managed closely through daily consultation

B. Kept satisfied with proportionate assurance

C. Excluded from project communications

D. Treated as a low-impact user

Correct Answer: B. Kept satisfied with proportionate assurance

Question 6

Which statement best describes a stakeholder persona?

A. A legally binding stakeholder contract

B. A project risk score assigned to an individual

C. An evidence-based representation of a stakeholder type

D. A list of all project deliverables

Correct Answer: C. An evidence-based representation of a stakeholder type

Question 7

Why is stakeholder prioritisation dynamic?

A. Stakeholder roles, urgency, influence, and impacts can change

B. The project budget always increases over time

C. All stakeholders become high power at project closure

D. Communication channels never remain stable

Correct Answer: A. Stakeholder roles, urgency, influence, and impacts can change

Question 8

In the betweenness-centrality formula, σ_st(v) represents:

A. All stakeholders in the project

B. The number of shortest paths from s to t passing through v

C. The total number of project risks

D. The strength of a stakeholder’s formal authority

Correct Answer: B. The number of shortest paths from s to t passing through v

Question 9

Which practice is most appropriate when using AI to analyse stakeholder feedback?

A. Accept automated classifications without review

B. Use AI outputs as decision support with human oversight

C. Infer sensitive characteristics without informing participants

D. Replace all stakeholder interviews with sentiment analysis

Correct Answer: B. Use AI outputs as decision support with human oversight

Question 10

A stakeholder has legitimate and urgent claims but little formal power. Which salience category is most closely associated with this situation?

A. Dependent stakeholder

B. Dormant stakeholder

C. Dominant stakeholder

D. Discretionary stakeholder

Correct Answer: A. Dependent stakeholder