What is a good presentation structure example?
A good presentation structure example is a repeatable order that helps an audience understand one idea in 10 to 18 minutes, or one business question in 6 to 12 slides. The strongest examples do not just list topics. They move from context to tension to answer, then end with a next step, decision, or memorable takeaway.
Three source-backed patterns show up again and again. MIT's NSE Communication Lab says a technical slide talk works best as an hourglass: start broad, narrow into your work, then widen back out to results and impact. Duarte's 2024 contrast guide says persuasive talks alternate between what is and what could be. Management Consulted's 2026 SCQA guide organizes business stories as Situation, Complication, Question, Answer.
In practice, that means a useful structure example is not just Intro, Body, Conclusion. It names the logic between those parts. For example: current state, problem, decision question, recommendation. Or: audience pain, future state, proof, next step. If you can write the flow in 1 sentence per slide before opening presentation software, the structure is usually solid.
| Structure example | Best use | Core order | What makes it work |
|---|---|---|---|
| Hourglass | Research, case study, conference talk | Big problem, method, result, impact | Starts with audience relevance and ends with why the result matters |
| SCQA | Executive update, strategy, recommendation | Situation, Complication, Question, Answer | Builds tension before the answer |
| Problem-solution | Sales, proposal, internal pitch | Problem, stakes, solution, proof, ask | Keeps attention on a clear before and after |
| Sparkline | Keynote, change story, fundraising | What is, what could be, what is, what could be | Creates contrast instead of a flat report |
What are the best presentation structures to copy?
The best presentation structure examples depend on the job the deck must do. Below are 5 structures that cover most real presentations, from project updates to investor pitches.
1. Simple three-part structure
Use this when the audience is broad and the topic is familiar. Copy this order: hook, agenda, 3 main points, recap, next step. Mural's 2024 outline guide includes title, introduction, agenda, main points, conclusion, and Q&A as a standard outline. A practical example is a 7-slide internal presentation: title, why this matters, point 1, point 2, point 3, summary, discussion.
2. Problem-solution-benefit
Use this for sales, proposals, and product launches. The logic is pain first, not product first. A clean 8-slide example is: title, audience problem, evidence or symptoms, solution, how it works, proof, implementation, call to action. This structure works because every slide answers one of 3 questions: what is wrong, what changes, what do we do next.
3. SCQA
Use this for executive audiences who need the point fast. Management Consulted's 2026 guide defines SCQA as Situation, Complication, Question, Answer. A copyable example for a budget request is: current performance is stable, costs rose 14 percent, what should we change in Q3, approve automation spend. The structure feels logical because the answer arrives only after the question becomes unavoidable.
4. Hourglass
Use this for research or analytical work. MIT says to start broadly with the issue the audience cares about, narrow into your project, then open up again into results and impact. Their guide also recommends grouping results into 2 to 4 groupings. A 9-slide example is: field problem, gap, goal, method, result 1, result 2, result 3, impact, next work.
5. Sparkline
Use this when you need energy, emotion, or change. Duarte's 2024 explanation says strong talks alternate between what is and what could be, rather than dumping facts for 10 slides and saving the recommendation for the end. A simple 6-slide example is: current reality, possible future, current blocker, possible gain, proof, invitation to act.
What does a slide-by-slide presentation structure example look like?
Here are 5 concrete presentation structure examples you can copy slide by slide. Each one fits a different real-world job.
| Use case | Slide-by-slide structure example | Typical length |
|---|---|---|
| Project update | 1 Title and goal, 2 status summary, 3 progress against milestones, 4 risks, 5 decisions needed, 6 next 30 days | 6 slides |
| Sales pitch | 1 customer problem, 2 cost of inaction, 3 solution, 4 product or service, 5 proof, 6 pricing or plan, 7 next step | 7 slides |
| Investor pitch | 1 problem, 2 solution, 3 market, 4 business model, 5 traction, 6 go-to-market, 7 competition, 8 team, 9 financials, 10 ask | 10 slides |
| Training session | 1 objective, 2 why this matters, 3 process overview, 4 step 1, 5 step 2, 6 step 3, 7 common mistakes, 8 recap | 8 slides |
| Research talk | 1 problem area, 2 gap, 3 question, 4 method, 5 result 1, 6 result 2, 7 interpretation, 8 impact, 9 next work | 9 slides |
The investor pitch example above matches Guy Kawasaki's 2021 advice that a pitch should aim for 10 slides, 20 minutes, and at least 30-point font. Even if your content changes, the ordering is still useful because it moves from why the company exists to why the investor should believe it.
The project update example works because it respects decision flow. Busy teams do not want 12 status slides before the risk appears. Put the status summary on slide 2, the risk on slide 4, and the decisions needed on slide 5. That shortens discussion time because the audience sees the action point before Q&A starts.
The training example is effective because it is procedural, not promotional. A learner usually needs 3 things in order: the objective, the sequence, and the mistakes to avoid. If the task has 3 steps, give 3 step slides. If it has 5 steps, give 5. The structure should mirror the process exactly.
- If the audience must approve something, end with a decision slide.
- If the audience must remember a concept, end with a one-line takeaway slide.
- If the audience must perform a workflow, the deck order should match the workflow order.
- If the audience must trust your result, put proof before the ask.
How many slides should each structure have?
There is no universal slide count, but there are useful source-backed constraints. Use time first, then let the structure decide the number of slides.
Guy Kawasaki wrote in 2021 that a pitch should target 10 slides, 20 minutes, and 30-point minimum font. That is not a law for every presentation, but it is a strong structure example for a high-stakes business pitch because it limits clutter and forces a clear narrative.
TED's official help page says talks should be 18 minutes or less because that is long enough to say something meaningful and short enough to hold attention. TED also notes that shorter talks of 3 to 9 minutes can be highly impactful, and some dialogues or interviews may run up to 30 minutes. If you are building a keynote-style structure example, that gives you a realistic time frame.
MIT's slide presentation guide takes a different approach: do not obsess over slide count. Focus on purpose, audience, and the evidence needed to support your message. Their practical advice is more useful than a fixed number for technical or analytical presentations, especially when your result section naturally groups into 2 to 4 findings.
| Presentation type | Useful starting point | Why |
|---|---|---|
| Investor pitch | 10 slides in about 20 minutes | Matches Kawasaki's 2021 rule and keeps concepts focused |
| TED-style talk | 1 idea in 18 minutes or less | Matches TED Help guidance |
| Project update | 5 to 7 slides in 10 to 15 minutes | Enough for status, risks, decisions, next step |
| Training demo | 1 slide per step plus intro and recap | Structure should mirror the process |
| Research talk | 1 slide per result grouping, usually 2 to 4 result slides | Matches MIT's grouping advice |
How do you choose the right presentation structure?
Pick the structure by audience and outcome, not by template style. Start with one question: what should the audience do, think, or feel by the final slide?
MIT's guide begins with purpose, audience, and central message before slide design. That order matters. If the audience is technical and wants evidence, use Hourglass. If the audience is executive and needs a decision, use SCQA. If the audience must imagine a better future, use Sparkline or Problem-solution.
| Audience goal | Best structure example | Start with | End with |
|---|---|---|---|
| Understand progress | Project update structure | Current status | Decision or next 30 days |
| Approve a recommendation | SCQA | Situation and complication | Answer and implications |
| Buy or sign up | Problem-solution | Pain and cost of inaction | Proof and next step |
| Learn a process | Training structure | Objective and overview | Recap and mistakes to avoid |
| Believe a new idea | Sparkline or TED-style structure | Current reality | Future possibility and invitation |
A simple 4-step selection method works well. Step 1: write the audience outcome in 1 sentence. Step 2: list the 3 to 5 ideas the audience must hear in order. Step 3: choose the structure that already matches that order. Step 4: write slide titles before writing slide text. This takes 10 to 20 minutes and usually prevents a weak middle section.
- Choose SCQA when the audience will ask why this matters.
- Choose Problem-solution when the audience already feels pain.
- Choose Hourglass when your evidence is the center of the story.
- Choose Sparkline when emotion and contrast matter as much as facts.
How do you make presentation structure examples with AnyGen?
If you already know the structure you want, AnyGen is most useful at turning that structure into an editable draft fast. The key is to give the structure as ordered data, not as a vague prompt.
Start with a named framework and a target length. For example: create a 7-slide presentation using Problem-solution-benefit for a sales pitch, or create a 9-slide research talk using Hourglass with 3 result slides. That gives the model both the logic and the constraints.
Then feed the exact slide order. Example input: 1 customer problem, 2 stakes, 3 solution, 4 how it works, 5 proof, 6 pricing, 7 next step. Or for SCQA: 1 situation, 2 complication, 3 question, 4 answer, 5 proof, 6 rollout, 7 decision. The closer your input matches the structure examples on this page, the better the first draft.
A practical workflow is 3 passes. Pass 1: generate the outline only. Pass 2: add speaker-ready bullets, numbers, and examples. Pass 3: simplify each slide to one message and one visual. This is especially helpful when you want to turn a rough note set into a deck without losing the original logic.
- Name the structure first: SCQA, Hourglass, Problem-solution, Sparkline, or Training flow.
- Set a number: 6, 7, 9, 10, or 18-minute talk.
- List slide titles in order before asking for visuals.
- Ask for one message per slide, not paragraph-heavy slides.
What mistakes make a presentation structure fall apart?
Most bad presentation structure examples fail for one of 4 reasons: they start too late, explain too much, delay the point, or end without a decision.
Duarte's contrast advice helps explain one common problem: flat decks. If 8 slides in a row describe what is, the audience gets a report, not a story. Add contrast earlier by showing what could change on slide 2 or 3, then return to proof. That creates momentum.
MIT warns against filler endings such as a final Questions slide. Instead, end by reconnecting to the motivation or impact. In business settings, that usually means a decision, recommendation, or next step. In a research setting, it means why the result matters beyond the experiment.
Kawasaki's 30-point font rule also exposes a structural issue. If you need tiny text, the problem is usually not typography. It is that one slide is trying to hold 2 or 3 ideas. Split the slide, or cut the idea. Better structure reduces text density automatically.
| Mistake | What it looks like | Fix |
|---|---|---|
| No clear question | Slides feel informational but aimless | Use SCQA and write the question by slide 3 |
| Proof comes after the ask | Audience resists or doubts | Move proof before the recommendation |
| Too many ideas per slide | Small text and weak recall | Limit each slide to 1 message |
| Weak ending | Audience claps but does not act | End with impact, decision, or next step |
Frequently asked questions
What is the best presentation structure example for beginners?
The easiest starting point is a 7-slide structure: title, why this matters, point 1, point 2, point 3, summary, next step. It is simple enough for a first presentation but still gives the audience a clear beginning, middle, and end.
What is a good presentation structure example for a business pitch?
A strong business pitch structure is problem, stakes, solution, how it works, proof, business model or pricing, and ask. For investor pitches, Guy Kawasaki's 2021 rule of 10 slides in 20 minutes is a useful starting model.
What is a good presentation structure example for a project update?
Use 6 slides: goal, status summary, progress against milestones, risks, decisions needed, next 30 days. This works because it puts the action point before discussion drifts into low-value detail.
What is a good presentation structure example for a research talk?
Use the Hourglass structure from MIT's Communication Lab: broad problem, gap, goal, method, results, impact. MIT also recommends grouping results into 2 to 4 groupings instead of trying to show every data point.
How many slides should a presentation structure example have?
It depends on the format. A pitch often works well at 10 slides, a project update at 5 to 7, a training deck at one slide per step plus intro and recap, and a TED-style talk at 18 minutes or less according to TED Help.
What is SCQA in presentation structure examples?
SCQA stands for Situation, Complication, Question, Answer. It is a business storytelling structure that sets context, introduces tension, asks the key question, and then delivers the answer in a way executives can follow quickly.
What is the difference between a presentation outline and a presentation structure?
An outline is the list of parts or slides. A structure is the logic that connects them. For example, an outline might say intro, problem, solution, proof. The structure explains why that order works for the audience.
Can I use the same presentation structure example for every talk?
No. Reuse the framework, not the exact order every time. A sales pitch, research talk, and training session each need a different flow because the audience wants a different outcome.
AnyGen





