Playbook · 2026

How to write all-hands decks with Claude: step-by-step.

An all-hands deck should tell one story, not dump every team's update. This playbook gives you a prompt template that structures a clear narrative arc.

Short version

Give Claude the meeting's one message, the updates, and the audience, then ask for a slide-by-slide outline with a narrative arc and speaker notes. You get a structured deck outline to build from, in minutes.

The prompt template

This template turns raw updates into a story: where we are, what changed, what is next, what we need from you. Paste your inputs.

Copy, paste, and fill in the brackets

You are my internal comms and presentation partner. Outline an all-hands deck. Context: - The ONE message of this all-hands: [the thing everyone should leave with] - Key updates: [paste metrics, wins, changes, challenges] - Audience: [whole company / size / context] - Tone: [candid / rallying / steady] Rules: - Structure a narrative arc: where we are, what changed, what is next, the ask. - One idea per slide, a clear title sentence, 2-4 bullets, and a speaker note. - 8-12 slides. Lead and close on the ONE message. - Do not use em dashes. Output a slide-by-slide outline.

The arc is the point: a deck that argues one message beats a stack of team updates. For the written version, see internal newsletters with Claude.

The step-by-step workflow

Set up a Claude Project. Add your company metrics, prior decks, and your leadership voice as project knowledge so you never re-paste context. Claude Projects keep brand voice, examples, and rules in one place.
Paste the prompt template. Fill in the bracketed fields with your specifics. The more precise the inputs, the less editing the output needs.
Generate two or three variations. Ask for two outline options with different narrative framings. Pick the strongest and tell Claude what you liked so the next pass sharpens it.
Iterate, do not accept the first draft. One follow-up instruction (tighter, warmer, shorter, more specific) usually does more than re-prompting from scratch.
Edit for voice and accuracy, then save the prompt. Claude gets you most of the way; you own the final 20 percent. Save the working prompt so next time is a two-minute job.

A worked example

Drop in the one message ('we are doubling down on retention this quarter') and your metrics. Claude returns a slide-by-slide outline that opens on that message, walks the arc, gives each slide a title sentence and speaker note, and closes on the ask, so you build slides instead of structuring from scratch.

What to avoid

Vague prompts. 'Help me write this' produces generic output. Specifics in, specifics out.
Publishing or sharing without editing. Always do the final human pass for voice, facts, and judgment.
Skipping the Project setup, which forces you to re-paste context every single time.
Treating Claude as a vending machine instead of a thinking partner you iterate with.

Frequently asked questions

How do I structure an all-hands deck?

Around one message, with a narrative arc: where we are, what changed, what is next, the ask. Give Claude your updates and the template here builds that arc.

Can Claude write speaker notes?

Yes. The prompt asks for a speaker note per slide so you have talking points, not just bullets. Edit them into your own voice.

How many slides should an all-hands have?

Usually 8 to 12. Prompt Claude to keep one idea per slide and cut anything that does not serve the single message.

Does Claude build the actual slides?

It builds the outline, titles, bullets, and notes. You drop that into your slide tool. The thinking and structure are the slow part, and that is what it handles.