Chapter 16: Stakeholder Analysis - Building Support, Managing Tensions, and Strengthening Implementation

Video: Stakeholder Analysis: The Often-Ignored Tool That Makes Your Solution More Credible and Ethical

Learning Objectives

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

• define a stakeholder in relation to a specific decision;
• identify internal and external stakeholders;
• distinguish stakeholders who are affected from those who can influence the outcome;
• understand stakeholder interests, expectations, concerns, and sources of power;
• assess stakeholder power, interest, legitimacy, urgency, and likely response;
• recognise conflicts and dependencies among stakeholder groups;
• identify stakeholders who could support, delay, reshape, or stop a recommendation;
• consider stakeholders with limited formal power but significant exposure to the consequences;
• develop appropriate engagement strategies for different stakeholders;
• integrate stakeholder considerations into strategy, ethics, risk, change management, and implementation;
• present stakeholder analysis without reducing it to a list of names.

Why This Matters

A business decision rarely affects only the organisation making it. Consider a decision to automate part of an operation. The change could affect:

• customers;
• employees;
• managers;
• unions;
• suppliers;
• technology partners;
• investors;
• regulators;
• governments;
• communities.

Each stakeholder may interpret the decision differently.

·        Customers may expect faster service but worry about losing access to human support.

·        Employees may recognise the need for efficiency but fear job loss, increased surveillance, or significant changes in their roles.

·        Investors may support lower operating costs but question the investment's size and risk.

·        Technology providers may see a new commercial opportunity.

·        Regulators may focus on privacy, safety, fairness, or employment obligations.

·        Community leaders may worry about the local economic impact.

A strategy that appears attractive from the organisation's perspective may create resistance, delay, reputational damage, regulatory intervention, or implementation failure if these perspectives are ignored. Stakeholder Analysis helps teams understand:

• who can affect the strategy;
• who will be affected by it;
• what each stakeholder wants or fears;
• how stakeholders are likely to respond;
• where interests conflict;
• what support the organisation needs;
• how the strategy and implementation plan should change as a result.

Discover Your MAD Skills Principle

A stakeholder is not simply someone affected by the decision. A stakeholder may also influence whether the decision succeeds.

These two dimensions are related but different. Some stakeholders have substantial power but experience little direct impact. Others have very little formal power but may experience serious consequences. For example:

• an investor may have significant influence over an automation decision, but experience limited direct disruption;
• a frontline employee may have little formal authority but face a major change in job responsibilities;
• a regulator may not use the service but can determine whether the model is legally acceptable;
• customers may have limited individual power but create substantial collective pressure through purchasing decisions, reviews, complaints, or social media.

A strong stakeholder analysis considers both influence over the decision and impact of the decision. A useful stakeholder progression is Stakeholder → Interest or Concern → Influence and Impact → Likely Response → Required Engagement.

Where Stakeholder Analysis Fits

Stakeholder Analysis is useful whenever successful implementation depends on the decisions, support, behaviour, resources, or acceptance of other people or organisations. It is particularly important when cases involve:

• government;
• healthcare;
• education;
• not-for-profits;
• sustainability;
• infrastructure;
• organisational change;
• restructuring;
• mergers and acquisitions;
• automation;
• digital transformation;
• employee relations;
• community impact;
• Indigenous communities;
• regulation;
• partnerships;
• public trust;
• environmental consequences;
• ethical trade-offs.

Stakeholder Analysis can strengthen several parts of a case solution.

Analysis

It can reveal:

• competing objectives;
• sources of resistance;
• decision-making power;
• implementation dependencies;
• ethical concerns;
• communication needs;
• risks that may not appear in financial analysis.

Alternative Evaluation

Stakeholder implications can become decision criteria when comparing alternatives. For example:

• customer acceptance;
• employee impact;
• regulatory feasibility;
• community support;
• partner compatibility;
• reputational risk.

Recommendation Design

Stakeholder needs may change:

• the solution;
• timing;
• scale;
• operating model;
• customer experience;
• workforce plan;
• partnership model;
• risk-mitigation approach.

Implementation

Stakeholder analysis can determine:

• who must be involved;
• who owns each relationship;
• what should be communicated;
• when engagement should occur;
• which concerns require action;
• and how support or resistance will be monitored.

Stakeholder Analysis should not be added at the end of the case as a communication exercise. It should influence the strategy itself.

What Is a Stakeholder?

A stakeholder is a person, group, organisation, or institution that:

• can affect a decision;
• is affected by a decision;
• provides something the organisation needs;
• controls an important resource or approval;
• possesses a legitimate interest in the outcome;
• may influence implementation or long-term success.

The relevant stakeholders depend on the decision. A group may be important to the organisation generally but not central to the specific question in the case. Another group may become important only because of the proposed recommendation. For example, a technology regulator may not be central to the current business model but may become highly important if the organisation begins collecting sensitive customer data. Stakeholder identification should therefore begin with what decision are we analysing?

Identifying Stakeholders

Start by asking:

• Who is directly affected?
• Who is indirectly affected?
• Who makes the decision?
• Who can approve, reject, delay, or reshape it?
• Who provides funding, knowledge, technology, labour, access, or legitimacy?
• Who must change their behaviour?
• Who will implement the recommendation?
• Who could resist it?
• Who could advocate for it?
• Who controls an important relationship or resource?
• Who carries the greatest risk?
• Who may experience unintended consequences?
• Who is not represented in the current decision-making process?
• Who becomes important if the strategy changes?

Internal Stakeholders

Internal stakeholders may include:

• employees;
• managers;
• executives;
• owners;
• board members;
• shareholders;
• departments;
• project teams;
• employee resource groups;
• unions or employee representatives.

External Stakeholders

External stakeholders may include:

• customers;
• users;
• suppliers;
• distributors;
• partners;
• investors;
• lenders;
• governments;
• regulators;
• communities;
• Indigenous groups;
• not-for-profit organisations;
• industry associations;
• media;
• advocacy groups;
• competitors;
• educational institutions;
• the natural environment as represented through affected communities, regulation, or environmental analysis.

Primary and Secondary Stakeholders

Primary stakeholders have a direct relationship with the organisation or decision. Examples might include:

• employees;
• customers;
• suppliers;
• owners;
• implementation partners.

Secondary stakeholders may influence or be affected indirectly by the decision. Examples might include:

• media;
• advocacy organisations;
• industry groups;
• local communities;
• public-interest organisations.

This distinction can help organise the analysis, but it must not automatically determine importance. A secondary stakeholder may possess considerable influence or raise a legitimate ethical concern.

Move Beyond Stakeholder Labels

"Employees" is usually too broad to function as a useful stakeholder category. Different employee groups may experience the same decision differently. An automation initiative could affect:

• frontline employees whose tasks will change;
• employees whose positions may be eliminated;
• managers who must implement new processes;
• technical employees who will maintain the system;
• human-resource employees responsible for redeployment or layoffs;
• union representatives negotiating the transition.

Similarly, "customers" may include:

• current customers;
• high-value customers;
• vulnerable customers;
• digital-first customers;
• customers requiring accessibility support;
• potential customers;
• customers in different geographic markets.

A strong analysis segments stakeholders when their:

• interests;
• influence;
• exposure;
• likely response;
• engagement needs

are materially different.

Understanding Stakeholder Interests

Stakeholder interests explain what each group wants, values, needs, or seeks to protect. Possible interests include:

• financial return;
• employment;
• job security;
• wages;
• safety;
• affordability;
• service quality;
• convenience;
• privacy;
• access;
• reliability;
• environmental protection;
• local economic development;
• regulatory compliance;
• organisational stability;
• professional identity;
• reputation;
• autonomy;
• fairness;
• transparency;
• influence over decisions.

Ask:

• What outcome does this stakeholder want?
• What problem are they trying to solve?
• What do they value?
• What might they gain?
• What might they lose?
• What obligation does the organisation have toward them?
• How might they define success?
• What would make the recommendation unacceptable?
• What information would they need to judge the decision?

Don't assume that all members of a stakeholder group want the same thing. Interests may also change over time as more information becomes available or implementation begins.

Understanding Stakeholder Power

Power is the stakeholder's ability to influence the decision or its implementation. Sources of power may include:

Formal Authority

The ability to approve, reject, regulate, direct, or govern. Examples include:

• boards;
• executives;
• regulators;
• elected officials;
• senior managers.

Resource Power

Control over something the organisation needs. Examples include:

• funding;
• labour;
• technology;
• information;
• property;
• distribution;
• licences;
• supplies;
• customer access.

Economic Power

The ability to affect revenue, cost, investment, or financial stability. Examples include:

• major customers;
• investors;
• lenders;
• large suppliers;
• purchasing groups.

Expertise Power

Specialised knowledge or credibility required for the decision. Examples include:

• technical employees;
• healthcare professionals;
• engineers;
• legal experts;
• academics;
• community knowledge holders.

Relationship Power

Access to influential people, organisations, or communities.

Collective Power

Limited individual power can become significant when stakeholders act together. Examples include:

• employees;
• consumers;
• residents;
• professional groups;
• unions;
• community coalitions;
• online communities.

Reputational Power

The ability to influence public trust, media attention, or the organisation's legitimacy. Power is not fixed. A low-power stakeholder can become influential through:

• organising;
• coalition building;
• public attention;
• legal action;
• political advocacy;
• media coverage;
• consumer behaviour;
• regulation changes.

Interest Is Not the Same as Impact

A stakeholder may have a high interest because the issue matters deeply to them. Impact asks how significantly the decision changes their situation. These are related but distinct. For example:

• a community advocacy group may have high interest but limited direct exposure;
• an employee may be highly affected but initially have little information or expressed interest;
• a senior executive may have high decision-making power but experience little personal impact;
• a vulnerable customer may experience substantial harm but have limited influence.

A rigorous analysis asks:

• How much does the stakeholder care?
• How much influence do they possess?
• How significantly will they be affected?
• How legitimate and urgent are their concerns?

Stakeholder Mapping

A Power–Interest Matrix is one of the simplest ways to organise stakeholders.

	Lower interest	Higher interest
Higher power	Keep satisfied	Manage closely
Lower power	Monitor appropriately	Keep informed and involve where meaningful

High Power, High Interest: Manage Closely

These stakeholders may have both the motivation and ability to influence the decision. Engagement may include:

• early consultation;
• participation in decision-making;
• regular Communication and negotiation;
• governance roles;
• and direct issue resolution.

High Power, Lower Interest: Keep Satisfied

These stakeholders may not focus on the issue unless their interests are threatened. Engagement may include:

• concise updates;
• targeted consultation;
• compliance assurance;
• risk escalation;
• maintaining confidence.

Lower Power, High Interest: Keep Informed and Involve

These stakeholders may experience significant consequences even if they cannot formally control the decision. Engagement may include:

• accessible consultation;
• feedback mechanisms;
• representation;
• co-design;
• support;
• escalation routes.

Lower Power, Lower Interest: Monitor Appropriately

These stakeholders may require less intensive engagement, but they should not be ignored automatically. Interest or power may change as the decision develops.

The Limits of a Power–Interest Map

The Power–Interest Matrix is useful for prioritising engagement, but it has limitations. A stakeholder with low power may still:

• possess a legitimate claim;
• face serious harm;
• have legal rights;
• represent an ethical obligation;
• possess knowledge the organisation needs;
• gain collective power later.

The matrix should not become a tool for deciding whose interests don't matter. Three additional questions should supplement it:

·        Legitimacy: Does the stakeholder have a valid legal, ethical, contractual, social, or practical claim?

·        Urgency: Does the issue require immediate attention because of timing, seriousness, or irreversible consequences?

·        Impact: How significantly will the stakeholder be affected if the recommendation proceeds?

A stakeholder may have low formal power but high legitimacy, urgency, and exposure. That stakeholder deserves serious consideration.

Stakeholder Salience

Stakeholder salience considers three characteristics:

• Power: Can the stakeholder influence the organisation or decision?
• Legitimacy: Does the stakeholder have a valid claim?
• Urgency: Does the claim require timely attention?

This lens helps teams recognise that stakeholder priority is not determined by influence alone. For example, a small group of customers with accessibility needs may account for a limited share of revenue and have little direct bargaining power. However, their concerns may have: 

• legal legitimacy;
• ethical significance;
• reputational implications;
• urgent consequences if a new digital service excludes them.

A strategy that engages only the most powerful stakeholders may still be unethical, illegal, or strategically shortsighted.

Understanding Stakeholder Position

Stakeholders may respond to a recommendation in different ways. A simple response spectrum includes:

• active resistance;
• passive resistance;
• neutral or undecided;
• passive support;
• active advocacy.

The team should assess both the current and required positions for implementation. For example:

Stakeholder	Current position	Required position
Executive sponsor	Supportive	Active champion
Frontline managers	Uncertain	Active implementers
Employees	Concerned	Willing participants
Union	Cautious	Negotiated acceptance
Customers	Unaware	Informed adopters
Regulator	Neutral	Satisfied that requirements are met

The gap between current and required support helps determine the engagement strategy.

What Do We Need from Each Stakeholder?

This is one of the most important questions in practical stakeholder analysis. The organisation may need a stakeholder to provide:

• approval;
• funding;
• information;
• expertise;
• participation;
• adoption;
• behaviour change;
• access;
• credibility;
• resources;
• partnership;
• compliance;
• public support;
• patience;
• feedback.

The engagement plan should be built around the required behaviour or contribution. For example:

Stakeholder	What they need	What we need from them
Employees	Role clarity, training, security, voice	Adoption and operational feedback
Customers	Reliable service, transparency, support	Trial, purchase, feedback, and retention
Investor	Credible economics and risk controls	Funding and patience during pilot
Regulator	Compliance evidence and accountability	Approval and continued operating permission
Supplier	Demand visibility and fair terms	Reliable capacity and quality
Community	Local benefits and mitigation of harm	Trust, feedback, and social acceptance

This moves the analysis from observation to implementation.

Stakeholder Conflict and Trade-Offs

Stakeholders don't always want the same thing. For example:

• shareholders may seek higher returns;
• employees may seek job security and manageable workloads;
• customers may seek lower prices and better service;
• suppliers may seek higher prices and longer contracts;
• governments may prioritise public outcomes;
• communities may seek local employment and environmental protection;
• managers may seek flexibility and control;
• partners may seek access to customers or data.

These priorities can conflict. A strategy cannot always maximise every stakeholder outcome simultaneously. The team must identify:

• where the conflicts exist;
• which interests are non-negotiable;
• who bears the costs and receives the benefits;
• whether the trade-off is fair;
• how negative effects can be reduced;
• what compensation or support may be appropriate;
• how the decision will be explained.

Example: Automation

Automation may create:

Organisational Benefits

• lower cost;
• greater speed;
• fewer errors;
• improved scalability;
• more consistent service.

Employee Concerns

• job loss;
• role uncertainty;
• increased monitoring;
• loss of autonomy;
• retraining demands;
• workload during transition.

Customer Benefits and Risks

• faster service;
• continuous access;
• reduced prices;
• loss of human support;
• accessibility barriers;
• privacy concerns;
• algorithmic errors.

A strong recommendation would not simply say, "Communicate the benefits of automation." It might:

• involve employees in process redesign;
• commit to redeployment where feasible;
• provide paid retraining;
• phase implementation;
• preserve human escalation;
• establish privacy and fairness controls;
• monitor customer outcomes;
• explain which roles and decisions remain human.

The strategy itself changes because of stakeholder analysis.

Ethics and Fairness

Stakeholder Analysis is not only about overcoming resistance. It also helps evaluate whether the recommendation treats affected groups responsibly. Two forms of fairness are especially useful.

Distributive Fairness

How are the benefits, costs, risks, and burdens distributed? Ask:

• Who gains?
• Who pays?
• Who carries the risk?
• Who may be harmed?
• Are the benefits concentrated while the costs are imposed on others?
• Are vulnerable groups disproportionately affected?
• Is compensation or mitigation appropriate?

Procedural Fairness

Was the decision-making process fair? Ask:

• Were affected stakeholders heard?
• Was relevant information shared?
• Were decision criteria transparent?
• Was feedback genuinely considered?
• Were stakeholders given a meaningful opportunity to participate?
• Is there an appeal or complaint process?
• Are decisions applied consistently?

People may be more willing to accept a difficult outcome when the process is transparent, respectful, and fair. Stakeholder engagement should not be used to create the appearance of consultation after the decision has already been made.

Designing the Engagement Strategy

Stakeholder engagement can take several forms.

Inform

Provide clear and timely information. Use when stakeholders need awareness but are not expected to shape the decision significantly. Methods may include:

• announcements;
• briefings;
• reports;
• frequently asked questions;
• dashboards;
• public updates.

Consult

Ask stakeholders for information, concerns, or feedback. Methods may include:

• interviews;
• surveys;
• focus groups;
• town halls;
• public consultations;
• advisory panels;
• feedback sessions.

Consultation should explain how feedback will be used.

Involve

Include stakeholders in design, planning, testing, or problem-solving. Methods may include:

• workshops;
• employee design teams;
• pilot groups;
• user testing;
• working groups;
• community advisory committees.

Collaborate

Share substantial responsibility for developing the solution. Methods may include:

• joint planning;
• partnerships;
• co-design;
• shared governance;
• and formal working arrangements.

Negotiate

Reach agreement where interests, rights, resources, or responsibilities differ. Methods may include:

• collective bargaining;
• contract negotiation;
• partnership agreements;
• community-benefit agreements;
• and regulatory commitments.

Empower

Give stakeholders formal authority or decision-making power over part of the process. This may be appropriate where stakeholders possess important rights, expertise, legitimacy, or direct responsibility. The appropriate level of engagement depends on:

• stakeholder power;
• impact;
• legitimacy;
• urgency;
• knowledge;
• implementation role;
• the reversibility of the decision.

Communication Is Not the Same as Engagement

Communication is one part of stakeholder engagement. Sending an email doesn't mean the stakeholder has been engaged. Engagement may require:

• listening;
• negotiation;
• participation;
• co-design;
• support;
• changes to the recommendation;
• ongoing relationship management;
• accountability.

The stronger question is not: "How will we communicate the decision?" It is: "How will this stakeholder influence the decision, and how will the organisation respond to their interests and concerns?"

Building a Stakeholder Plan

A practical stakeholder plan may include:

Stakeholder	Interest or concern	Power and impact	Current position	Required contribution	Engagement approach	Owner
Frontline employees	Job security and workload	Medium power, high impact	Concerned	Adoption and feedback	Involve in design; training and transition support	Operations and HR
Customers	Price, reliability, human support	High collective power, high impact	Uncertain	Trial and continued use	Testing, transparent communication, support options	Customer lead
Regulator	Privacy, safety, compliance	High power, moderate impact	Neutral	Approval	Early consultation and compliance evidence	Legal lead
Technology partner	Contract value and implementation	Medium power, high involvement	Supportive	Reliable delivery	Joint governance and service standards	Technology lead
Investors	Return, cost, risk	High power, lower direct impact	Supportive	Funding and patience	Milestone reporting and risk controls	CFO

The plan should also specify:

• timing;
• message;
• decision or input required;
• major concerns;
• mitigation;
• feedback channel;
• escalation path;
• success measure.

Stakeholder Engagement Across Implementation

Engagement needs change over time.

Before the Decision

The organisation may need to:

• understand interests;
• gather evidence;
• identify risks;
• consult affected groups;
• assess support;
• and test alternatives.

During Design

The organisation may need to:

• involve users;
• negotiate responsibilities;
• co-design processes;
• establish protections;
• define success measures;
• and clarify roles.

During the Pilot

The organisation may need to:

• support adoption;
• monitor experience;
• gather feedback;
• resolve problems;
• and adjust the solution.

During Expansion

The organisation may need to:

• communicate results;
• reinforce new behaviours;
• revise agreements;
• scale support;
• and monitor unintended consequences.

After Implementation

The organisation may need to:

• maintain relationships;
• report outcomes;
• respond to concerns;
• update safeguards;
• and remain accountable.

Stakeholder engagement is an ongoing process, not a launch announcement.

A Worked Example

Return to the regional meal-kit company examined in Chapters 11–15. The company is considering a partnership-led pilot in a new Canadian city. The proposed model includes:

• local ingredient sourcing;
• a shared commercial kitchen;
• a regional delivery provider;
• targeted digital marketing;
• employer partnerships;
• a small local operations team.

Step 1: Identify the Stakeholders

The team identifies:

• current employees;
• the new local operations team;
• local food producers;
• the shared-kitchen operator;
• the delivery partner;
• pilot customers;
• employer partners;
• existing customers in the home market;
• investors;
• municipal regulators;
• food-safety regulators;
• and the local community.

Step 2: Understand Interests and Concerns

Current Employees

·        Interests: Organisational growth, job stability, manageable workloads, and career opportunities.

·        Concerns: Expansion may create additional work or divert attention from the home market.

·        What the organisation needs: Knowledge transfer, support for pilot design, and continuity in the existing operation.

Local Food Producers

·        Interests: Predictable orders, fair prices, timely payment, and recognition of their local products.

·        Concerns: Uncertain volumes, changing demand, and contracts favouring the meal-kit company.

·        What the organisation needs: Reliable supply, product quality, regional knowledge, and collaboration on menu development.

Shared-Kitchen Operator

·        Interests: Stable facility use, predictable scheduling, and a profitable agreement.

·        Concerns: Operational disruption, food-safety responsibility, and demand volatility.

·        What the organisation needs: Production capacity, compliance, quality, and scheduling flexibility.

Delivery Partner

1.      Interests: Sufficient delivery volume and efficient routes.

2.      Concerns: Last-minute information, failed deliveries, and unrealistic service expectations.

3.      What the organisation needs: Reliable and traceable delivery.

Pilot Customers

·        Interests: Convenience, freshness, local ingredients, transparent pricing, and dependable delivery.

·        Concerns: Subscription commitment, food quality, missed deliveries, and weak customer support.

·        What the organisation needs: Trial, purchase, feedback, and retention.

Existing Customers

·        Interests: Continued service quality in the home market.

·        Concerns: Expansion may reduce attention, product quality, or delivery reliability.

·        What the organisation needs: Continued trust and retention.

Investors

·        Interests: Growth, credible economics, controlled investment, and scalable learning.

·        Concerns: Expansion risk, cash requirements, and the recurrence of existing operational problems.

·        What the organisation needs: Pilot funding and patience until evidence is available.

Regulators

·        Interests: Food safety, employment compliance, licensing, and consumer protection.

·        Concerns: Inadequate systems, unclear accountability, or non-compliance.

·        What the organisation needs: Approval and continued permission to operate.

Local Community

·        Interests: Local employment, support for regional producers, responsible waste management, and economic benefit.

·        Concerns: Temporary employment, excessive packaging, food waste, traffic, and the use of "local" as unsupported marketing.

·        What the organisation needs: Trust, community knowledge, and local legitimacy.

Step 3: Map Power and Impact

Stakeholder	Influence over pilot	Impact from pilot	Priority
Investors	High	Moderate	Manage closely
Regulators	High	Moderate	Manage closely
Shared-kitchen partner	High	High	Manage closely
Delivery partner	High	High	Manage closely
Current employees	Medium	High	Involve actively
Local producers	Medium collectively	High	Collaborate
Pilot customers	High collectively	High	Test and involve
Existing customers	Medium collectively	Moderate	Keep informed and monitor
Local community	Variable	Moderate	Consult and monitor

The table doesn't determine whose interests matter ethically. It helps determine the type and intensity of engagement.

Step 4: Identify Stakeholder Tensions

Several tensions emerge:

Investors and Employees

·        Investors may prefer a low-cost pilot using existing staff. Employees may already be at capacity.

·        Response: Create a dedicated pilot team and limit the responsibilities placed on the home-market operation.

Customers and Delivery Partner

·        Customers expect narrow delivery windows. The delivery partner needs route density and scheduling flexibility.

·        Response: Start in a limited delivery zone, establish order cut-off times, and test time-window options.

Company and Local Producers

·        The company wants flexible order volumes. Producers need predictability.

·        Response: Use minimum-volume commitments, rolling forecasts, and a staged supplier model.

Growth and Existing Customers

·        The company wants to expand, but existing customers expect service quality to remain stable.

·        Response: Establish home-market service thresholds that must be maintained during the pilot.

Sustainability Promise and Packaging

·        The local-food value proposition may be weakened by excessive single-use packaging.

·        Response: Test lower-waste packaging and report on food waste and packaging measures.

Step 5: Design the Engagement Plan

·        Employees

o   involve representatives in pilot-process design;

o   clarify workload and responsibilities;

o   provide temporary backfill where necessary;

o   explain career opportunities;

o   create a feedback and escalation channel.

·        Producers

o   involve suppliers in menu and volume planning;

o   establish fair contract terms;

o   share rolling forecasts;

o define product-quality expectations.

·        Partners

o   establish joint governance;

o   define service standards;

o   clarify data ownership;

o   create issue-escalation procedures;

o hold regular operational reviews.

·        Customers

o   conduct pre-launch testing;

o   explain pricing and subscription terms clearly;

o   provide real-time delivery information;

o   preserve human support for exceptions;

o use feedback to refine the model.

·        Regulators

o   engage before launch;

o   confirm licensing and food-safety requirements;

o   document accountability;

o   provide evidence of compliance.

·        Investors

o   communicate investment limits;

o   report progress through defined milestones;

o   connect further funding to customer, operational, and financial evidence.

Step 6: Change the Recommendation

Stakeholder Analysis changes the implementation plan. The team now recommends:

1. a geographically limited pilot;
2. dedicated pilot staffing rather than relying only on current employees;
3. minimum-volume and forecasting arrangements with producers;
4. formal service-level agreements with kitchen and delivery partners;
5. pre-launch consultation with regulators;
6. customer co-design and testing;
7. protection of service standards in the existing market; and
8. stakeholder-specific success measures.

The recommendation has become more credible because it reflects the relationships necessary for it to work.

Stakeholder Analysis Is Not a Popularity Contest

A strategy doesn't need every stakeholder to agree with every decision. Some conflicts cannot be eliminated. The objective is to:

• understand the interests involved;
• identify legitimate claims;
• make informed trade-offs;
• reduce avoidable harm;
• involve the right stakeholders;
• establish fair processes;
• build sufficient support;
• and manage resistance responsibly.

The organisation may still make a difficult decision. Stakeholder Analysis helps ensure that it understands:

• who bears the consequences;
• what protections are required;
• what support is necessary;
• and how the decision should be implemented.

Stakeholder Analysis Is Not the Recommendation

Identifying stakeholders doesn't determine the strategy. A complete process is:

1. define the decision;
2. identify the relevant stakeholders;
3. segment broad stakeholder groups where necessary;
4. understand interests, concerns, and expectations;
5. assess power, interest, impact, legitimacy, and urgency;
6. determine current and required positions;
7. identify conflicts and dependencies;
8. decide how stakeholder considerations should affect the solution;
9. design the engagement plan;
10. assign relationship owners;
11. integrate engagement into implementation;
12. monitor stakeholder response and emerging concerns.

Stakeholder Analysis strengthens strategic judgement. It doesn't replace ethical reasoning, financial analysis, legal review, customer analysis, or implementation planning.

Measuring Stakeholder Engagement

Engagement should be measured by more than the number of meetings held.

Awareness Measures

• understanding of the change;
• message reach;
• attendance;
• and communication clarity.

Participation Measures

• consultation response;
• involvement in design;
• representation;
• and quality of feedback.

Support Measures

• stakeholder position;
• approval;
• advocacy;
• willingness to participate;
• and partner commitment.

Adoption Measures

• employee use;
• customer uptake;
• partner performance;
• and behavioural change.

Relationship Measures

• trust;
• satisfaction;
• complaint volume;
• issue-resolution time;
• and agreement compliance.

Outcome Measures

• employee retention;
• customer retention;
• community benefit;
• regulatory compliance;
• supplier reliability;
• and distribution of costs and benefits.

The right measure depends on what the organisation needs from the stakeholder.

Winning the Room: Presenting Stakeholder Analysis

A slide containing a ring of stakeholder names around the company rarely provides useful insight. It tells the judges who exists. It doesn't tell them what matters.

Lead with the Stakeholder Challenge

For example, the pilot depends on local producers and delivery partners, but the pilot's need for predictable volume conflicts with the company's need to limit early-stage risk.

Prioritise the Stakeholders

Focus on the stakeholders who:

• can significantly affect success;
• experience the greatest impact;
• possess legitimate or urgent concerns;
• require a behaviour change.

Show the Tension

Explain:

• what the organisation wants;
• what the stakeholder wants;
• where those interests conflict;
• why the conflict matters.

Present the Response

For example: We recommend rolling volume forecasts and minimum purchasing commitments to give producers greater predictability while preserving flexibility during the pilot.

Connect Engagement to Implementation

Explain:

• when engagement occurs;
• who owns the relationship;
• what contribution is required;
• what support or protection is provided;
• and how success will be measured.

The analytical chain becomes: Stakeholder Interest → Tension or Dependency → Implementation Risk → Engagement Response.

Coach's Lens

One of the biggest mistakes teams make is treating stakeholders as a list. They say, "Our stakeholders are customers, employees, suppliers, the government, and shareholders." Fine, but what does that tell us? The stronger questions are:

• What does each stakeholder need?
• What do they fear?
• What do we need from them?
• How can they affect implementation?
• How will the recommendation affect them?
• What must we do differently because of that analysis?

I often ask, "Who could stop this recommendation from succeeding?" I also ask who could be seriously affected and may not have the power to stop it. The first question improves implementation. The second improves the recommendation's ethics and credibility. 

Common Mistakes

·        Treating Stakeholders as a List: Naming stakeholders doesn't reveal their relevance. Explain each stakeholder's interests, concerns, influence, impact, and required contributions.

·        Treating All Stakeholders Equally: Different stakeholders require different levels and forms of engagement; prioritise based on power, interest, impact, legitimacy, urgency, and implementation role. 

·        Focusing Only on Powerful Stakeholders: Low-power stakeholders may experience substantial harm or possess legitimate rights. Consider influence and impact separately.

·        Treating Broad Groups as Homogeneous: Not all employees, customers, suppliers, or communities share the same interests. Segment groups when their exposure, influence, or concerns differ materially.

·        Assuming Stakeholder Interests: Teams may rely on stereotypes rather than evidence. Use case facts, interviews, research, prior behaviour, contracts, surveys, or explicit assumptions.

·        Ignoring Conflicting Interests: Stakeholder priorities can directly conflict. State the tension and explain how the strategy balances, mitigates, or makes the trade-off.

·        Treating Resistance as Irrational: Resistance may reflect legitimate concerns about risk, fairness, workload, trust, or past failures. Understand the source before designing the response.

·        Using Communication in the Entire Engagement Plan: Informing stakeholders doesn't mean involving or supporting them. Determine whether the stakeholder should be informed, consulted, involved, collaborated with, negotiated with, or empowered.

·        Consulting After the Decision Is Final. Late consultation may appear performative and damage trust. Engage stakeholders early enough for their input to influence the decision.

·        Identifying Without Acting: Knowing that a stakeholder matters is not enough. Specify the engagement approach, owner, timing, support, and measure.

·        Ignoring Collective Power: Individuals with limited influence may become powerful when organised. Consider unions, coalitions, communities, advocacy groups, and public opinion.

·        Forgetting Stakeholder Change Over Time: Power, interest, and support may shift during implementation. Reassess the stakeholder map at key milestones.

·        Trying to Make Everyone Happy: Some stakeholder conflicts cannot be eliminated. Make transparent, evidence-based, and ethically defensible trade-offs.

·        Presenting the Entire Map: A complicated matrix may distract from the strategic issue. Present the stakeholders, tensions, and actions that materially affect the recommendation.

MAD Skills Drill

Choose a recommendation from a previous case.

Step 1: Define the Decision

State clearly:

• what the organisation proposes to do;
• where;
• when;
• what will change.

Step 2: Identify the Stakeholders

Identify at least:

• two internal stakeholders;
• two external stakeholders;
• one stakeholder with high power;
• one stakeholder likely to experience significant impact;
• one stakeholder whose perspective may be overlooked.

Step 3: Understand Each Stakeholder

For every stakeholder, identify:

• what they want;
• what they value;
• what they fear;
• what they may gain;
• what they may lose;
• what the organisation needs from them.

Step 4: Assess Priority

Evaluate each stakeholder's:

• power;
• interest;
• impact;
• legitimacy;
• urgency;
• current position.

Step 5: Identify the Critical Stakeholders

·        Answer: Who could stop, delay, or significantly reshape the recommendation?

·        Then answer: Who could experience significant consequences without having much influence?

Both groups deserve attention.

Step 6: Identify Conflicts

Select one important stakeholder tension.

Explain:

• what each stakeholder wants;
• why the interests conflict;
• which outcomes are non-negotiable;
• what trade-off may be required;
• how negative effects could be reduced.

Step 7: Design the Engagement Plan

For each priority stakeholder, determine:

• what contribution or behaviour is required;
• whether to inform, consult, involve, collaborate, negotiate, or empower;
• who owns the relationship;
• when engagement begins;
• what support or mitigation is provided;
• how the response will be measured.

Step 8: Change the Recommendation

Identify at least one way the stakeholder analysis should alter:

• the solution;
• timing;
• pilot;
• implementation;
• workforce plan;
• communication;
• partnership structure;
• risk mitigation;
• performance measures.

If the analysis doesn't influence anything, it may not be strategically relevant.

Step 9: Deliver the Insight

Prepare a 60-second explanation answering:

1. Which stakeholder relationship matters most?
2. What does that stakeholder want or fear?
3. What does the organisation need from them?
4. What conflict or implementation risk exists?
5. How should the organisation respond?

Don't read a list of stakeholders. Explain the relationship that changed the strategy.

Chapter Summary

Stakeholder Analysis helps case teams understand the individuals, groups, organisations, and institutions that influence or are influenced by a decision. Its value doesn't come from listing stakeholders. It comes from determining:

• what each stakeholder values;
• how the recommendation affects them;
• how much influence they possess;
• whether their concerns are legitimate or urgent;
• how they are likely to respond;
• what the organisation needs from them;
• where stakeholder interests conflict;
• how engagement should shape the solution and implementation.

Strong Stakeholder Analysis follows this progression: Who matters? → What do they need or fear? → How can they affect success? → How will the decision affect them? → How should we engage them? Stakeholder power is important, but it is not the only consideration. Stakeholders with limited formal influence may still experience significant consequences, possess legitimate rights, or hold knowledge the organisation needs. A weak stakeholder analysis identifies stakeholders. A strong stakeholder analysis changes how the recommendation is designed and implemented.

Key Takeaways

✓ Stakeholders include individuals and groups that can affect a decision, are affected by it, provide essential resources, possess legitimate claims, or influence implementation.

✓ Begin with the specific decision because stakeholder relevance changes with the strategy.

✓ Consider both internal and external stakeholders.

✓ Segment broad groups when their interests, influence, impact, or engagement needs differ.

✓ Understand what each stakeholder wants, values, fears, may gain, and may lose.

✓ Assess power, interest, impact, legitimacy, urgency, and likely response.

✓ Power–Interest mapping helps prioritise engagement but should not be used to dismiss low-power stakeholders.

✓ Stakeholders with limited power may still experience serious harm, possess legal or ethical rights, or gain collective influence.

✓ Determine the stakeholder's current position and the position or contribution required for implementation.

✓ Ask what the organisation needs from each stakeholder, not only what the stakeholder wants.

✓ Recognise conflicts among stakeholders and explain how the strategy manages trade-offs.

✓ Evaluate both distributive fairness who receives benefits and bears costs and procedural fairness how the decision is made.

✓ Choose an appropriate engagement approach: inform, consult, involve, collaborate, negotiate, or empower.

✓ Communication is only one part of stakeholder engagement.

✓ Stakeholder engagement should begin early enough to influence the decision and continue throughout implementation.

✓ Assign an owner, timing, action, and measure for every priority stakeholder relationship.

✓ Use stakeholder analysis to change the recommendation, implementation plan, protections, measures, or engagement approach.

✓ In the presentation, focus on the stakeholder tension or dependency that materially affects the strategy, not on presenting a list of names.

Looking Ahead

Stakeholder Analysis completes this section's progression from understanding the external environment and industry to examining the organisation, its capabilities, its business model, and its relationships. Together, these tools help case teams answer:

• What is changing around the organisation?
• What competitive pressures shape the decision?
• Where does the organisation create value?
• Which capabilities can help it win?
• How does its business model fit together?
• Is the organisation aligned to execute?
• Who must support or will be affected by the strategy?

The next part of the manual moves from understanding the situation to using those insights to develop, evaluate, and select strategic solutions.