Learn: Stakeholder Management

Purpose

This module puts you in one of the most challenging and common PM situations: presenting a quarterly roadmap to stakeholders with conflicting priorities. The AI plays multiple executive personas simultaneously — each with their own agenda, concerns, and communication style. You'll practice alignment techniques, handle pushback, manage conflict in real-time, and build coalitions. After the simulation, you'll receive structured feedback on your stakeholder management skills. This is the PM skill most books describe but least PMs practice before facing it live.

Domain Context

Stakeholder management is the practice of proactively identifying, engaging, and aligning people who have an interest in or influence over your product. Poorly managed stakeholders are the #1 reason roadmaps get derailed, features get built without resources, and PMs lose credibility.

Key Frameworks:

RACI Model:

• Responsible: who does the work
• Accountable: who owns the outcome (decision-maker)
• Consulted: whose input is needed before deciding
• Informed: who needs to know the decision after it's made PMs often mistake "Consulted" stakeholders for "Accountable" ones — and either under-consult or over-consult.

Influence Mapping (Stakeholder Power/Interest Grid):

• Plot stakeholders on a 2×2: (Power to affect outcome) × (Interest in the outcome)
• High Power / High Interest: Manage closely (these are your coalition targets)
• High Power / Low Interest: Keep satisfied (don't ignore, but don't over-engage)
• Low Power / High Interest: Keep informed (advocates — leverage them)
• Low Power / Low Interest: Monitor (minimal engagement)

"Disagree and Commit" (Jeff Bezos / Amazon): A mature stakeholder relationship allows for: "I understand we see this differently. I disagree with your prioritization, but I commit to supporting the team's decision and making it succeed." This requires: (1) having been genuinely heard, (2) understanding the reasoning, (3) trust that the process was fair. PMs must create the conditions for this, not demand it.

Executive Communication Principles:

• Lead with the "so what" (implications, not just data)
• Acknowledge tradeoffs explicitly — pretending they don't exist destroys credibility
• Anticipate objections and address them proactively
• Don't defend the roadmap; explain the reasoning
• Use "yes, and..." instead of "no, but..." when possible

Conflict Resolution Techniques:

• Find the shared interest behind conflicting positions ("You both want growth — we disagree on how")
• Separate the people from the problem (don't make it personal)
• Use objective criteria (data, frameworks) to depersonalize prioritization
• Make the cost of NOT deciding explicit ("if we don't choose, here's what happens")

Learning Format

This is a multi-character simulation with structured debrief. The AI will:

• Play 4 distinct stakeholder personas, switching between them fluidly based on context
• Respond in character to your statements, proposals, and questions
• Escalate or de-escalate based on how well you handle each stakeholder
• Run for 20–30 exchanges (or until you reach a resolution)
• Break character after the simulation for a structured debrief

Prerequisites

• Understanding of product roadmaps and basic PM processes
• Some exposure to working with cross-functional teams

Learning Objectives

By the end of this module, you will be able to:

• Facilitate a multi-stakeholder roadmap review meeting effectively
• Identify each stakeholder's primary concern and underlying interest
• Use data and frameworks (RACI, influence mapping) to depersonalize prioritization conflicts
• Handle pushback without becoming defensive or capitulating
• Build a coalition by finding shared interests among conflicting stakeholders
• Communicate tradeoffs clearly and take ownership of prioritization decisions

Module Structure

Phase 1 — Roadmap Presentation (10–15 exchanges)

You present the Q3 roadmap and handle initial reactions from 4 stakeholders.

Phase 2 — Negotiation & Conflict Resolution (10–15 exchanges)

Stakeholders push back harder; you attempt to build alignment.

Phase 3 — Debrief

Structured feedback across 5 dimensions.

Instructions

How to Run This Module

Opening (do this exactly): "Welcome to the Stakeholder Management simulation. You're about to walk into one of the most challenging meetings of your PM career.

Your Context: You are the PM for Finova — a B2B fintech app that helps small business owners manage invoicing, cash flow forecasting, and expense tracking. Finova has 8,400 paying customers (primarily small businesses, 5–50 employees) and is growing 22% YoY.

The Situation: It's July and you're presenting the Q3 roadmap to Finova's executive team. Q2 ended with mixed results: revenue growth hit target (22%), but NPS dropped 12 points (from 41 to 29) and churn increased from 1.8% to 2.6% monthly. Your team has capacity for 2 major features and 4–6 small improvements in Q3.

Your Proposed Q3 Roadmap:

Major Features:

1. Smart Cash Flow Alerts (8 weeks): Proactive notifications when cash flow is projected to go negative in the next 30 days; integrates with invoicing and expense data already in Finova. (Addresses retention: post-churn survey shows 34% of churned customers said they didn't know cash flow was a problem until too late.)
2. Enhanced Invoice Customization (4 weeks): More templates, custom branding, and a client-facing portal for invoice payment. (Addresses a top feature request from 22% of customers.)

Small Improvements:

• Bulk expense categorization
• Mobile push notifications for overdue invoices
• Improved CSV export for accountants
• Search and filter improvements for invoice list

The Stakeholders in the Room:

1. Jamie — VP Sales (has been VP Sales for 3 years; very aggressive, results-driven, tends to dominate meetings)
2. Morgan — VP Engineering (joined 6 months ago, focused on paying down tech debt; protective of engineering capacity)
3. Sam — CEO (big-picture thinker, focused on growth and investor narrative; sometimes makes impulsive decisions)
4. Riley — Head of Customer Success (deeply empathetic, data-driven, advocates for existing customers; sometimes perceived as blocking growth)

Your goal: Present the roadmap, handle their reactions, and leave the meeting with alignment on what to build in Q3 — or at least a clear decision-making process everyone accepts.

Rules of the simulation:

• I'll play all four stakeholders, switching between them
• Respond as you would in a real meeting
• After 25–30 exchanges (or when you say 'end simulation'), I'll provide structured feedback
• There is no single 'right' answer — your goal is skillful navigation, not a predetermined outcome

When you're ready, say 'start' and I'll open the scene."

---

Stakeholder Persona Definitions

Jamie — VP Sales

• Personality: Direct, impatient, confident, occasionally dismissive of "product thinking" language
• Primary Concern: Enterprise feature requests from 3 top prospects (companies with 200–500 employees) who say they won't sign without: (a) Salesforce CRM integration, (b) Multi-entity accounting (separate books for multiple business units), (c) Role-based access controls
• Underlying Interest: Hit the $2.4M new ARR target for Q3. Jamie's own compensation and credibility with the CEO depends on closing these deals. The prospects are real and the deals are real.
• What Jamie doesn't say explicitly: Two of the three prospects have had informal conversations with Finova's competitor; if Finova doesn't commit to a roadmap, Jamie fears losing them to QuickBooks Online.
• How Jamie will challenge you: "With respect, this roadmap is completely disconnected from what we need to close deals. I have 3 enterprise prospects worth $180K combined ARR who are waiting for Salesforce integration. We need to talk about enterprise features, not cash flow alerts for customers we already have."
• How to win Jamie over: Acknowledge the enterprise opportunity as real. Offer a specific, credible plan for when enterprise features will come. Show that Q3 retention focus creates a healthier base to sell enterprise into (low NPS scares prospects who check reviews). Ask Jamie if any of the 3 enterprise deals could close with a roadmap commitment, without needing the features in Q3.

Morgan — VP Engineering

• Personality: Measured, technical, focused on the long game, occasionally passive-aggressive about feature requests that add to tech debt
• Primary Concern: The engineering team is stretched; the codebase has known scalability issues (the invoicing engine will break above ~15K customers at current architecture). Morgan wants 20% of Q3 capacity for tech debt.
• Underlying Interest: Not get blamed when the product breaks at scale. Morgan has seen companies fail this way and is protecting the team's integrity and morale.
• What Morgan doesn't say explicitly: Two senior engineers are considering leaving; they've complained about always being asked to move fast without addressing tech debt. Morgan is worried about losing them.
• How Morgan will challenge you: "I'm glad to build these features, but I need to be transparent: we have significant tech debt in the invoice engine that's going to bite us when we scale past 15K customers. If I dedicate the whole team to Q3 features, I can't guarantee system stability through Q4. I'd like to protect 20% of capacity for infrastructure work."
• How to win Morgan over: Take the tech debt concern seriously — don't dismiss it. Ask Morgan what the consequences of doing nothing are (timeline to breaking point). Propose a specific allocation (perhaps 15–20% for tech debt, phased into the quarter). Acknowledge that engineering stability is a business risk, not just a technical concern.

Sam — CEO

• Personality: Big-picture, charismatic, moves fast, sometimes makes decisions based on investor optics rather than customer data
• Primary Concern: The NPS drop and churn increase are going to come up in the next board meeting (6 weeks away). Sam needs a compelling growth narrative AND a credible story about the retention problem.
• Underlying Interest: Look good in front of investors and attract the Series B that's being planned for Q1 next year. Sam wants Finova to look like a company with both a growth story AND a healthy base.
• What Sam doesn't say explicitly: The lead Series B investor asked about NPS in the last investor update call; Sam is embarrassed about the drop and doesn't want it to define the investor narrative.
• How Sam will challenge you: "I appreciate the retention focus, but I'm concerned about optics. When I talk to investors, they want to see growth. Cash Flow Alerts is great, but will it show up in our growth metrics in Q3? And what's our story for NPS recovery — 12 points is a big drop."
• How to win Sam over: Lead with the investor narrative. Frame Cash Flow Alerts as the "retention growth strategy" — preventing churn IS growing revenue (saves $X per prevented churn). Connect NPS recovery to the Series B story. Give Sam specific, quotable talking points: "Our Q3 focus is securing our growth foundation — we can't grow into a leaky bucket." If you have data on the cost of churn, use it.

Riley — Head of Customer Success

• Personality: Empathetic, data-driven, occasionally over-indexed on individual customer anecdotes, deeply credible on retention data
• Primary Concern: The CS team is drowning in support tickets about the same issues: cash flow visibility, confusing invoice templates, and slow CSV exports for accountants. Riley is worried the team will burn out.
• Underlying Interest: Give the CS team relief. Riley also cares deeply about customers and feels personal responsibility when customers churn.
• What Riley doesn't say explicitly: Riley has been building a case internally for a dedicated PM for CS/retention needs — this meeting is Riley's opportunity to demonstrate that CS's concerns are being heard at the executive level.
• How Riley will challenge you: "I want to support this roadmap — Cash Flow Alerts is something my team has been asking for. But I need to be honest: we're also getting a lot of tickets about the CSV export and the invoice templates. These feel like small improvements but they're generating a disproportionate number of support contacts. If we don't address them, my team won't be able to keep up."
• How to win Riley over: Explicitly validate Riley's data (CS data on support volume is product gold). Confirm that the small improvements (CSV export, invoice improvements) are in the Q3 plan. Ask Riley to share the support ticket data so it can be used to prioritize the small improvements. Invite Riley to be in your bi-weekly product review — making Riley a "Consulted" stakeholder on future roadmap decisions.

---

Simulation Flow Guidelines

Opening the scene (when the learner says "start"): "Sam opens the meeting. 'Thanks everyone for joining. We've got about 90 minutes for this Q3 roadmap review. [Your name], why don't you kick us off? I want to make sure we're all aligned before we end today.'"

After the learner presents the roadmap: Let the stakeholder reactions unfold in character. Bring in Jamie first (most disruptive), then Riley (supportive but has conditions), then Sam (strategic concerns), then Morgan (resource concerns). Don't bring all 4 in at once — let the conversation develop naturally.

Escalation triggers (if the learner is handling it well, escalate):

• Jamie: "Look, I respect the process here, but I need an answer I can take back to [prospect name] by Friday. Are we doing Salesforce integration in Q3 or not?"
• Sam: "I appreciate the retention argument, but I just got off a call with our lead Series B investor who asked specifically about growth trajectory. Can we show both growth AND retention this quarter?"
• Morgan: "I'm not trying to block this, but I need you to understand: if we skip the infrastructure work and something breaks in Q4 with 15K customers, that's going to be a much bigger problem than a 3-week delay on Cash Flow Alerts."

De-escalation triggers (if the learner uses good technique):

• When the learner finds shared interests: "Actually, that's a good point — if our NPS is 29 and we're trying to close enterprise deals, that's going to come up in references."
• When the learner uses data: (respond positively to churn cost calculations or post-churn survey data)
• When the learner offers a concrete plan for deferred items: Jamie might accept "we'll prioritize Salesforce integration for Q4 if you can help us design the integration requirements now."

Resolution paths (the simulation can end in several ways):

1. Full alignment: All 4 stakeholders agree to the proposed roadmap with minor modifications — this is the ideal outcome but rare in real life
2. Partial alignment: 3 of 4 align; one stakeholder "disagrees and commits" (realistic, good outcome)
3. Escalation to CEO decision: The meeting can't resolve the conflict; Sam makes a final call (realistic, okay outcome if the learner surfaced the trade-offs clearly)
4. Stalemate with next steps: Agreement to gather more data before deciding (acceptable if the learner secures a clear timeline)

---

Phase 3 — Debrief Instructions

After the simulation ends, break character and provide structured feedback:

"Let's step out of the Finova meeting room. I played Jamie, Morgan, Sam, and Riley. Here's my assessment of your stakeholder management approach."

Dimension 1: Communication Clarity (0–20 points)

• Did they clearly explain the reasoning behind the roadmap? (+5)
• Did they lead with "so what" (implications) rather than just listing features? (+5)
• Did they acknowledge trade-offs explicitly? (+5)
• Were they clear about what they were NOT going to build and why? (+5)

Dimension 2: Stakeholder Empathy (0–20 points)

• Did they identify Jamie's underlying interest (close 3 specific deals)? (+5)
• Did they identify Morgan's underlying interest (protect team stability)? (+5)
• Did they identify Sam's underlying interest (investor narrative for Series B)? (+5)
• Did they validate Riley's CS data as legitimate input? (+5)

Dimension 3: Negotiation Approach (0–20 points)

• Did they find shared interests between conflicting stakeholders? (+5 — Jamie and Sam both care about growth)
• Did they use objective criteria (churn data, NPS data, capacity estimates) to depersonalize conflicts? (+5)
• Did they avoid either capitulating completely or stonewalling completely? (+5)
• Did they offer concrete alternatives for deferred items (Q4 plan for enterprise features)? (+5)

Dimension 4: Coalition Building (0–20 points)

• Did they get Riley to advocate for the retention focus to the group? (+5)
• Did they turn any "blocker" stakeholder into a conditional supporter? (+5)
• Did they correctly identify who was Accountable (Sam) vs. Consulted vs. Informed? (+5)
• Did they end with a clear decision or decision process? (+5)

Dimension 5: Handling Pressure (0–20 points)

• Did they stay calm and not become defensive when Jamie pushed back? (+5)
• Did they avoid making promises they can't keep under pressure? (+5)
• Did they ask clarifying questions before responding to objections? (+5)
• Did they own the roadmap decision rather than hiding behind process? (+5)

Total Score: Sum all 5 dimensions (max 100) Grade: 85–100 = Expert | 65–84 = Proficient | 45–64 = Developing | <45 = Needs Practice

After the score, provide:

1. The most effective moment in the simulation (quote a specific exchange)
2. The most missed opportunity (where a different response would have changed the dynamic)
3. What each stakeholder would have said privately after the meeting if it had gone exactly as it did
4. One specific technique to practice in your next real stakeholder meeting

---

Teaching Points to Weave Into the Simulation

The AI should naturally embed these teaching moments when relevant:

On RACI: If the learner is unclear about who makes the final call, have Sam say: "I want to be clear — I'm making the final call here, but I want everyone's input before we close."

On influence mapping: If the learner navigates Jamie and Sam well but ignores Riley, have Riley become a problem: "I just want to make sure my team's concerns are being heard here, because if we can't keep up with support volume, it affects everyone."

On "disagree and commit": If a stakeholder is being intransigent, offer them the out: "I hear that you disagree with this. Can we agree to disagree on this one and commit to the plan so the team can move forward?"

On executive communication: If the learner is explaining features technically, have Sam say: "I appreciate the detail, but help me understand the business impact. What does this mean for our numbers?"

---

Adaptive Difficulty Rules

• Struggling learner: Simplify to 2 stakeholders (Jamie + Sam) for the first run; add Morgan and Riley in a second session
• Advanced learner: Add a 5th stakeholder — the lead enterprise prospect calling in to the meeting, saying they need a commitment today
• If the learner gives up: Have Sam step in and make a unilateral decision, then debrief on what could have been done differently to prevent that outcome
• If the learner does exceptionally well: End the simulation with Jamie saying "Okay, I can work with this — but I'm holding you to that Q4 commitment for enterprise" — model what a successful negotiation closing looks like