Home / Module 7
Module 7

Roadmapping & Stakeholder Alignment

📖 2 Lessons⏱ 60-90 min 🧪 Lab: Roadmap and Stakeholder Communication✅ Quiz: 6 questions

Learning Objectives

Lesson 7.1
Roadmaps Are Communication Tools
✓
Roadmaps SHOULD communicate:
  • Strategic direction (where we are going)
  • Priorities (what matters most)
  • Outcomes (what we expect to achieve)
  • Sequencing (what comes first and why)
✗
Roadmaps should NOT be:
  • Feature wishlists
  • Guaranteed commitments
  • Static documents that go stale
  • Output-focused (features) rather than outcome-focused
⚠️
AI Roadmap Failures to Watch For: Key results not measurable ("improve onboarding" vs "increase step 3 completion from 41% to 55%") · Sprint allocation miscounts · Dependencies in wrong order · Initiatives spanning more than 4 sprints without a milestone · Features listed instead of outcomes
Lesson 7.2
Stakeholder Communication Patterns
AudienceWhat They Care AboutCommunication Style
ExecutivesOutcomes, risks, metrics1-page summary, no jargon, bullet points
EngineersScope, clarity, dependenciesDetailed requirements, technical context
DesignersUser problems, constraints, freedomProblem statements, not solutions
SalesCompetitive positioning, timelinesFeature availability, objection handling
SupportKnown issues, workarounds, ETAsTroubleshooting guides, escalation paths
Lab 7

Roadmap and Stakeholder Communication

Scenario: Q3 prioritization is complete (from Module 6). You need to: (1) build the Q3 roadmap, (2) communicate it to three different audiences, and (3) resolve a stakeholder conflict.
Step 1 and 2

Create prompts/roadmap-generator.md. The roadmap must be outcome-oriented, include quarterly goals, key results (measurable), dependencies, risk assessment, sprint allocation (12 sprints, 1 buffer), and sequencing rationale. Run it and apply the AI roadmap failure check before proceeding.

Step 3

Create prompts/stakeholder-comms.md to generate three communications from the same roadmap:

  • Executive update (CEO + VP Product): 5 sentences max, outcomes + risks, bullet format
  • Engineering kickoff (Tech Lead + engineers): 15 sentences max, scope + dependencies + constraints, structured sections
  • Sales enablement (Head of Sales + AEs): 10 sentences max, what's coming + when + competitive positioning, Q&A style

Rules: do not promise unconfirmed dates, do not overcommit scope, be honest about risks, tailor language to each audience.

Step 4 — Stakeholder Conflict Resolution

Resolve this conflict:

Engineering Lead: "Onboarding wizard scope is too large for Q3. We can do
the basic flow but progress tracking and contextual guidance need to wait."

Sales Lead: "We told Acme Corp the full wizard would be ready in August.
If we don't deliver the full experience, they'll evaluate WorkForge."

CEO: "I want this shipped in Q3. Full scope."

Work through: (A) map constraints — what each stakeholder wants, why, what they fear, and their flexibility; (B) find the overlap; (C) identify false constraints; (D) propose a phased approach with Phase 1 (Q3) and Phase 2 (Q4) with committed timeline.

Write deliverables/W07-conflict-resolution.md with constraint mapping table, proposed solution with phasing, tradeoffs made, and the actual message you would send to each stakeholder.

Deliverables

  • Roadmap generator prompt + raw output
  • Stakeholder comms prompt + 3 communications
  • Conflict resolution memo with actual stakeholder messages

How to Verify Completion

  • Every initiative in your roadmap has measurable key results with numbers — not directional phrases
  • Sprint allocation sums to 11 (leaving 1 buffer)
  • Your three stakeholder communications use demonstrably different vocabulary and detail levels
  • Your conflict resolution memo includes the actual messages you would send to Engineering Lead, Sales Lead, and CEO
  • Your phased solution specifies what ships in Q3 vs Q4 with a committed date for Q4
Done when: Each stakeholder receives communication that directly addresses their concern without creating inconsistency between what you've told different people.
Quiz

Module 7 — Knowledge Check

0 / 6 answered
Question 1 of 6
A roadmap entry reads "Improve onboarding experience." Why is this an AI roadmap failure?
A It is too vague for the engineering team to estimate
B It is not a measurable key result — there is no number to know when success is achieved or progress tracked
C It does not mention which team member is responsible
D It is a feature, not an outcome
Correct. Roadmaps need measurable key results. "Improve onboarding" cannot be tracked. "Increase step 3 completion from 41% to 55% by end of Q3" can be measured, celebrated when hit, and investigated when missed.
Question 2 of 6
Why should you include 1 buffer sprint in a 12-sprint quarterly roadmap?
A To give the team time to take vacation
B Because stakeholders always request additional features mid-quarter
C To absorb unplanned work — every quarter has incidents, urgent fixes, or scope changes that were not anticipated; a buffer makes this manageable without blowing the roadmap
D Because AI models automatically add a buffer in roadmap generation
Correct. A roadmap that allocates 100% of capacity is a roadmap that will fail every quarter. Unplanned work always arrives. A buffer sprint makes the roadmap resilient to reality rather than brittle to it.
Question 3 of 6
When communicating the roadmap to Sales, what should you focus on that you would NOT emphasize to Engineers?
A Technical architecture decisions and API dependencies
B Sprint-level delivery timeline and sprint capacity
C User research findings that validated the roadmap priorities
D What is coming and when, how to position it against competitors, and how to handle customer objections
Correct. Sales needs to know what they can sell, when it will be available, and how to talk about it versus competitors. They do not need to understand sprint allocation or API design. Communication should match what the audience will act on.
Question 4 of 6
In the stakeholder conflict, Sales says Acme Corp "will evaluate WorkForge" if full scope doesn't ship. How should a PM treat this claim?
A Accept it as fact and escalate to the CEO to force the feature through
B Dismiss it — customers rarely follow through on threats
C Investigate whether it is a verified threat or a fear — ask Sales what specifically Acme said and whether partial delivery plus a committed Q4 date would satisfy them
D Immediately reduce scope to deliver a partial wizard faster
Correct. The conflict resolution framework asks you to identify false constraints. "They will evaluate WorkForge" might be a direct customer statement or a Sales rep's fear. Before making engineering tradeoffs, verify what the customer actually requires vs. what would satisfy them.
Question 5 of 6
What makes a phased delivery proposal effective in resolving stakeholder conflicts?
A It reduces engineering effort by delivering less
B It partially satisfies all stakeholders by delivering value sooner while making Phase 2 credible with a committed timeline from Engineering
C It delays the conflict until Phase 2 without resolving it
D It shows the CEO that the PM is collaborative and willing to compromise
Correct. Phasing works because: Engineering delivers a feasible scope, Sales can tell Acme something ships in Q3, and the CEO gets meaningful progress. The key is that Phase 2 must be credible — Engineering must commit to the Q4 date, not just acknowledge it.
Question 6 of 6
When reviewing AI-generated stakeholder communications, what is the most important thing to check?
A Grammar and spelling
B Whether the communication matches the roadmap's visual format
C Whether the AI used the stakeholder's name correctly
D Whether any promises, dates, or scope commitments appear that were not in the approved roadmap — AI often adds specificity that creates implicit commitments
Correct. AI-generated communications frequently add specificity to seem helpful: "This will be shipped by August 15" when you only said "Q3"; or "this includes full SSO support" when SSO was only partial. Any commitment in a communication that was not in the source roadmap is a risk.
Module 7 Score