AI for Presentations
Work a full example
A worked project proves the method by showing decisions, failures, corrections, and evidence.
Before you start
Why this matters
Without opening an AI tool, write the acceptance test for this job: create a seven-minute decision deck for a six-week customer-support pilot. Name one fact that must be exact, one judgment a person must make, and one condition that should stop the workflow. Compare your answer with the professional standard below; the gap is what you should practice.
1Learn the idea
Read
Project brief
The project is to build and rehearse a six-slide pilot approval deck with an evidence appendix and anticipated-question sheet. The user is department leaders with little technical background. Definition of done: the intended action is clear, the candidate uses approved evidence, blocking safety checks pass, and another person can reproduce the key result.
Stage 1: prepare
Create the job card and collect decision requested, audience concerns, verified evidence, time limit, slide count, brand constraints, and likely objections. Remove or replace prohibited material: remove confidential strategy, customer names, internal forecasts, and unreleased product information before using an external tool. Add one ordinary case, one boundary case, and one hostile or misleading case. Record unknowns instead of filling them with plausible guesses.
Stage 2: draft
Create a six-slide outline for leaders deciding whether to assign two staff to a six-week support pilot. Use only my evidence. Each title must be a complete takeaway sentence; add 2–3 support bullets, a suggested visual, and speaker notes under 40 words. Mark missing evidence; never invent metrics or quotes.
The first candidate should be A title-only story that moves from current support delay to bounded pilot, measurement plan, risk controls, and a final staffing decision. In this worked run, imagine it also exhibits one realistic defect from this set: decorating before structuring; invented metrics; slide titles that name topics rather than conclusions; overcrowded notes; unlabeled generated imagery. Do not hide the defect. Mark the exact criterion it violates and decide whether the cause belongs to context, instruction, model capability, or the surrounding process.
Stage 3: repair narrowly
Issue a targeted revision:
Revise only the failed criterion identified below.
Preserve all verified content and the original output contract.
Do not add facts or assets.
Return the corrected artifact plus a one-line change note.
Failed criterion: [paste criterion and evidence]
A narrow repair keeps the review surface understandable. If the model cannot repair without new authoritative information, pause and obtain that information.
Stage 4: verify and release
Now read titles alone for logical flow, trace every number to a source, inspect chart axes, rehearse to seven minutes, and test contrast, font size, and alt text. Record pass/fail evidence for each criterion and have the named reviewer make the release decision. A deck is a guided argument, not prose divided into rectangles. If the titles alone do not tell the story, visual polish will not rescue it. Save limitations in language the audience can understand.
Read
Retrospective
The durable deliverable is not only the final result. It is a presentation packet containing the brief, title spine, source ledger, accessible visuals, timed notes, and Q&A prep. Write what surprised you, which check found it, what you changed, and which control should become the default. A clean retrospective distinguishes a prompt improvement from a data, tool, or policy change.
Continue learning · glossary & guides
- Can the reviewer see the failed first attempt and why the correction was justified?
- Does the release packet contain evidence, ownership, and known limitations?
- Reference · Related concept
- Previous
- Next