The Presentation Plater

Here's an office truth nobody says in the meeting: most presentations are plating work. The thinking already exists — in your report, your spreadsheet, your journal — and then you spend three hours moving it into boxes, fighting fonts, and wondering if the section header should say "Update" or "Progress." The content took a week to earn; the boxes took an evening to fill.

AI slide tools promise to fix this and mostly commit the opposite sin: gorgeous decks with invented structure — their idea of what matters, wearing your data. The plater we build today has a stricter contract, the same one every station in this kitchen signs: it plates only what your kitchen actually cooked, and you decide the menu.

What you'll plate today

A real deck outline — one message per slide, evidence attached, speaker notes drafted — built from your existing work, plus honest guidance on the last mile into PowerPoint.

Ingredients

• Your prep-station kitchen, now rich with material (report drafts, grind output, recaps)
• One real upcoming presentation need — even a small one ("explain the Q3 numbers to the team")
• About 30 minutes

Cook

1. The message outline — thinking before boxes

The plater's core discipline comes from how good presenters actually work: every slide is one message stated as a sentence, not a topic. "Q3 costs" is a topic; "Q3 costs fell 12% because the butler did it" is a message.

I'm presenting [topic] to [audience] for [outcome — inform?
approve? decide?]. Search the kitchen — journal, report drafts,
grind output, recaps — and propose OUTLINE.md:

1. One slide per line. Each line is a MESSAGE — a full sentence
   someone could agree or disagree with. No topic-titles.
2. Under each message: the evidence from my files that backs it,
   with the source named.
3. Mark any message you WANTED to include but found no evidence
   for as [NO SPINE] — those either get evidence or get cut.
4. Ten slides maximum. Fewer is better.

Work the outline hard — this is the judgment step and it's yours. Reorder, cut, and watch the [NO SPINE] flags especially: a claim with no evidence behind it is exactly the slide that gets you the hard question in the room. Cut it or go earn its spine.

2. Plate it

OUTLINE.md is approved. Plate it as slides.html — a simple
clean deck I can present from a browser: message as the headline,
evidence as the body, my First Kitchen taste rules, arrow keys to
navigate. And under each slide put SPEAKER NOTES: two plain
sentences of what I'd actually say, in my register.

Open it, arrow through, read the notes aloud once. Adjust with the loop — "slide 4's evidence should be the chart numbers, not the sentence about them." A browser deck presents perfectly well over screen-share, which covers most office reality.

3. The PowerPoint mile — honest version

Sometimes the deck must be .pptx because the company template is law. The honest state of that road:

I need this in PowerPoint with our corporate template. What are
my real options from here, and what does each cost me?

It will lay out the menu truthfully: outline-paste into PowerPoint (fast, then you restyle), agent-generated .pptx (real, but template fidelity varies — check what it says about your setup), or slides.html for the meeting and .pptx only if someone asks for "the file." Pick by what the room requires, not by maximalism. The three hours you're saving were never in the file format — they were in the boxes-and-fonts loop you just skipped.

4. Station it

Create a skill "plate": given a topic, audience, and outcome, cook
the message outline from kitchen evidence ([NO SPINE] flags on),
wait for my edit, then plate slides.html with speaker notes.
Save point "the plater", CHORES.md done, log it.

When it burns

• The outline came back with corporate poetry ("Driving synergies across…") — your register rule isn't loaded here yet: "plain declarative sentences, the way my report-style file talks. Rewrite." Poetry hides weak messages; flat sentences expose them, which is why we use them.
• Every message flagged [NO SPINE] — the presentation might be premature, and learning that now beats learning it in the room. Either go cook the missing evidence (a grind run? a journal search?) or narrow the talk to what you can actually stand behind.
• Ten slides feel impossibly few — the appendix trick: "add an APPENDIX section — slides I show only if asked." The main line stays lean; the backup answers live one keypress away. Old consulting move, honestly earned here.
• The deck looks plain next to a designed template — plain with a spine beats gorgeous without one, and the room remembers messages, not gradients. If design is politically required, that's the .pptx mile — budget the extra time consciously.
• You're presenting the grind numbers and someone will ask "is this right?" — the Lesson 7 answer, out loud: "checked against last month's known-good edition, checksums passed." Watch what that sentence does to the room.

Order up

□ OUTLINE.md: messages with spines, [NO SPINE] claims cut or fixed
□ slides.html plates only what the kitchen cooked — notes in your voice
□ You know the honest .pptx options and picked consciously
□ Skill "plate" standing by; CHORES.md: seventh DONE

Next up — Lesson 09: The Safety Inspection. Seven stations run on your machine now, and they touch work data. Before the last lesson sends your cooking toward colleagues, we write the rules — what never enters this kitchen, what IT deserves to know, and when the honest answer is "not yet."

Stuck on a step? Question box below.