Stakeholder Analysis - Building Support, Managing Tensions, and Strengthening Implementation

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

“A strategy is implemented by people. If you don't understand the people who can influence the outcome, you don't fully understand the strategy.”

Learning Objectives

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

• explain the purpose of stakeholder analysis;

• identify the stakeholders affected by or able to influence a decision;

• distinguish between stakeholder interest and stakeholder influence;

• understand different stakeholder perspectives and priorities;

• identify potential sources of support and resistance;

• assess stakeholder relationships and dependencies;

• prioritise stakeholders rather than treating everyone equally;

• develop strategies for building support and managing resistance;

• incorporate stakeholder considerations into implementation planning;

• use stakeholder analysis to strengthen recommendations and reduce execution risk.

Why This Matters

A strategy may look compelling from the organisation's perspective. But organisations don't implement strategies by themselves. People do.

• Employees may have to change their behaviour.
• Customers may have to change their purchasing habits.
• Suppliers may have to change how they operate.
• Managers may have to give up control.
• Investors may have to accept a different risk profile.
• Regulators may have to approve a change.
• Partners may have to invest resources.
• Communities may respond positively or negatively.

A recommendation can therefore fail even when the underlying strategy is sound. The problem may not be the strategy. The problem may be that the people who matter were not considered. Stakeholder analysis helps answer: Who can influence this decision, who will be affected by it, and what do we need from them for the strategy to succeed?

Discover Your MAD Skills Principle

Don't try to make every stakeholder happy. Understand what matters to them, how much influence they have, and what you need from them to make the strategy work.

This distinction is important. Strong stakeholder analysis is not about pleasing everyone. Different stakeholders may have competing interests. For example:

• customers want lower prices

• employees want higher compensation

• shareholders want stronger returns

• suppliers want higher prices

• regulators want compliance

• communities want environmental protection

A strategy may not be able to maximise all of these interests simultaneously. The case solver's job is to understand the tensions and determine how they should influence the recommendation and implementation plan.

What Is a Stakeholder?

A stakeholder is an individual, group, or organisation that:

• can affect the organisation

• is affected by the organisation

• has an interest in the decision

• can influence implementation

• controls resources required for success

Stakeholders can be:

Internal

• employees

• managers

• executives

• owners

• board members

• shareholders

External

• customers

• suppliers

• partners

• competitors

• regulators

• governments

• communities

• advocacy groups

• investors

• lenders

Not every stakeholder has the same level of importance for every decision. That is why prioritisation matters.

Stakeholder Analysis Begins With the Decision

One of the most common mistakes is creating a generic stakeholder list. Instead, begin with the specific strategic decision.

• Ask: What are we trying to change?
• Then ask: Who can influence whether that change succeeds?

For example, if the recommendation is to launch a new digital platform, the relevant stakeholders might include:

• customers

• employees

• technology teams

• senior management

• IT vendors

• regulators

• investors

If the recommendation is to close several physical locations, the stakeholder landscape changes:

• employees

• local customers

• landlords

• suppliers

• communities

• investors

• local governments

The stakeholder analysis should therefore be decision-specific.

The Stakeholder Test

For each potential stakeholder, ask four questions:

1. Are they affected?

Will the decision change their:

• costs?

• benefits?

• responsibilities?

• risks?

• opportunities?

• access?

• behaviour?

2. Can they influence the outcome?

Can they:

• approve?

• block?

• delay?

• fund?

• support?

• promote?

• implement?

3. What do they want?

What are their:

• objectives?

• concerns?

• incentives?

• priorities?

• constraints?

4. What do we need from them?

Do we need:

• approval?

• cooperation?

• investment?

• behaviour change?

• information?

• resources?

• advocacy?

These questions move stakeholder analysis beyond simply identifying names.

Interest and Influence

Two of the most useful dimensions for prioritising stakeholders are:

• Interest: how much the stakeholder cares about the decision.
• Influence: how much ability the stakeholder has to affect the outcome.

This creates a simple stakeholder map.

	High Influence	Low Influence
High Interest	Manage closely	Keep informed
Low Interest	Keep satisfied	Monitor

The purpose is not to label people permanently. Stakeholder positions can change as the strategy develops. A stakeholder with low interest today may become highly interested when implementation affects them directly.

High Influence / High Interest

These stakeholders deserve close attention. They may include:

• senior executives

• major investors

• key customers

• critical partners

• regulators

• employees responsible for implementation 

They may have both the motivation and the ability to influence the outcome.

Approach

• engage early

• understand concerns

• involve where appropriate

• communicate clearly

• address major objections

• establish accountability

The objective is to build sufficient alignment for implementation.

High Influence / Low Interest

These stakeholders have the ability to affect the outcome but may not be deeply engaged. Examples could include:

• senior leaders focused on other priorities

• regulators with limited interest in the specific issue

• major partners who are not directly affected

Approach

Keep satisfied. Don't overwhelm them with unnecessary information. But make sure they understand:

• what is changing

• why it matters

• what you need from them

• when their involvement is required

Low Influence / High Interest

These stakeholders may care deeply but have limited direct decision-making power. Examples could include:

• employees affected by a restructuring

• local customers

• community groups

• frontline staff

Their direct influence may be limited, but they can still matter significantly. They may influence:

• implementation quality

• customer perception

• employee morale

• reputation

• public opinion

• operational success

Approach

Keep informed and listen. Don't confuse low formal power with low importance.

Low Influence / Low Interest

These stakeholders require less active management. They must still be monitored because their position may change.

Approach

Monitor. The objective is not to spend equal amounts of time on every stakeholder. It's to allocate attention where it can make the greatest difference.

Stakeholder Interests

Identifying stakeholders is only the beginning. You need to understand what each stakeholder actually wants. Consider a company considering automation.

Shareholders

May want:

• lower costs

• higher productivity

• improved margins

Employees

May be concerned about:

• job security

• workload

• retraining

• career opportunities

Customers

May want:

• lower prices

• better service

• faster delivery

Management

May want:

• productivity

• successful implementation

• operational control

Regulators

May focus on:

• employment

• safety

• compliance

• privacy

The same strategic initiative therefore creates different consequences for different groups.

Stakeholder Tensions

Strong strategies often involve trade-offs. Stakeholder analysis helps identify them before they become implementation problems. For example:

Cost reduction

may benefit shareholders and customers through lower prices.

But it may negatively affect employees or suppliers.

Environmental investment

may benefit communities and customers.

But it may increase short-term costs.

Premium pricing

may improve margins.

But it may reduce accessibility and customer demand. The goal is not to pretend these tensions don't exist. The goal is to make them visible and determine how they must be managed.

The Stakeholder Conflict Test

For each major stakeholder, ask:

• What do they gain?
• What do they lose?
• What are they being asked to change?
• What might they resist?
• What could we offer that addresses their legitimate concerns?

This can produce a much stronger implementation plan.

Stakeholder Support Is Not the Same as Agreement

A useful distinction:

• Agreement means a stakeholder believes the strategy is the right decision.
• Support means the stakeholder is willing to help make the decision successful.

A stakeholder doesn't necessarily need to love the recommendation. They may simply need to:

• cooperate

• provide resources

• follow the new process

• stop blocking implementation

• communicate the change positively

• meet their responsibilities

In some cases, sufficient support is more realistic than universal agreement.

Stakeholder Resistance

Resistance is not automatically irrational.

Stakeholders may resist because:

• they will lose something

• they don't understand the change

• they don't trust leadership

• they have experienced failed initiatives before

• incentives are misaligned

• they lack the skills required

• they believe the change creates unacceptable risk

• they have legitimate concerns about implementation

Instead of asking: “How do we overcome resistance?” ask: “Why is the stakeholder resisting?” The answer may reveal an implementation problem that needs to be addressed.

The Resistance Diagnosis

A useful way to diagnose resistance is to ask whether the issue is primarily:

Information

• They don't understand the change.
• Response: Communicate.

Incentives

• The change works against their interests.
• Response: Align incentives where appropriate.

Capability

• They don't know how to execute the change.
• Response: Train, support, or recruit.

Trust

• They don't believe the organisation will follow through.
• Response: Build credibility through actions and transparency.

Resources

• They lack the time, money, technology, or people required.
• Response: Provide resources or redesign the implementation.

Genuine Conflict

• The stakeholder's interests fundamentally conflict with the proposed strategy.
• Response: Negotiate, redesign, compensate where appropriate, or accept the trade-off.

This prevents "stakeholder resistance" from becoming a vague explanation.

Stakeholder Mapping Is Dynamic

Stakeholder influence can change over time. Consider a major transformation.

• At the beginning: Senior leadership may have the greatest influence.
• During implementation: Frontline employees may become much more important because they actually execute the change.
• After launch: Customers may become critical because adoption determines whether the strategy succeeds.

Stakeholder analysis should therefore be revisited at important implementation stages.

Stakeholders and Implementation

Stakeholder analysis becomes most valuable when it changes the implementation plan. Instead of: “Communicate the strategy to employees.” Be specific.

• Stakeholder
  • Frontline employees
• Concern
  • Job security and increased workload
• Required Behaviour
  • Adopt new technology and processes
• Response
  • Training, role clarification, and transition support
• Owner
  • Operations leadership
• Measure
  • Training completion, adoption rate, employee feedback, and productivity

Now, stakeholder analysis has become an implementation tool.

Stakeholder Engagement Strategies

Different stakeholders require different approaches.

Inform

Provide relevant information.

Consult

Seek input before decisions are finalised.

Involve

Give stakeholders an active role in developing or implementing the solution.

Collaborate

Work jointly toward an outcome.

Negotiate

Address competing interests and trade-offs.

Empower

Give stakeholders meaningful decision authority where appropriate. The appropriate level depends on:

• influence

• interest

• risk

• importance

• implementation requirements

Stakeholder Analysis and Communication

Stakeholder analysis should influence what you communicate, to whom, and how. The same strategy may require different messages.

Employees

“Here is what is changing and how we will support you.”

Customers

“Here is how this change improves your experience.”

Investors

“Here is the expected economic impact.”

Regulators

“Here is how the organisation will remain compliant.”

Partners

“Here is what we need from you and what you gain from participating.”

One strategy. Different stakeholder messages. This is why stakeholder analysis also connects directly to effective communication.

Connecting Stakeholder Analysis to Other Frameworks

Stakeholders + McKinsey 7S

• 7S asks: Is the organisation internally aligned?
• Stakeholder analysis asks: Who inside and outside the organisation can influence implementation?

Together they strengthen execution planning.

Stakeholders + Business Model Canvas

The Business Model Canvas identifies:

• customers

• partners

• activities

• resources

Stakeholder analysis asks: What do these groups want, and how might they respond? This makes the business model more realistic.

Stakeholders + Value Chain

Value Chain identifies important activities. Stakeholder analysis identifies the people and organisations involved in performing those activities. For example: Supplier → Procurement → Manufacturing → Distribution → Customer. Each connection creates stakeholder dependencies.

Stakeholders + VRIO

VRIO may identify a capability as strategically important. Stakeholder analysis can reveal whether the organisation has the relationships and support necessary to deploy that capability. For example: A company may have strong proprietary technology but depend on an external partner to commercialise it. The partner becomes strategically important.

Stakeholders + Five Forces

Five Forces focuses on competitive relationships. Stakeholder analysis broadens the perspective to include groups that may not be direct competitors but can still affect implementation.

Worked Example: Entering a New Market

Consider a company planning to enter a new geographic market. The strategy appears attractive based on market size and growth. But stakeholder analysis reveals additional considerations.

Customers

• Interest: High
• Influence: High

Need to understand local preferences and willingness to pay.

Employees

• Interest: Medium–High
• Influence: High

May need training or relocation.

Local Partners

• Interest: High
• Influence: High

May provide distribution and market knowledge.

Regulators

• Interest: Medium
• Influence: High

May control market access or compliance.

Existing Suppliers

• Interest: Medium
• Influence: Medium

May need to increase capacity.

Local Community

• Interest: High
• Influence: Variable

May influence reputation and the organisation's social license to operate.

The strategic question is no longer simply: “Should we enter the market?” It becomes: “What stakeholder conditions must be satisfied for successful market entry?” That is a much stronger strategic question.

From Stakeholder Analysis to Strategic Alternatives

Stakeholder analysis can influence the recommendation itself. Suppose a proposed strategy requires significant employee resistance. Possible alternatives might include:

Full Transformation

Implement the complete strategy immediately.

Phased Transformation

Implement in stages and learn from each phase.

Pilot

Test the strategy with a smaller group first.

Partnership

Use an external partner to reduce internal disruption.

Co-Creation

Involve important stakeholders in designing the solution.

Compensation or Transition Support

Address legitimate costs imposed on affected stakeholders. Stakeholder analysis therefore doesn't simply affect communication. It can change the strategy and implementation design.

The Stakeholder Feasibility Test

Before finalising a recommendation, ask:

• Support
  • Who needs to support this?
• Resistance
  • Who is likely to resist?
• Influence
  • Who can block or delay it?
• Resources
  • Who controls the resources we need?
• Dependencies
  • Who must cooperate for implementation to work?
• Impact
  • Who is most affected?
• Response
  • What are we going to do about each critical stakeholder?

If these questions can't be answered, the recommendation may not be implementation-ready.

Winning the Room

Don't present stakeholder analysis as a list of names. Instead, identify the stakeholder dynamics that matter to the recommendation. For example: “The strategy has strong customer and investor support, but implementation depends on frontline employees adopting the new operating model. Their primary concern is increased workload rather than the strategy itself. We therefore recommend a phased rollout supported by training, redesigned incentives, and frontline feedback before full implementation.” This tells the judges:

• who matters

• what matters to them

• where the risk lies

• how you will address it

That is much more persuasive than a stakeholder matrix by itself.

Coach's Lens

“Don't tell me who the stakeholders are. Tell me what you need from them, and what you need to do to get it.” This is the key shift from stakeholder identification to stakeholder management. The strongest case teams understand that implementation is often a process of building enough alignment to move the organisation forward.

Common Mistakes

• Listing every possible stakeholder: Not everyone deserves equal attention.
• Treating influence and interest as the same thing: A stakeholder can care deeply but have limited influence, or have significant influence without much interest.
• Assuming resistance is irrational: Resistance often contains useful information about risk, incentives, or implementation barriers.
• Trying to make everyone happy: Strategic decisions involve trade-offs.
• Ignoring internal stakeholders: Employees and managers often determine whether implementation succeeds.
• Ignoring external stakeholders: Customers, suppliers, regulators, partners, and communities can materially affect outcomes.
• Stopping at the stakeholder map: The map is a diagnostic tool it should lead to actions.
• Using generic communication: Different stakeholders require different messages.
• Forgetting stakeholder dependencies: A strategy may depend on one stakeholder even if that stakeholder appears relatively unimportant at first.
• Treating stakeholder analysis as a one-time exercise: Stakeholder influence and interests can change throughout implementation.

MAD Skills Drill

Take a recommendation from a case.

Step 1: Identify the Critical Stakeholders

List the five to eight stakeholders most relevant to implementation.

Step 2: Map Them

For each stakeholder, assess:

• Interest

• Influence

• Likely position

• Desired outcome

Step 3: Diagnose the Tension

For each important stakeholder, complete:

• They want ______.
• Our strategy requires ______.
• The potential conflict is ______.

Step 4: Identify the Required Behaviour

What do you actually need the stakeholder to do? For example:

• approve

• fund

• adopt

• cooperate

• change behaviour

• provide resources

• promote

• comply

Step 5: Build the Response

Determine whether you need to:

• inform

• consult

• involve

• collaborate

• negotiate

• incentivize

• train

• compensate

• redesign the strategy

Step 6: Assign Ownership

Who inside the organisation is responsible for managing the relationship?

Step 7: Define the Measure

How will you know whether sufficient stakeholder support has been achieved?

Step 8: Deliver the Story

In 90 seconds, explain: “The stakeholders who matter most are ______. Their primary interests are ______. The biggest implementation tension is ______. We will address it by ______, which will enable ______.” No stakeholder-map tour. Tell the judges the stakeholder story.

Chapter Summary

Stakeholder analysis helps case solvers understand the people and organisations that can influence or be affected by a strategic decision. The framework moves through several levels: Identify → Prioritise → Understand → Anticipate → Engage → Manage. The objective is not to make every stakeholder happy. It is to understand:

• who matters

• what they want

• how much influence they have

• what they may support or resist

• what the organisation needs from them

• what actions are required to build sufficient support

Stakeholder analysis becomes particularly powerful when connected to implementation. A recommendation is stronger when it recognises the human and organisational realities that determine whether the strategy can actually be executed.

Key Takeaways

✓ Strategy is implemented by people and organisations, not by plans alone.

✓ Stakeholder analysis should begin with the specific strategic decision.

✓ Distinguish between interest and influence.

✓ Prioritise stakeholders rather than treating everyone equally.

✓ Understand stakeholder interests, incentives, concerns, and dependencies.

✓ Resistance can reveal legitimate implementation problems.

✓ Support doesn't necessarily require universal agreement.

✓ Different stakeholders require different engagement strategies.

✓ Stakeholder analysis can influence the strategy itself, not just communication.

✓ Connect stakeholder analysis to McKinsey 7S, Business Model Canvas, Value Chain, VRIO, and implementation planning.

✓ Turn the stakeholder map into specific actions, owners, and measures.

Bottom Line

A strategy becomes implementable when the organisation understands not only what needs to change, but who must help make that change happen. The strongest case solutions recognise that strategic decisions create different consequences for different stakeholders. They anticipate those reactions, manage legitimate tensions, build the necessary support, and incorporate stakeholder realities directly into the implementation plan. The goal is not to eliminate disagreement. The goal is to create enough understanding, alignment, cooperation, and accountability for the strategy to move forward.

Looking Ahead

With this chapter, we complete the core framework toolkit in this section. We have moved from understanding the external environment to understanding the organisation and finally to understanding the people who influence execution:

• PESTLE → What is changing around the organisation?
• Porter's Five Forces → What competitive pressures shape the industry?
• Value Chain → Where is value created, lost, and strengthened?
• VRIO → What can the organisation do better, differently, or more defensibly?
• Business Model Canvas → How does the organisation create, deliver, and capture value?
• McKinsey 7S → Is the organisation aligned to execute the strategy?
• Stakeholder Analysis → Who must support, enable, or respond to the strategy?

The important lesson is that no single framework provides the answer. The real MAD Skill is knowing which question needs to be answered, choosing the right tool, finding the insight, and turning that insight into a decision. Frameworks are not answers. Frameworks are thinking tools.