Decks that win the room.
A deck earns its place when it makes the thinking clearer. We built one live from a fictional partner brief and kept the reasoning visible as we worked.
We began with messy notes and one meeting objective. Six slides came out at the end, but the useful work happened before we built any of them.
The workflow had six moves: restate the objective, research what matters, model the people in the room, outline the argument, build the deck, and polish it against the brief. Each move ended with a visible checkpoint. That made weak reasoning easier to catch before someone turned it into a convincing slide.
The agent built a browser-based deck with presenter notes. Then we asked it to review the result against the audience and objective. Two slides changed, and that second pass mattered more than the first render.
Operator move: take the meeting you keep pushing to Sunday evening. Run the six moves before opening PowerPoint.
Build the argument first
Give the agent your notes and ask: "What does this room need to believe by the end?" Do not build a slide until the answer feels sharp.
Run the six moves on one real meeting
Bring meeting notes you are allowed to use, plus the audience and the decision you need from them.
- Save your notes in a folder as
notes.md. Remove private details if the tool is not approved for them. - Paste the prompt below. Approve or correct the argument before the assistant builds anything.
- Open the result and ask for one critique against the audience and objective.
- Change the weakest slide. Do not spend the remaining time adjusting fonts.
Read notes.md. We are preparing for this meeting: - Audience: [who will be in the room] - Decision or outcome: [what we need by the end] - Time available: [minutes] Work in six moves. 1. Restate the objective as one sentence: "By the end, this room needs to believe..." 2. List the facts that matter and the claims that still need evidence. 3. Model the audience. What does each decision-maker need to hear or see? 4. Propose a six-slide argument. One claim per slide. 5. Wait for my approval, then build a single-file HTML deck with presenter notes. 6. Review the finished deck against the audience and objective. Name the weakest slide and fix it. Use only facts from my notes or sources you can cite. Mark assumptions clearly. Keep the visible text short.
Public slide deck
The argument, the six-move model, and the exercise in seven slides.
open slides ๐ฌFull recording
Microsoft employees can watch the complete live deck build after corporate sign-in.
Microsoft employees ๐ ๏ธSlidemaster Framework
The public, reusable HTML presentation framework behind this workflow.
public repo ๐ฏUse Case Finder
Find the real meeting or deliverable worth building next.
Still not a developer. Just got tired of fighting the slide before fixing the argument.