How to Structure a Presentation: A Simple Story Framework
Most presentations don’t fail because of bad slides. They fail because the audience can’t tell where the talk is going. If you’ve ever wondered how to structure a presentation so people follow from start to finish, a simple story framework will do most of the work. This post walks through five parts, a worked example and how to apply it to a talk, an assignment or a recorded video.
Why structure matters more than slides
An audience can forgive plain slides. They struggle with a talk that wanders. A clear structure tells people what problem you’re solving, why it matters and what you want them to do. It also makes the talk easier to write, because each slide has a job.
Structure matters even more in a video. A live audience can ask a question when they’re lost. A viewer just stops watching.
How to structure a presentation in five parts
The framework is simple: situation, problem, answer, proof, next step.
1. Situation
Start with what the audience already knows or accepts. This gets everyone on the same page and shows you understand their world.
Example: “Every semester, our first-year students submit their first lab report in week four.”
2. Problem
Introduce the tension. What’s wrong, missing or at risk? This is the reason anyone should keep listening.
Example: “Many of those reports lose marks for the same formatting errors, and markers spend hours writing the same feedback.”
3. Answer
Give your main point, solution or finding. Say it plainly. If the audience remembers one thing, it should be this.
Example: “A ten-minute video guide, released in week two, walks students through the report template before they start.”
4. Proof
Back up the answer. Use evidence the audience will trust: data, examples, a demonstration or a comparison. Only use figures you can actually stand behind.
Example: “In the pilot class, markers reported fewer repeated formatting comments, and students said they felt clearer about what was expected.” (Swap in your own real results.)
5. Next step
Tell people exactly what to do now. A talk without a next step ends with a polite nod and no action.
Example: “I’m asking each unit coordinator to add the video to their week-two module.”
Turning the framework into slides
Once you have the five parts, build the deck around them.
| Part | Typical slides | Tip |
|---|---|---|
| Situation | 1 to 2 | Keep it short; the audience knows this already |
| Problem | 1 to 3 | Make it concrete with one example |
| Answer | 1 to 2 | Put the answer in the headline |
| Proof | 2 to 5 | One piece of evidence per slide |
| Next step | 1 | One clear request |
A few rules make it work:
- One idea per slide. If a slide carries two points, split it.
- Headlines that make a point. “Formatting errors cost students marks” beats “Lab reports”.
- Detail in the notes. The slide shows the point; the notes hold the explanation.
For more on keeping slides focused, see The One Idea Per Slide Rule (and When to Break It).
Write the headlines first
A quick way to test your structure is to write only the slide headlines, in order, before designing anything. Read them aloud. They should tell the whole story on their own.
Here’s the lab report talk as headlines:
- First-years submit their first lab report in week four
- Many lose marks for the same formatting errors
- Markers repeat the same feedback hundreds of times
- A short video guide in week two can fix this
- The pilot class made fewer formatting errors
- Students said they understood the template better
- Add the video to your week-two module
If a headline doesn’t move the story forward, cut it or merge it.
Adapting the framework
For a short talk
Use one slide per part. Five slides, five minutes.
For a longer talk
Repeat the problem, answer and proof cycle for each sub-topic, then finish with one combined next step.
For an assignment
Your marking criteria often map neatly to the framework. The situation is your context, the problem is your research question, the answer is your argument, the proof is your evidence and the next step is your conclusion or recommendation.
For a recorded video
Keep the situation very short. Viewers decide quickly whether to keep watching, so get to the problem early. Write your speaker notes as spoken sentences, because they’ll become your narration.
Common mistakes
- Starting with background that goes on too long. Get to the problem quickly.
- Hiding the answer. Don’t save your main point for the final slide.
- Proof without a point. A chart should support a claim stated in the headline.
- No ask. End with a specific next step, not “any questions?”
Quick checklist
- Can you state the problem in one sentence?
- Is the answer in a headline, not buried in a bullet?
- Does each proof slide support the answer?
- Does the final slide ask for one specific action?
- Do the headlines alone tell the story?
From structured slides to a structured video
A deck built on this framework turns into a clear video with very little extra work, because the story is already there. When your headlines and notes are ready, upload the deck to the PowerPoint to video converter. a.i. takes the director’s chair: it reads the whole deck, tightens the story and designs each scene around the part it plays, whether situation, problem, answer, proof or next step. You’ll hear quickly whether the story flows.