Outline a presentation slide by slide
Give your topic, audience and time slot. Get a slide-by-slide outline with a title, the one key point and speaker notes for each slide, timed to fit your slot.
How to use it
- Say what you want to happen Not the topic but the outcome: a decision, approval, a change in what people do.
- Attach your material Reports, data or notes the talk should draw on. The outline uses their numbers.
- Read the titles only Slide titles read in order should tell the whole story. If they don't, ask for a rework.
- Build and rehearse Ask in the chat for full speaker notes for any slide, or a five-minute version.
The prompt
Plan a presentation for me, slide by slide.
Topic: [TOPIC]
Audience (who they are, what they know, what they care about): [AUDIENCE_DETAILS]
Time slot: [TIME_AVAILABLE]
What I want the audience to do or decide afterwards: [DESIRED_OUTCOME]
Use any attached material for facts and numbers.
Return:
- The one-sentence message of the whole talk.
- A table of slides: number, slide title written as a full-sentence takeaway (not a label like "Background"), the single key point, what goes on the slide (chart, image, three words — not paragraphs), and minutes.
- Speaker notes for each slide: two to four sentences of what to say.
- Timing that adds up to the slot with a minute or two spare, and an opening that is not "Today I'll talk about…".
- The three questions the audience is most likely to ask, with short answers or what to prepare.About one slide per minute or two. Put the ask early and repeat it at the end. Do not invent data; where a slide needs a number I have not given, mark it "number needed".
Example result
The message: A three-month, four-day roster trial for support costs nothing extra, keeps cover the same, and gives us real data on burnout and satisfaction — approve it for February.
| # | Slide title (takeaway) | Key point | On the slide | Min |
|---|---|---|---|---|
| 1 | We're asking for a 3-month trial, not a permanent change | The ask, up front | The ask in one line + dates | 1 |
| 2 | Support attrition is our most expensive problem | Why now | Attrition rate, cost per replacement — number needed | 1.5 |
| 3 | The roster keeps the same hours of cover | It isn't fewer hours open | Current vs trial roster, two columns | 2 |
| 4 | Other support teams have trialled this | Evidence, not theory | Two short examples with results | 1.5 |
| 5 | We'll measure CSAT, response time and sick leave weekly | How we'll know | Three metrics with today's baselines | 1.5 |
| 6 | If CSAT drops more than 3 points, we stop | Low risk | Stop rule in large type | 1 |
| 7 | Approve a February start today | The ask, repeated | Decision + next steps | 1 |
Total: 9.5 minutes, 30 seconds spare.
Speaker notes
- "I'm here for one decision: a three-month trial of a four-day roster for support, starting in February. Everything else in the next ten minutes is why it's safe to say yes."
- "Last year we lost [number needed] support staff. Each replacement costs about [number needed] in recruiting and training — before the hit to customers while they ramp up."
- "Nobody's open hours change. We stagger the roster so every day has the same cover as now; each person works four longer days."
- Keep to two examples you can name, and say what they measured.
- "We'll report these three numbers every week, against the baseline on screen."
- "If satisfaction drops more than three points for two weeks in a row, the trial ends early. You lose nothing."
- "So: can we start the trial on 2 February? If yes, I'll send the roster to team leads this week."
Opening line instead of "Today I'll talk about…": "Last year, every second person we hired into support left within 18 months."
Likely questions
- "What does it cost?" — Prepare a one-line answer: no change in salary or hours of cover.
- "What if customers notice?" — Point to the stop rule on slide 6.
- "Why only support?" — Support has the highest attrition; a contained trial gives clean data.