Stakeholder Prep
🔵 Optional
Use this when: You have a stakeholder meeting tomorrow (or in a few hours) and need to be ready with clear talking points, anticipated questions, and a concise progress narrative.
Quick version: Use the
/stakeholder-prepskill in Claude Code for one-command execution.
Why this matters
Stakeholder meetings are where trust is built or eroded. A PM who shows up with a clear narrative, data to back it up, and answers to likely questions earns confidence. A PM who wings it burns credibility.
An agent can help you build that narrative quickly by processing your sprint data, backlog state, and context into a structured briefing.
What to prepare
Before running this workflow, gather:
- Who's in the meeting and what they care about (goals, concerns, biases)
- Current iteration status (what shipped, what's in progress, what's blocked)
- Recent metrics or data (if relevant — usage, conversion, support tickets)
- Any sensitive topics (delays, scope changes, team issues, budget)
- The meeting's stated purpose or agenda (if one exists)
The workflow
Step 1: Build the briefing
I have a stakeholder meeting with (stakeholder name/role) about (topic/project).
Here's the context:
Meeting purpose: (what they expect from this meeting)
Stakeholders attending: (names and what each person cares about)
Current iteration status:
(Paste iteration plan with status updates)
Recent progress:
(Key things shipped or learned in the last 1-2 iterations)
Open issues:
(Blockers, delays, risks, scope changes)
Help me prepare:
1. Draft a 2-minute verbal summary I can use to open the meeting (what we did, what we learned, what's next)
2. List the 3-5 questions they're most likely to ask, with suggested answers
3. Identify any topics I should proactively raise (before they ask)
4. Flag anything in my context that could be a concern for this audience
5. Suggest 1-2 things I should ask them for (decisions, resources, access, feedback)
Step 2: Review and adapt
The agent's output is a starting draft. Refine it:
- Tone — Does the verbal summary sound like you? Rewrite phrases that feel generic or robotic.
- Political awareness — The agent doesn't know interpersonal dynamics. Adjust the framing based on what you know about each stakeholder.
- Anticipated questions — Are these the right questions? Add any you know from experience that the agent missed.
- Proactive topics — Is there anything you should raise that the agent couldn't know about (hallway conversations, recent org changes)?
Step 3: Prepare your asks
Every stakeholder meeting should end with something you need from them. The agent's suggestions are a starting point, but you know what's truly blocking progress.
What to review
| Check | Why |
|---|---|
| The narrative is accurate | Don't present the agent's version of events if it's slightly wrong — stakeholders will notice |
| The tone matches the audience | Executive stakeholders want concision; technical stakeholders want depth |
| Anticipated questions are realistic | Add questions from your experience with these specific people |
| Your asks are actionable | Vague asks ("we need more support") waste the meeting; specific asks ("we need access to X by Friday") work |
Common mistakes
- Over-preparing — A 20-page briefing doc isn't preparation; it's avoidance. The agent helps you distill, not expand.
- Reading the agent's script — Use the briefing as prep, not a teleprompter. Stakeholders respond to genuine communication.
- Hiding bad news — If something is behind or at risk, raise it proactively. The agent's briefing should help you frame it constructively, not avoid it.
- Forgetting to ask for something — Every meeting should advance the project. If you're only reporting status, you're wasting a meeting.
AI in practice: stakeholder prep beyond sprint updates
This workflow applies to client-facing meeting prep across industries:
- Account prioritization and meeting prep — Customer success teams use this pattern to synthesize CRM data, usage metrics, and open tickets into pre-call briefings. Prep time drops from 45 minutes to 10 minutes per account. See Customer Success use cases.
- Executive knowledge briefings — Agents pull the most relevant updates across internal platforms into a structured briefing before leadership meetings. See Research & Knowledge use cases.
- Wealth advisor client prep — Financial advisors get portfolio performance, market context, and regulatory updates synthesized into a one-page briefing. See Financial Services use cases.
Frequency
Before every stakeholder meeting. This takes 5-10 minutes and pays for itself in stakeholder confidence.