consulting-stakeholder-update

name

consulting-stakeholder-update

description

The writing style for a quick update or recap to an external stakeholder (client sponsor, champion, exec, partner) after a session, milestone, or to flag a blocker plus an ask. Use on "draft an update to {name}", "recap the session for the client", "send {sponsor} a quick note", "status update", "check in with {stakeholder}". Runs on top of consulting-outbound-email (the process) and consulting-copy-writer (the voice), shaping them into a fast, scannable update built on simplicity, clarity, and play. Not for internal post-session notes (those are unfiltered, Sid's POV) and not the formal bi-weekly progress report (heavier) — this is the light note between them.

Consulting Stakeholder Update

The style for a short note to a stakeholder: a recap after a working session, a milestone update, or a "here's what surfaced and what I need" flag. It sits on top of consulting-outbound-email (the process: read all context first, route the ask to the right person, gate before sending) and consulting-copy-writer (the voice: no em-dashes, short and direct, cool/calm/confident). This skill adds the shape and the feel for updates specifically.

Not rigid. This is a set of principles and a shape to riff on, not a template to fill. Adapt to the person and the moment. Drop any section that earns nothing. The goal is a note that reads like a trusted partner wrote it in two minutes, not a status report.

Three principles

Simplicity — fewer words, faster read.

• Lead with the headline in line one. No throat-clearing ("I wanted to reach out").
• One idea per sentence. If a word earns nothing, cut it.
• Group anything list-like into tight bullets (reasons, tools, next steps). Bullets scan faster than prose.
• One clear ask with a low-effort default ("connect me with X and I'll take it from there"), not a menu.
• Shorter than feels natural. A recap rarely needs more than ~150 words.

Clarity — the reader knows exactly what happened, what you need, and from whom.

• Plain words a non-expert would say out loud. No jargon, no insider verbs.
• Make the win explicit, so a setup-heavy session never reads as a bust.
• Frame a blocker as a finding plus the fix, never a complaint.
• Route each ask to the right owner (IT vs ops vs the sponsor); name names when you can.
• Every fact, name, and product name correct (e.g. Wispr Flow, not Whisper; Git is the machine, GitHub is hosting).

Play — keep the human in it.

• Match the relationship's tone. With a warm contact a casual sign-off ("Ok byyyyyeeeee") beats a stiff one; with a formal one, dial it back.
• Confident and easy, never needy. No "just checking in," no apologizing for their time.
• A little personality and warmth is the point. This is a note from a partner who's enjoying the work, not a corporate update.

The shape (use what serves; reorder freely)

1. Headline — one warm line: what happened / how it went.
2. What we did — a sentence or two of real progress (the win).
3. What surfaced + the ask — the blocker or finding, framed as solvable, with the ask routed to the right person. Bullets if it's a list.
4. Quick notes — tools, recommendations, side items. Bulleted, brief.
5. Next — the forward look (next session booked, momentum).
6. Sign-off — with personality that fits the relationship.

Gut check before sending (read it as them, don't grind a checklist)

• Could a busy person get the point and the ask in one skim?
• Is the win obvious and the blocker framed as solvable?
• Is the ask aimed at the right person and low-effort for them?
• Does it sound like you, not a status bot? (And zero em-dashes — see consulting-copy-writer.)

Worked example — session recap to a sponsor (Darren session 1 → Evan, 2026-06-23)

Setup-heavy session, framed as a win plus one routed ask. ~150 words, scannable, warm sign-off.

Hey Evan,

Great first session with Darren. I saw exactly how he's using AI, and we started building Seeker's finance AI operating system in Claude Code.

One thing surfaced that's bigger than Darren: he was still in Claude Chat, not the coding agents (Cowork / Code) where the real leverage is. Windows machines need some setup a Mac doesn't:

• The virtual machine platform enabled
• Git, Node.js, and Python installed

We worked around it today. But it's worth a quick conversation with IT about setting every machine up so the team is AI-ready out of the box.

A few cheap tools would speed Darren up. No need to go org-wide yet. Let's go person by person until something's worth scaling:

• Granola for meeting notes
• Wispr Flow for voice prompting
• GitHub access to save his work to the company's codebase

Last thing: I can start scoping the IRIS API connection. Darren said Janet can help, so feel free to connect us.

Ok byyyyyeeeee

Sid

Why it works: headline win first; the blocker is a finding with a fix, not a gripe; the one real ask (IT) is routed and low-effort; tools and next step are bulleted and brief; the sign-off keeps the rapport. Plain words throughout, no jargon, no em-dashes.