Use this when you have a stakeholder meeting coming up and need to show up with a clear narrative, anticipated questions with answers, and specific asks. Takes 5-10 minutes to prepare, builds stakeholder confidence.
Related resources:
stakeholder-update-guide.md-- 4-step Quick Start Guide for writing stakeholder updates (standalone, printable).
Process
Step 1: Gather context
Ask the user:
- Who is in the meeting? (Names, roles, and what each person cares about — goals, concerns, biases)
- What is the meeting about? (Purpose, agenda if one exists)
- Meeting formality level — working session, steering committee, executive review, or board meeting. This adjusts output tone, depth, and whether a pre-read document is expected.
- Current iteration status — what shipped, what's in progress, what's blocked
- Recent progress — key things shipped or learned in the last 1-2 iterations
- Open issues — blockers, delays, risks, scope changes, sensitive topics
- Which end-user persona(s) is your current work targeting? This frames your narrative around user impact, not just delivery status. If you have defined personas (e.g., from
/persona-createor/persona-draft), name them. If not, describe the key user type briefly.
The user can paste raw data — iteration plans, status updates, notes.
Step 1b: Read the room and calibrate energy
Before the meeting, assess:
- Who has the most at stake? They'll be most engaged or most defensive. Prepare for both.
- Who didn't want this meeting? They'll be resistant or disengaged. Plan to earn their attention early.
- What just happened? If the group just came from another meeting, a crisis, or a celebration, their energy is already set. Don't fight it -- work with it.
- Default power dynamic: Who typically speaks first? Who defers? Who stays silent? Prepare to surface voices that usually stay quiet.
Energy calibration for the verbal summary: Match the opening energy to the room.
- Worried stakeholders → slower pace, calmer tone, ground the update in facts before asking for anything
- Celebratory context → match briefly, then bridge to what's next
- Hostile or skeptical → stay neutral, lead with data, hold space for their reactions before defending
- Flat or distracted → raise energy slightly, open with a question or a specific result that demands attention
Related skills: See
/room-readfor full pre-read and real-time adaptation tools.
Step 2: Generate the briefing
## Stakeholder Briefing — (Meeting topic, date)
### 2-Minute Verbal Summary
(A concise narrative the user can deliver to open the meeting. Covers: what we did, what we learned, what's next. Connect delivered work to the end-user personas it serves — stakeholders respond to user impact, not task completion. Written in natural speaking style, not bullet points.)
**Executive framing variant:** When meeting formality is "executive review" or "board meeting," lead with strategic impact and business outcomes rather than delivery status. Open with the business result, not the activity. Example: "We reduced churn risk in the enterprise segment by 15%" not "We shipped the retention dashboard."
### Pre-Read Document (executive review / board meeting only)
(When the meeting formality calls for a pre-read, generate a one-page document the user can send 24-48 hours before the meeting. Structure: context paragraph, key metrics table, decision or input needed, supporting detail. This replaces the verbal summary as the opening — the meeting then starts with questions, not a readout.)
### Anticipated Questions
1. **(Question they're likely to ask)**
Answer: (Suggested response — concise, honest, data-backed)
2. **(Question)**
Answer: (Response)
3. **(Question)**
Answer: (Response)
### Proactive Topics
(Topics the user should raise before they're asked — risks, scope changes, decisions needed. For each: what to say and why raising it proactively builds trust.)
- (Topic 1)
- (Topic 2)
### Your Asks
(1-2 specific things to ask stakeholders for — decisions, resources, access, feedback. Every meeting should advance the project.)
- (Ask 1 — what you need, from whom, by when)
- (Ask 2)
### Watch-Outs
(Anything in the provided context that could be a concern for this audience — things to handle carefully or reframe.)
### Sensitive Framing Considerations
(Include this section when the meeting involves raising concerns about power dynamics, interpersonal patterns, gender dynamics, or situations where the consultant feels undermined. Skip if not applicable.)
**Framing checklist:**
- Am I presenting an observation or a conclusion? (Observations invite investigation. Conclusions draw lines.)
- Have I separated the behavior pattern from the attributed cause? ("My input gets less traction in meetings with X" vs. "X doesn't respect me because I'm [identity].")
- Is this the right audience for this concern?
- *Team sync:* Name the behavior and its impact on team effectiveness. Keep it about work outcomes.
- *Manager/engagement lead 1:1:* Share the full picture including personal experience and emotional impact. This is where attribution is appropriate.
- *Client-facing:* Frame as process improvement, not personal dynamics. "How can we improve decision flow?" not "Why am I being excluded?"
- Am I asking the audience to solve a problem they have tools for? (Teammates can adjust behavior. They can't adjudicate gender dynamics. Choose the right problem for the right audience.)
**Say this / Not this:**
| Say this | Not this |
|---|---|
| "I'm noticing a pattern where [behavior]. The impact on the team is [specific impact]." | "I think this is happening because of [identity attribute]." |
| "How can we make sure all perspectives are heard in [forum]?" | "Nobody listens to me." |
| "I'd like to flag something I'm observing and get your read on it." | "Lines are drawn and you need to pick a side." |
**Escalation guide:**
- If the behavior is interpersonal friction → raise with the person directly, then engagement lead
- If the behavior is systemic (patterns across interactions, not one incident) → raise with engagement lead or HR
- If you're unsure whether it's personal or systemic → bring it to a trusted peer first, then your engagement lead. Don't process it in a team sync.
Step 3: Review and refine
Ask the user:
- Does the verbal summary sound like you? (Rewrite anything that feels generic.)
- Are the anticipated questions the right ones for these specific people?
- Is there anything the agent couldn't know — interpersonal dynamics, hallway conversations, org changes?
- Are your asks specific enough? ("We need access to X by Friday" works. "We need more support" doesn't.)
Adjust as needed.
Related skills
/artbeat— if the meeting is a weekly engagement update, use/artbeatinstead to generate the full client-facing + internal update. Use/stakeholder-prepfor ad-hoc stakeholder meetings, steering committees, or exec check-ins./sprint-report— if you need iteration data to feed into your stakeholder prep, run/sprint-reportfirst./financial-health-snapshot— if the stakeholder conversation involves budget, financial health, or investment decisions, run this first for context./business-case-builder— if you need to justify an initiative or investment in the meeting, build the business case first.
Output location
Present the briefing as formatted text in the conversation. This is personal prep — the user should not share it as a document.
Example Output
Input
- Who is in the meeting: Sarah Chen (CPO, cares about product-market fit and roadmap coherence, skeptical of scope creep), Marcus Duval (VP Engineering, focused on team capacity and technical debt, tends to push back on timelines), Priya Nair (Head of Customer Success, advocates for enterprise clients, emotionally invested in the retention problem)
- Meeting about: Quarterly steering committee review of the Atlas platform's B2B retention initiative — progress check, upcoming Q3 priorities, and a resource ask
- Meeting formality: Steering committee (executive review)
- Current status and recent progress: Shipped the churn risk scoring dashboard to 12 pilot enterprise accounts; early signal shows 18% reduction in at-risk accounts escalating to churn; onboarding flow redesign is 70% complete but blocked on legal approval for new data consent language
- Open issues: Legal review has been pending 3 weeks and is now threatening Q3 launch date; eng team is running at 90% capacity with two engineers on PTO in August; one pilot customer (Northgate Financial) gave negative feedback on dashboard complexity
- Personas targeted: "Overloaded CSM" — customer success managers at enterprise accounts managing 40+ accounts who need fast, actionable risk signals without additional workflow overhead
Output (abbreviated)
Stakeholder Briefing — Atlas Retention Initiative Steering Committee, Q2 Review
Pre-Read Document
(Send 24–48 hours before the meeting)
Context
The Atlas B2B retention initiative completed its first pilot phase this quarter, delivering a churn risk scoring dashboard to 12 enterprise accounts. Early results are encouraging: at-risk account escalations have dropped 18% among pilot participants. The primary user this work serves is the Overloaded CSM — enterprise customer success managers carrying 40+ accounts who need fast, actionable risk signals without adding to their workflow burden. The next phase targets full rollout alongside a redesigned onboarding flow, currently gated on legal approval.
Key Metrics
| Metric | Status |
|---|---|
| Pilot accounts live | 12 of 12 |
| Reduction in at-risk escalations | 18% |
| Onboarding flow redesign completion | 70% |
| Legal review turnaround (consent language) | Pending — 3 weeks elapsed |
| Engineering capacity (August) | ~80% due to planned PTO |
Decision Needed
Sponsor-level escalation of the legal review to protect the Q3 launch date. Without approval by July 28, the onboarding flow launch slips a minimum of 3 weeks.
Supporting Detail
One pilot customer, Northgate Financial, flagged the dashboard as overly complex for their CSM team. A targeted simplification pass is scoped and can be absorbed in the current sprint. This is a signal worth watching across the broader rollout — CSM adoption is the leading indicator of retention impact, not just deployment count.
2-Minute Verbal Summary
"We set out this quarter to give enterprise CSMs a faster way to spot accounts at risk before they become escalations — and the early data says it's working. Across 12 pilot accounts, at-risk escalations dropped 18%. That's not just a delivery metric — that's Priya's team spending less time in firefighting mode and more time on proactive relationship work, which is exactly what this initiative was designed to unlock.
We're 70% through the onboarding flow redesign, which is what turns this from a pilot into a scalable product. The one thing standing between us and a Q3 launch is legal sign-off on data consent language — it's been in queue for three weeks, and that's now our critical path.
There's also an honest signal from Northgate Financial that the dashboard has more complexity than their CSMs want to engage with. We're treating that as a gift — we'd rather hear it now from one account than after full rollout. A simplification pass is already scoped.
Two things I'd like to get alignment on today: getting someone in this room to escalate the legal review, and a quick conversation about August capacity before we lock Q3 commitments."
Anticipated Questions
-
"Is 18% actually meaningful, or is that noise from a 12-account sample?" Answer: It's a directional signal, not a statistically conclusive result — and we should say that clearly. The more important data point is which accounts improved: 8 of the 12 are in our highest-ACV tier. We're deliberately not over-indexing on the number yet, but we're confident enough to proceed to full rollout while continuing to track.
-
"How much of a delay are we actually looking at if legal doesn't move?" Answer: If approval comes by July 28, Q3 launch holds. Every week past that pushes launch by roughly the same amount — there's no buffer in the engineering schedule once August PTO starts. The practical ceiling is a 3–4 week slip if this drags into mid-August.
-
"What did Northgate Financial actually say, and should we be worried about adoption more broadly?" Answer: Their CSM lead said the risk score was useful but the supporting data view was "too much to process in a 30-second scan." That's consistent with what we know about the Overloaded CSM persona — they need the signal, not the methodology. We're treating it as a UX fix, not a product direction change. We'll validate the simplified version with two additional pilot accounts before broad rollout.
-
"Can the eng team actually absorb Q3 scope at 80% capacity?" Answer: For the planned scope, yes — but there's no room for scope additions or unplanned rework. If the legal delay forces a compressed launch timeline in September, we'd need to have a conversation about trade-offs.
Proactive Topics
-
Legal review block — Raise this yourself before Marcus or Sarah ask about Q3 confidence. Framing: "I want to flag this as our one external dependency that's outside the team's control, and I'd like to leave today with a clear escalation path." Raising it proactively signals you're on top of risk and prevents it from landing as a surprise.
-
Northgate feedback — Don't wait for Priya to bring it up defensively. Frame it as a product learning, not a problem: "One of our pilot customers gave us feedback that's making the product better." This builds trust with the CS audience and shows you're listening to enterprise users.
Your Asks
- Ask 1 (Decision): Request that Sarah or Priya — whoever has the stronger relationship with Legal leadership — formally escalate the consent language review with a July 28 deadline. Ask for confirmation in the meeting, not a follow-up.
- Ask 2 (Alignment): Get explicit acknowledgment from Marcus that current Q3 scope is locked, so the engineering team isn't absorbing informal additions after this meeting. A simple "we're aligned that this is the scope" from him in the room prevents downstream friction.
Watch-Outs
- Sarah's scope creep antenna will be up. The Northgate feedback could prompt a suggestion to "rethink the dashboard before rollout." Hold the line — the simplification is scoped and contained. Broad redesign would blow the Q3 date entirely.
- Marcus may use capacity as a reason to push launch. He's not wrong that 80% is tight, but the risk isn't August — it's a legal delay compressing the September window. Keep him focused on the legal dependency as the real constraint, not the team.
- Priya will want to protect enterprise relationships. She may advocate for more Northgate-specific customization. Redirect toward the scheduled simplification pass and the plan to validate with two additional accounts — she needs to trust the process is already responding to her customers.
Step 3: Refine Before You Walk In
- Does the verbal summary sound like how you actually talk? Adjust any language that feels too formal for your relationship with this group.
- Is there anything happening between Sarah and Marcus right now — budget tensions, reorg rumors — that would affect how they interact in the room?
- Is Priya likely to have already talked to Northgate Financial before this meeting? If so, she may have more detail (or more anxiety) than the feedback summary above captures.
- Your ask to Marcus about scope lock: have you had a pre-conversation with him, or will this land cold?