Stakeholder Analysis and Engagement Design

Purpose

Systematically identify all organisational actors who can influence or are affected by a validation decision, map their power, interest, and salience, assess their current disposition, and design differentiated engagement strategies that build the coalition needed for genuine (not ceremonial) approval.

Unlike stakeholder listing (names on a slide), this method produces an actionable engagement plan: who to meet, in what sequence, with what message, seeking what commitment. The method operationalises stakeholder theory and stakeholder salience for innovation governance contexts where approval requires multi-constituency alignment across functional boundaries.

When to Use

Use stakeholder analysis and engagement design when:

• A1.5 validation requires governance approval involving multiple decision-makers or functional leaders
• Initiative impacts teams beyond the innovation group (IT, Legal, Operations, Sales, Marketing)
• Political complexity exists: competing priorities, contested resources, powerful individuals with conflicting interests
• Prior initiatives failed or stalled due to stakeholder resistance during A4–A7 execution
• Portfolio capacity is constrained—approval requires navigating trade-offs and de-prioritisation of existing projects

Do NOT use when:

• Single decision-maker with full authority and known support—direct presentation sufficient
• Initiative has no cross-functional dependencies (self-contained team, own budget)
• Precedent stakeholder map exists and organisational context unchanged—reuse prior map with light update

Sample Size and Duration

Stakeholder count guidance:

• <5 stakeholders: Simple—1 week
• 5–8 stakeholders: Moderate (standard)—2 weeks
• 8–12 stakeholders: Complex—2–3 weeks
• >12 stakeholders: Very complex—3+ weeks; consider staged validation or delegation

Time allocation per round:

• Round 1 (socialisation): 3–5 days
• Round 2 (deep dives): 3–5 days
• Round 3 (coalition building): 2–3 days
• Round 4 (blocker neutralisation): 2–5 days
• Business case revision between rounds: 1–3 days

Prerequisites

• Draft business case: Completed or near-complete (Method: Structured Business Case Development, the referenced method)— stakeholder engagement revolves around this artefact
• Organisational knowledge: Understanding of I2 governance structure, budget ownership, and informal power dynamics
• Executive sponsor input: Sponsor provides political intelligence (who supports, who opposes, why)
• Participants: Innovation Manager (engagement lead), executive sponsor (political guidance), 1–2 team members (meeting support)
• Time: 1–3 weeks depending on stakeholder count and complexity

Complete Procedure

Step 1: Identify Stakeholders (2–4 hours)

Cast a wide net across four categories, extending beyond formal hierarchy to informal power networks :

1. Decision-makers: executives with formal approval authority (I2 governance members, budget approvers, investment committee)
2. Influencers: individuals who shape decision-maker perspectives (trusted advisors, domain experts, peer executives)
3. Implementers: functional leaders and teams who must execute during A2–A7 (IT, Legal, Operations, Sales, Marketing, Customer Success)
4. Blockers: individuals with veto power or ability to create substantial friction (executives with competing priorities, functional leaders controlling required resources, compliance officers)

Identification prompts:

• Who votes on approval? Who controls the budget?
• Who must provide team members or functional support?
• Whose workflow will change when this launches?
• Who has the CEO's ear on innovation investment?
• Who blocked or slowed a similar initiative in the past?

Step 2: Map Power, Interest, and Salience (1–2 hours)

2a. Power–interest matrix:

Plot each stakeholder on a 2×2 grid:

2b. Salience assessment :

For each stakeholder, assess three attributes:

• Power: Can this stakeholder influence the approval outcome or control required resources?
• Legitimacy: Does this stakeholder have a rightful claim to be considered (functional responsibility, regulatory authority, user impact)?
• Urgency: Is this stakeholder's concern time-sensitive (budget cycle closing, regulatory deadline, competing initiative launching)?

Definitive stakeholders (all three attributes) receive highest engagement priority. Latent stakeholders (one attribute) receive monitoring only.

2c. Disposition assessment:

For each stakeholder, assess current stance: supportive, neutral, sceptical, opposed, or unknown.

Step 3: Populate Stakeholder Register (1–2 hours)

Document all findings in a structured register:

Step 4: Design Engagement Plan (2–4 hours)

For each priority stakeholder (Players and Context-setters), specify:

1. Engagement objective: what outcome do you seek? (e.g., “Convert CFO from sceptical to neutral; secure budget pre-approval”)
2. Message: tailored to their concern (CFO sees financials; CTO sees architecture; COO sees operational impact)
3. Format: one-on-one (30–60 min), small group, or written brief
4. Messenger: who from the team has credibility with this stakeholder?
5. Timing and sequence: engage champions first to build momentum; approach blockers after coalition established

Step 5: Execute Multi-Round Engagement (1–3 weeks)

Follow iterative consensus-building pattern :

Round 1—Initial socialisation (1–2 weeks before governance):

• 30-minute one-on-ones with players and key context-setters
• Present business case summary; test receptiveness; identify major concerns
• Capture feedback for business case refinement

Round 2—Deep dives (1 week before governance):

• 45–60 minute meetings with implementers and functional stakeholders
• Present detailed sections relevant to their domain; negotiate resource commitments
• Create psychological safety for genuine objections

Round 3—Coalition building:

• Convert supportive stakeholders into active champions willing to advocate at governance
• Coordinate messaging; align on key talking points
• Create peer influence through champion network

Round 4—Blocker neutralisation:

• Re-engage stakeholders with fundamental objections; demonstrate how revised case addresses concerns
• Negotiate compromises (scope adjustments, phased approval, conditional Go)
• Secure commitment or at minimum neutrality (“I won't oppose this”)

Revise business case between rounds: incorporate legitimate feedback, adjust scope / timeline / approach where conflicts surfaced, document what changed and why.

Step 6: Assess Consensus Sufficiency (1–2 hours)

Proceed to governance when :

• Decision-makers are briefed and indicate likely approval
• Implementers have committed resources
• Major blockers are neutralised or outnumbered by champions
• Business case incorporates substantial stakeholder feedback

Stop signals: If a powerful blocker remains opposed after 3 engagement rounds, consider recommending Defer or Decline before proceeding to likely governance rejection.

Quality Criteria

Excellent stakeholder analysis and engagement demonstrates:

1. Comprehensive identification: All four categories covered—not just governance committee members
2. Evidence-based mapping: Power, interest, and salience ratings justified by organisational knowledge
3. Differentiated engagement: Strategies vary by quadrant—players get deep engagement, context-setters get concise briefings
4. Sequenced execution: Champions engaged before blockers; coalition built before governance
5. Documented interactions: Engagement tracker records dates, concerns, commitments, and follow-ups
6. Business case evolution: Case visibly improved through stakeholder feedback
7. No governance surprises: Every Player briefed before formal presentation
8. Commitment depth: Functional leaders have made specific commitments (names, FTE, dates)

Theoretical Foundation

Seminal references:

• Foundational work establishing stakeholder theory for strategic management. Defined stakeholders as any group or individual who can affect or is affected by the achievement of an organisation's objectives. Provided the conceptual basis for identifying stakeholders beyond formal decision-makers—including implementers, influencers, and affected parties whose cooperation determines execution success. Remains the standard theoretical framework for stakeholder identification.
• Introduced the stakeholder salience framework based on three attributes—power, legitimacy, and urgency—enabling systematic prioritisation. Definitive stakeholders (all three attributes) demand immediate, substantive engagement; latent stakeholders (one attribute) require monitoring only. This framework resolves the common problem of treating all stakeholders equally, which wastes engagement time and misses critical power dynamics.
• Landmark study of 150 strategic decisions across 30 organisations, demonstrating that decisions requiring cross-functional coordination are rarely made during formal meetings. Formal governance ratifies consensus already built through pre-meeting engagement. This finding provides the empirical justification for multi-round pre-socialisation (Step 5) before governance presentation.

Contemporary references:

• Extended change management research to coalition building, showing that successful organisational initiatives require a “guiding coalition” of influential stakeholders—not just top-management sponsorship. Provided the 8-step change model in which building coalition is the second step, emphasising early engagement before formal launch. Directly informs the multi-round engagement pattern and champion-building logic in Step 5.
• Identified five dysfunctions that undermine team and stakeholder alignment—absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Provides diagnostic framework for understanding why stakeholder engagement stalls: surface agreement masking unresolved conflict (political theatre) is a trust and conflict dysfunction, not a process failure.
• Argues that organisational learning requires psychological safety—people must feel safe to raise concerns without punishment. Informs stakeholder engagement design: blockers must be engaged in environments where expressing genuine objections is welcomed, not penalised. One-on-one meetings (Round 2) create safer contexts for surfacing concerns than formal governance presentations.

Challenges and Solutions

Challenge 1: Decision-Maker Bias—Ignoring Implementers

Symptoms:

• Team focuses exclusively on governance committee members
• Approval secured, but IT / Legal / Operations resist during A4–A7

Solutions:

• Mandate stakeholder register includes at least 2 implementer roles per major function impacted
• Gate A1.5-1 checklist requires documented functional commitments
• Ask: “Whose cooperation do we need during A4–A7 that we haven't engaged yet?”

Challenge 2: Premature Governance Presentation—Skipping Pre-Socialisation

Symptoms:

• Governance committee surprised by proposal
• Decision deferred; zombie approval without genuine commitment

Solutions:

• Enforce rule: no governance presentation until all Players have had one-on-one briefing
• Executive sponsor confirms governance readiness before scheduling presentation

Challenge 3: Powerful Low-Interest Stakeholders Becoming Blockers

Symptoms:

• CEO or CFO learns about initiative late and raises fundamental objection
• Initiative derailed despite broad lower-level support

Solutions:

• Context-setters receive short briefing (15–20 minutes) early in Round 1
• Executive sponsor manages upward briefing
• Focus message on what context-setter cares about (“no impact on your budget”)

Challenge 4: Endless Consensus Seeking—Scope Creep Through Stakeholder Demands

Symptoms:

• Each stakeholder adds requirements; scope doubles
• Validation takes 12+ weeks

Solutions:

• Set consensus sufficiency threshold (Step 6) before starting engagement—perfect consensus is not the goal
• Distinguish “incorporate” from “park” (valid but out-of-scope—acknowledge and defer)
• Time-box engagement: if consensus not reached after 4 weeks, escalate to governance with documented positions

Relationship to Other Methods

Stakeholder Analysis receives input from:

• Structured Business Case Development (the referenced method): The artefact engagement revolves around
• Scope and Ecosystem Mapping (the referenced method): Ecosystem map reveals organisational actors
• A1.4 Feasibility Assessment: Organisational readiness identifies likely supporters and resistors
• I2 Governance Design: Governance structure reveals formal decision-makers

Stakeholder Analysis provides input to:

• Governance Presentation Design (the referenced method): Engagement results determine presentation strategy
• Risk and Assumption Mapping (the referenced method): Stakeholder opposition becomes organisational risk
• Project Charter (A1.5 Step 5): Commitments become charter dependencies
• A2–A7 Execution: Stakeholder map transfers to project team

*Example: Digital Patient Engagement Platform

Stakeholder register (condensed):

Engagement sequence:

1. Week 1: CMO-Med CTO Head of Ortho
2. Week 2: CFO VP Regulatory (Round 1)
3. Week 3: VP Regulatory (Round 2) VP Sales CEO
4. Week 4: VP Regulatory (Round 3) governance readiness check

Outcome: VP Regulatory converted to Conditional Support (advisory board with external expert). CFO moved to Neutral (Phase 2 contingent on Phase 1 data). All Players briefed before governance.

Tools and Templates

• Stakeholder Register (the referenced method)
• Power–Interest Matrix (the referenced method)
• RACI Matrix (the referenced method)
• Stakeholder Engagement Tracker (spreadsheet)
• Customised presentation decks per audience
• FAQ document with prepared responses

• A. C. Edmondson (2023). Right Kind of Wrong: The Science of Failing Well. Atria Books.
• D. J. Hickson, R. J. Butler, D. Cray, G. R. Mallory & D. C. Wilson (1986). Top Decisions: Strategic Decision-Making in Organizations.
• J. P. Kotter (2012). Leading Change. Harvard Business Review Press.
• P. Lencioni (2002). The Five Dysfunctions of a Team. Jossey-Bass.
• R. E. Freeman (1984). Strategic Management: A Stakeholder Approach. Pitman Publishing.
• R. K. Mitchell, B. R. Agle & D. J. Wood (1997). Toward a Theory of Stakeholder Identification and Salience: Defining the Principle of Who and What Really Counts. Academy of Management Review. 22(4). pp. 853–886. doi:10.5465/amr.1997.9711022105