Salience Model: 7 Stakeholder Types Explained
The Salience Model is the framework most project managers reach for when too many stakeholders compete for attention and the team has to decide who matters right now. Three yes/no attributes (power, legitimacy, urgency) classify each stakeholder into one of seven types, and the type tells you whether to engage immediately, monitor, or filter out for now.
This guide covers what the Salience Model is and the three attributes that drive classification. It walks through the seven stakeholder types and how to engage each one. It also includes comparisons to other stakeholder frameworks and the mistakes that turn a good model into a static slide. Use the Salience Builder widget further down to map your own project's stakeholders.
Quick Answer: What Is the Salience Model?
The Salience Model is a stakeholder-prioritization framework that classifies stakeholders by three attributes: power, legitimacy, and urgency. It was introduced by Ronald Mitchell, Bradley Agle, and Donna Wood in their 1997 paper Toward a Theory of Stakeholder Identification and Salience, published in the Academy of Management Review. Stakeholders with all three attributes are Definitive (highest priority). Those with two are Expectant. Those with one are Latent. Salience is dynamic, so the classification needs re-running as the project context shifts.
"Stakeholder salience is the degree to which managers give priority to competing stakeholder claims." - Mitchell, Agle & Wood, Toward a Theory of Stakeholder Identification and Salience (1997)
The model fills a specific gap in stakeholder analysis. The Stakeholder Map is great for plotting everyone visually. The RACI Matrix is great for decision rights. The Salience Model is the priority lens that answers "if I can only call three stakeholders before the next meeting, who?"
Origin and Why It Works
Mitchell, Agle, and Wood developed the Salience Model in response to a specific problem in 1990s stakeholder theory. Earlier work (Freeman, 1984) defined stakeholders broadly as anyone affected by an organization's actions. That definition was inclusive but useless for prioritization: managers ended up with stakeholder lists of 30 or 40 names and no way to decide whose claim mattered most this quarter.
The 1997 paper solved this by introducing three observable attributes that combined to produce a salience score. The classification turned the abstract question "who is a stakeholder?" into the concrete one "who deserves attention right now, and why?" The model has been cited over 16,000 times in academic literature and is part of the Project Management Institute's standard stakeholder analysis toolkit. Its persistence is mostly due to the binary attribute design: yes/no questions force a clearer decision than 1-to-10 scoring scales.
The model is most useful in projects with many stakeholders and limited engagement bandwidth. Construction, public-sector projects, healthcare, and complex agency engagements are typical settings; for a 5-person internal initiative with three stakeholders, the framework adds overhead without much insight.
The 3 Attributes
The whole framework rests on three binary attributes. Each stakeholder either has the attribute or does not, and the combination determines the type.
Power. The stakeholder can influence the project's outcome, formally (org-chart authority, budget control, regulatory authority) or informally (coalition leadership, media reach, a coercive option). Power is "can they make us do something we would otherwise not do?"
Legitimacy. The stakeholder's claim is appropriate within the project's social, legal, or contractual context. Legitimacy does not require formal authority; a community affected by a planned development has legitimacy even without an org-chart title. Legitimacy is "do they have a reasonable basis to be heard?"
Urgency. The stakeholder's claim is time-sensitive or critical to them. Urgency has two parts: time pressure (regulatory deadline, contractual due date) and criticality (the issue matters intensely to the stakeholder). Urgency is "if we wait, does this become much worse?"
Salience Builder
Type a stakeholder name in each row, then toggle which of the three attributes each one holds: power (can influence outcomes), legitimacy (claim is appropriate), urgency (time-sensitive). The widget classifies each into one of seven types. Add rows below, copy the map when done.
The widget above is the version we hand to project teams that want a working salience map in 5 minutes. Add stakeholder names, toggle the three attributes, and the widget classifies each into one of the seven types with an engagement hint. Reset to the example to see a worked map.
The 7 Stakeholder Types
The combinations of three binary attributes produce eight possibilities; subtract the "no attributes" case (non-stakeholder) and you have seven actionable types. Mitchell, Agle, and Wood group them into three tiers: Latent (one attribute), Expectant (two), and Definitive (all three).
| Type | Attributes | Example | How to engage |
|---|---|---|---|
| Definitive | PowerLegitimacyUrgency | Project sponsor demanding a feature for a board deadline | Top priority. Immediate, sustained engagement; resolve the claim or escalate. |
| Dominant | PowerLegitimacy | Compliance team, executive committee, regulator without imminent deadline | Keep informed and aligned; they expect engagement and have means to insist. |
| Dangerous | PowerUrgency | Hostile press contact during a crisis; coercive lobbying group | Watch closely. Without legitimacy, may use coercion; address fast or risk disruption. |
| Dependent | LegitimacyUrgency | End-users awaiting a critical fix; community impacted by a project deadline | Their claim is valid and pressing but they lack power. Advocate or pair with a powerful ally. |
| Dormant | Power | Influential industry figure with no current claim against your project | Monitor. Can become Dominant or Dangerous quickly if their claim becomes legitimate or urgent. |
| Discretionary | Legitimacy | Long-term industry partner with general interest in the project | Engage selectively. No urgent need, but the relationship matters long-term. |
| Demanding | Urgency | Vocal social-media critic with no formal authority or obvious legitimacy | Acknowledge. Risk of becoming Dangerous if they gain power or legitimacy; do not ignore. |
The most common mistake at this stage is over-investing in Latent types and under-investing in Dangerous ones. Latent stakeholders matter, but they are watch-list items, not active engagements. Dangerous stakeholders (power plus urgency, no legitimacy) are the ones who blow up projects in the news cycle. Their lack of legitimacy means they are willing to use coercion. Their power and urgency mean they have the means and motivation to do it now.
How to Engage Each Stakeholder Type
Classification without an engagement plan is paperwork. Each of the seven types needs a different posture, cadence, and owner. The patterns below are what we run on agency and project work; adapt to your context but keep the principle that engagement effort should match salience.
Definitive (all three attributes). Top priority. The project sponsor or regulator with imminent claims gets immediate, sustained engagement. Named owner at executive level. Weekly or daily touchpoints. Resolve the claim or escalate; do not let it sit.
Dominant (power plus legitimacy). Keep informed and aligned. Compliance team, executive committee, anchor client. Monthly steering committee at minimum, plus immediate escalation when scope or risk changes. They expect to be engaged; missing them creates trust damage.
Dangerous (power plus urgency). Watch closely; address fast. Hostile press contact, lobbying group, coercive vendor. Defensive engagement: clear, prompt, on-record responses. The goal is to prevent escalation and avoid giving them legitimacy through public conflict.
Dependent (legitimacy plus urgency). Advocate for them. End users awaiting a fix, communities affected by a project deadline. Pair them with a powerful ally inside the organization who can act on their behalf. Without that ally, their valid claims go unmet.
Dormant, Discretionary, Demanding (one attribute each). Watch list. Quarterly check-in or trigger-based monitoring. The trigger is the missing attribute: a Dormant stakeholder who suddenly has a legitimate claim becomes Dominant; a Demanding stakeholder who picks up power becomes Dangerous. Track the trigger conditions explicitly.
"Stakeholders' salience emerges from their interactions, not from individual attributes alone." - Aaltonen and Kujala, A multilateral stakeholder salience approach (2010 / 2021 extension)
Aaltonen and Kujala's extension to the original model is worth absorbing. Stakeholders rarely act alone; coalitions form, alliances shift. A Dormant stakeholder paired with a Demanding one can produce the equivalent of a Dangerous coalition without either party crossing a threshold individually. Track the relationships between stakeholders, not just their individual scores.
"Gaining and maintaining the support and commitment of stakeholders requires a continuous process of engaging the right stakeholders at the right time." - Lynda Bourne, Stakeholder Relationship Management
Bourne's framing is the practical complement to Mitchell's theory. Salience tells you who; Bourne's continuous-engagement principle tells you that the work is never done. The model classifies; the engagement plan operationalizes.
Salience Model vs Other Stakeholder Frameworks
The Salience Model is one of several stakeholder frameworks, and it answers a specific question. The table below shows where each framework belongs in your stakeholder toolkit.
| Framework | Dimensions | Best for |
|---|---|---|
| Salience Model | Power, Legitimacy, Urgency (3 attributes, 7 types) | Identifying which stakeholders deserve priority right now, especially when claims compete |
| Stakeholder Map | 2x2 grid (typically Influence x Interest, or Power x Interest) | Visual planning across all stakeholders at a glance; setting engagement strategy by quadrant |
| Power-Interest Grid (Mendelow) | 2x2 grid (Power x Interest) | Quick segmentation into Manage Closely / Keep Informed / Keep Satisfied / Monitor |
| RACI Matrix | Responsible / Accountable / Consulted / Informed | Defining who does what on a project; clarifying decision rights, not stakeholder priority |
| Stakeholder Onion (or Circle) | Concentric rings: core team, project, organization, external | Mapping proximity to the work; useful for communication frequency planning |
The pragmatic stack we recommend works in three steps. Use the Stakeholder Map first to identify everyone visually. Then run the Salience Model to set priority among them. Then use a RACI matrix to assign decision rights on the engagement plan. Three frameworks, three different questions answered.
How to Apply the Salience Model in 5 Steps
The mechanics are straightforward; the discipline is in keeping the attributes binary and re-running the model as the project changes. Five steps separate teams that get value from the framework from teams that produce a static slide nobody opens.
- List every stakeholder, not just the obvious ones Pull names from the project charter, the org chart, regulators with jurisdiction, vendors, customers affected, internal teams downstream. Aim for 15 to 25 names on the long list. The Salience Model will filter; the job at this stage is exhaustive identification.
- Score each on power, legitimacy, and urgency Mark each stakeholder yes/no on the three attributes. Power means they can influence the outcome (formally or informally). Legitimacy means their claim is appropriate within the project's social and legal context. Urgency means time sensitivity or critical importance to them.
- Classify into the 7 types Three attributes equal Definitive (top priority). Two equal Expectant (Dominant, Dangerous, or Dependent). One equals Latent (Dormant, Discretionary, or Demanding). Zero means non-stakeholder for now. The Salience Builder above does this classification automatically.
- Decide engagement strategy per type Definitive and Dominant get sustained, high-touch engagement. Dangerous get fast, defensive attention. Dependent get advocacy from a powerful ally. Latent types stay on a watch list with a trigger condition (what would push them up to Expectant?).
- Re-run the model when the project shifts Salience is dynamic. A public incident can convert a Dormant stakeholder into Dangerous overnight; a coalition can convert Demanding into Dominant. Re-run the classification at least once per project phase, plus after any major change in scope, regulation, or external context.
The fifth step (re-running the model) is the one most teams skip. Salience is dynamic by design: a public incident, a coalition forming, a new regulation, a vendor failure can all change the classification overnight. Calendar a quarterly re-run plus a trigger-based one whenever the project's context shifts materially.
Common Mistakes
The patterns below show up across teams that adopt the Salience Model and lose value within one or two project phases. Most are about treating the framework as a slide deck rather than an operating exercise.
- Confusing legitimacy with formal authority Legitimacy is whether the claim is appropriate within the project's social and legal context. It does not require an org-chart title. A community group affected by a planned facility has legitimacy even without formal authority; ignoring them produces Dependent stakeholders that escalate to Dangerous.
- Treating salience as static Salience changes. A regulator with no current claim is Dormant; the same regulator with a public incident on file is Definitive overnight. Run the classification as a quarterly or per-phase exercise, not a one-time mapping.
- Ignoring Demanding stakeholders Demanding stakeholders (urgency only) get dismissed because they lack power and legitimacy. Mistake: they are one coalition or one news cycle away from gaining either. Acknowledge them; the cheap response now prevents the expensive one later.
- Over-engineering the score Some teams turn the three yes/no attributes into 1-to-10 scales and weighted formulas. The model loses its bite when over-quantified. The yes/no version forces a clearer decision; binary attributes are the point of the framework.
- Skipping the engagement-action step Identifying Definitive and Dangerous stakeholders without writing down who owns the relationship and what the engagement cadence is leaves the work undone. Each Expectant or Definitive stakeholder needs a named owner and a defined touchpoint frequency.
- Using Salience without a complementary framework Salience tells you who matters most right now; it does not tell you what each person should DO on the project. Pair with a RACI matrix for decision rights and a Stakeholder Map for engagement strategy across the long tail. Salience is the priority lens, not the whole stakeholder system.
The biggest of these is treating salience as static. The whole point of the model is that the classification can change as the project unfolds; if your map is a one-time exercise from kickoff, you are managing yesterday's stakeholders. Re-run quarterly at minimum, and after every material context change.
What We Recommend
At Rock we run the Salience Model as a recurring 30-minute exercise pinned inside the project workspace. The output is a note with the seven-type classification. Each Definitive and Expectant stakeholder gets a named owner. Each Latent stakeholder gets a trigger condition (what would push them up the priority ladder). The classification updates at every phase gate, and tasks for the engagement plan live in the same workspace as the project work.
The reason for keeping the salience map inside the project workspace is the failure mode otherwise. Stakeholder maps that live in slide decks become decoration; they get reviewed at the start of the project and forgotten when the team is heads-down on delivery. A pinned note with the current map plus tracked tasks for each engagement keeps the model alive when it actually matters.
Pair this with the broader stakeholder toolkit. The Stakeholder Map handles visual planning. The RACI matrix handles decision rights. Our stakeholder communication guide covers the cadence of how you engage each priority tier.
Pin the salience map inside the project workspace. Rock combines chat, tasks, and notes in one workspace. One flat price, unlimited users. Get started for free.
