How to Make a Board Presentation with Claude

What a board presentation has to do

A board does not meet to learn what happened last quarter. It meets to make a decision, and it has read forty other pages that week. A board deck is therefore an argument with one recommendation, not a summary of everything the team knows.

Three ideas from strategy consulting shape that argument. The Pyramid Principle, developed by Barbara Minto at McKinsey, puts the answer first and the supporting evidence beneath it. The answer is stated as a governing thought: the one sentence the board should remember when it leaves the room. The storyline follows SCR, situation, complication, resolution: what the room already agrees on, what has changed and forces a decision, and what you recommend.

Beneath the governing thought sit three supporting arguments that are MECE, mutually exclusive and collectively exhaustive. They do not overlap, and together they cover the whole case. A fourth argument usually means two of the three overlap; two arguments usually mean one is missing.

Why a one-line request gives a weak deck

Type “make me a board presentation on our margin problem” into any AI tool and you get a title slide, an agenda and eight slides of bullet points. The content may be accurate. The structure is the problem, because the request gave the tool nothing to decide with: no decision, no audience, no evidence, no rules.

The method, step by step

Consultants build a board deck in a fixed order, and the order is what makes the result good. The same eight steps work in Claude if you make the AI follow them rather than jump to slides.

1. Intake. State the objective (the one decision the deck must win), the audience and their main concern, the length and deadline, your raw material, and your brand colours and fonts if you have them.
2. Route. Classify the deck. A board recommendation, a market study, a sales pitch, an investor deck and a quarterly business review (QBR) each need a different storyline and different analyses. Adjust for the audience: a board leads with risk, governance and shareholder value, and drops operational detail.
3. Analyse. Run only the analyses that deck type needs, and grade every finding as evidence-based, inference or assumption, so the board knows which numbers are measured and which are judgment.
4. Narrate. Write the governing thought and the three MECE arguments before a single slide exists, and say the whole case aloud in 60 seconds. If it does not work spoken, it will not work on slides.
5. Blueprint. Lay out the slide-by-slide skeleton: for each slide, its action title, its job in the argument, its visual, its evidence and its speaker note. Flag any slide carrying two ideas (split it) or none (cut it).
6. Craft. Lock the final action title and the one chart for every slide, in a consistent house style.
7. QA. Test the whole deck against a short list of board gates and fix every failure.
8. Build. Produce the file, or a build-ready specification where the tool cannot create files.

Worked example: Ridgeline Health

Run through the method, the brief routes as a strategy and board deck. The storyline is SCR with the answer first, and the audience overlay for a board puts risk and governance ahead of operational detail. The blueprint for that deck type runs to twelve slides: cover, governing thought, situation, complication, root cause, options, recommendation, business case, roadmap, risks, the ask, and an appendix.

The order matters more than the content of any one slide. The recommendation reaches the board on slide 2, before the evidence, so every later slide is read as proof of a position rather than as background. The PowerPoint Generator page shows Ridgeline’s twelve slides as the prompt built them.

Action titles: the test every slide must pass

An action title is a slide title written as a full sentence that states the slide’s one takeaway. A topic label names the subject and leaves the reader to work out the point; an action title makes the point. Board members often read only the titles, so the titles have to carry the argument by themselves.

Three rules keep action titles honest. One message per slide: if the title needs “and” to join two findings, the slide should be two slides. The body proves the title: anything on the slide that does not support the sentence at the top is removed or moved to the appendix. The titles read as a paragraph: list them in order and they should tell the whole case without the slides.

Try it: the action-title check

This is one module of the PowerPoint Generator, the action-title standard, rewritten to run on its own on a deck you already have. Paste your slide titles with the key number from each slide.

You are a former engagement manager at a strategy consulting firm who has reviewed hundreds of board decks before they went to the client. A board reads the slide titles first, and often only the titles, so every title must state its slide's one takeaway as a full sentence, and the titles read in order must carry the whole argument.

MY DECK:
- The decision this deck asks for: [e.g. approve a margin recovery plan]
- Who it is for: [board / CEO / investors / a customer]
- Each slide, in order: [slide number | current title | the key number or finding on the slide]

Produce:

1. THE REWRITTEN TITLES. For every slide, the current title and a new action title: one full sentence, under 15 words, stating the takeaway and carrying the slide's key number. If a slide has no finding to state, say so instead of inventing one.

2. THE SLIDES TO SPLIT OR CUT. Any slide carrying two messages (split it, and give both titles) and any slide carrying none (cut it or merge it).

3. THE ANSWER-FIRST CHECK. Whether the recommendation appears by slide 2. If it does not, write the governing thought: the one sentence the audience should remember, stated as the answer.

4. THE STORYLINE READ. The new titles, in order, written as one paragraph, and the one gap in the argument that paragraph exposes.

Use only the numbers I give you. Where a title needs a figure I have not supplied, write [NEEDS DATA] rather than estimating one.

This check fixes the titles of a deck that already exists. It does not classify the deck, run the analysis, build the storyline from raw material, choose the charts or produce the file. Those are the other seven steps of the Generator.

One chart per slide, chosen for the point

Each slide makes one point, so it needs one visual, and the visual follows from the kind of point being made. If the data does not justify a chart, the slide uses text.

Getting an editable PowerPoint file out of Claude

Claude can create a real .pptx file when code execution and file creation is turned on in its settings. It writes and runs code that builds the file, which you then download and open in PowerPoint. Built this way, charts are native chart objects: the series, labels and colours can all be edited in PowerPoint, rather than being pictures of charts.

ChatGPT can run the same steps and build a file where code execution is available to it. Gemini returns a build-ready specification: titles, body text, visuals, speaker notes and colour codes for each slide.

Two habits make the difference in practice. Paste the whole instruction set in one message, so the rules travel with the task. Stay in one conversation to the end. A specification copied into a new chat is a summary; the evidence grades and the reasoning behind each title stay in the conversation that produced them, and the deck built from the summary is weaker.

Checks before the board sees it

Before any file is built, test the deck slide by slide. A deck that fails one of these is not ready, however good it looks.

• Every title is a full-sentence takeaway, not a topic label.
• Each slide carries one message.
• The governing thought appears by slide 2.
• The arguments do not overlap, and together they cover the case.
• Every slide body proves its title; no data sits on a slide without a point.
• Every number can be traced to a source, and estimates are marked as estimates.
• The deck leads with what this audience cares about most.
• It ends on a specific ask.
• Each visual matches its data, with nothing added for decoration.

Questions

Written by a former Gartner Managing Partner and investment banking SVP

The guides and the prompt templates on this site come from a career spent building these documents: board decks, forecasts, business cases and hiring decisions, as Managing Partner at Gartner, SVP in investment banking and Country Manager at international subsidiaries. The worked examples are published in full on each product page. Browse the Prompt Library.