Aidar Akmaev
Disclosure: NOXI publishes this guide and is one of the tools it mentions; the method works in any presentation software.
Quick answer: Structure a presentation around what the audience must do when it ends. Write that action and your main message in one sentence each, then pick the matching framework: answer first (the pyramid principle with SCQA) for a decision, options then recommendation for a choice, problem–solution–benefit for a change, a status structure for progress, explain-and-teach for a skill, and a story arc for a new direction. Group the content into three to five sections, give every slide a full-sentence title, and check that the titles alone tell the story.
"Beginning, middle and end" is true of every presentation, so it decides nothing. The decisions that matter are which order the middle takes, what goes on the first slide and what the last slide asks for. This guide gives you a framework chooser, outlines for six structures, a 10-step build process, the ghost-deck test and one recommendation shown weak and strong.
In short
- StartWrite the audience's next action in one sentence: "After this, [who] will [do what] by [when]."
- FrameworkSix structures cover most talks. Choose by that action, not by topic and not by the order in which you did the work.
- SectionsThree to five groups under one message, each answering a question the audience will ask.
- TitlesOne full-sentence finding per slide; read the titles alone, as a ghost deck, before you design anything.
- Open and closePurpose and main message or ask in the first minute; end on the decision or next step, never on "Questions?".
- TimeIn a decision meeting, present for 70–80% of the slot and keep the rest for discussion.
What is presentation structure?
Presentation structure is the order in which you reveal your message, its supporting points and their evidence, chosen so the audience can act when you finish. It works at three levels: one message, three to five sections, and one point per slide.
| Level | What it is | How to test it |
|---|---|---|
| Message | The one sentence the audience should remember or act on | Can you say it in 25 words or fewer, without "and also"? |
| Sections | Three to five groups, each answering one question the audience will ask | Does each section's one-line summary support the message? |
| Slides | One point per slide, stated in the title | Does the body of the slide prove its title, and nothing else? |
The limit of three to five sections is practical. Working-memory research puts the number of meaningful items young adults can hold in mind at once at about three to five (Cowan, 2010), and a listener cannot scroll back.
Start with what the audience must do next
The audience's next action decides the structure. Before you choose a framework or open any slide software, write one sentence: "After this presentation, [audience] will [action] by [time]."
A topic ("an update on support") does not tell you the order, the level of detail or the ending; an action does. If you cannot name one, send an email instead.
| Topic goal | Action sentence | Framework it points to |
|---|---|---|
| Update leadership on support | "The COO approves a $60,000 budget and a January start today." | Answer first |
| Present the CRM options | "The steering group chooses one CRM option at this meeting." | Options, then recommendation |
| Introduce the supplier portal | "Finance leads agree to move their top 50 suppliers by March." | Problem, solution, benefit |
| Report on the project | "The sponsor approves two extra analysts to recover a one-week slip." | Status update |
| Train new hires on expenses | "New hires submit a correct claim in their first week." | Explain and teach |
| Share the strategy | "Each team lead names one project to stop by Friday." | Story arc |
Three more facts refine the choice: what the audience believes now (a receptive room can take the answer at once; a skeptical one must first agree there is a problem), whether the deck will be presented, read as a pre-read or both, and how much of the slot will go to discussion.
The framework chooser: six presentation structures and when to use each
Six structures cover almost every business, academic and public presentation. Choose the one that matches the audience's next action, use it for the whole deck, and let individual sections borrow another structure where they need it.
| Structure | Use when the audience must | Typical presentations | Opens with | Watch out for |
|---|---|---|---|---|
| Answer first (pyramid, SCQA) | Decide, approve or agree | Recommendations, business cases, board papers, executive updates | The answer and the ask | A skeptical room may need the problem agreed before the answer |
| Options, then recommendation | Choose between real alternatives | Vendor selection, strategic options, investment choices | The decision and the criteria | Straw-man options; leaving out "do nothing" |
| Problem, solution, benefit | Accept a change they did not ask for | Change proposals, sales pitches, new policies | The problem in their terms | A solution looking for a problem; benefits without proof |
| Status update | Track progress and act on exceptions | Project reports, quarterly reviews, monthly operations reviews | Overall status and decisions needed | An activity list that hides the one item at risk |
| Explain and teach | Understand or do something new | Training, onboarding, technical explanations, lectures | What they will be able to do | Covering everything instead of the steps that matter |
| Story arc | Commit to a direction or a belief | Keynotes, all-hands meetings, vision talks | The world as it is today | No concrete ask; emotion without evidence |
Nesting is normal: a status update can hold a problem–solution section for the workstream that is off track. Switching the top-level structure halfway through is not. If you are unsure, answer first is the safest default for a business audience.
Answer first: the pyramid principle and SCQA
Answer first means the recommendation or main finding comes in the first minute and the rest of the presentation proves it. It is the right default for decisions and senior audiences, because people who have to act need the conclusion before the reasons.
Minto applies the pyramid to presentations as well as documents (Barbara Minto: the pyramid principle concept) and presents the SCQ framework as the way to identify the question in the reader's mind (barbaraminto.com). Military writing reaches the same rule: the US Army names "bottom line up front" as one of two essential requirements of Army writing (AR 25-50, paragraph 1-38).
Answer-first outline template
| Slide | Job | What goes on it |
|---|---|---|
| 1 | Answer and ask | The recommendation in one sentence, what it achieves, what you need and by when |
| 2 | Situation and complication | What the audience already accepts, what changed, and the question it raises |
| 3–4 | Key line 1 | The first reason the answer is right, usually "it works", with evidence |
| 5 | Key line 2 | The second reason, often "it beats the alternatives" |
| 6 | Key line 3 | The third reason, often feasibility: people, cost, time |
| 7 | Risks | What could go wrong, and who owns each response |
| 8 | Decision and next steps | The ask restated, owners, dates, and how success will be measured |
| Appendix | Backup | Data, method, and answers to the questions you expect |
Keep the key lines the same kind of idea (all reasons, all steps or all parts); Minto's course stresses that "three reasons" must be exactly three valid reasons that add up to an insight (Barbara Minto: the course). If the room is likely to reject the answer on sight, agree the situation and complication on slide 1 and give the answer on slide 2. Our board meeting presentation guide applies this order to a full board deck.
Problem, solution, benefit: for a change the audience did not ask for
Use problem–solution–benefit when the audience must accept a change they did not request. Lead with the problem in their terms, show its cause, then the solution, the benefit and the ask; a solution only feels welcome once the audience agrees there is a problem.
| Slide | Job | What goes on it |
|---|---|---|
| 1 | The problem | What is going wrong, for whom, and how it is measured |
| 2 | Why now | The cost of waiting; what happens if nothing changes |
| 3 | The cause | Why it happens; the solution must address this, not the symptom |
| 4 | The solution | What changes, in plain words |
| 5 | Proof | A pilot, a comparable case, data or a demonstration |
| 6 | Benefits | What the audience gains, in the measures they use |
| 7 | Objections | The two or three concerns you expect, answered |
| 8 | The ask | The action, the first step and the date |
Public-speaking courses teach a longer persuasive version, Monroe's motivated sequence: attention, need, satisfaction, visualization and action. An open public-speaking textbook notes that little experimental research supports it over other patterns; the one test it cites found no extra persuasive effect, although audiences rated the speeches as better organized (Stand Up, Speak Out, section 17.3). Use it as a planning checklist, not a formula, and never skip the cause: a fix aimed at the symptom fails when the cause is something else.
Options, then recommendation: when the audience must choose
When the audience must choose, agree the criteria first, compare every realistic option on the same criteria, including doing nothing, and then recommend one. Criteria agreed before the options appear make the comparison credible, because the audience can see the winner was not picked first and justified afterwards.
| Slide | Job | What goes on it |
|---|---|---|
| 1 | The decision | What must be decided, by when, and why now |
| 2 | Criteria | How the options will be judged, with weights if you use them |
| 3 | Options | Business as usual, a minimum option and two or three real alternatives |
| 4 | Comparison | One table: every option scored on every criterion, from the same sources |
| 5 | Recommendation | The option you recommend and the deciding reason |
| 6 | Trade-offs and risks | What the recommendation gives up and how its risks are handled |
| 7 | The ask | The decision, the budget and the first step |
Always include the baseline. The UK Treasury's appraisal guidance requires the business-as-usual option to go through to the shortlist as the benchmark for every other option, and suggests a shortlist of around five that includes a "do minimum" option (HM Treasury, The Green Book 2026, paragraphs 2.16 and 5.17–5.18). It is written for public spending, but the logic holds in any meeting: without a baseline, nobody can judge whether your option is worth its cost.
Criteria first suits a neutral facilitator or a distrustful audience. When the audience expects your view, put the recommendation on slide 1 and use the comparison as one of its key lines.
Status update: lead with the overall status and the exceptions
A status presentation states the overall status and any decision needed first, then what is done, what is at risk and what comes next. People reviewing progress scan for exceptions, so put them before the activity list.
| Slide | Job | What goes on it |
|---|---|---|
| 1 | Status and decisions | On track, at risk or off track against the plan, and any decision needed today |
| 2 | Progress against plan | Milestones and measures, planned against actual |
| 3 | At risk | Issues and risks, each with its impact, owner and fix |
| 4 | Help needed | What you need from this audience: approval, people, a decision |
| 5 | Next period | The next milestones and their dates |
| Appendix | Detail | The full milestone list, budget detail, completed work |
Chronological order belongs inside sections, such as an incident timeline, not at the top, where it buries the item at risk. Keep the same structure every period so that changes stand out. Our project status report guide covers the one-slide status, red-amber-green thresholds and the steering committee deck.
Explain and teach: build understanding in the order people learn
For training, onboarding and technical explanations, structure the talk around what the audience must be able to do afterwards: the goal, the core idea, a worked example, practice and a recap. Teach the few steps that matter and send the rest as reference material.
| Slide | Job | What goes on it |
|---|---|---|
| 1 | The outcome | What they will be able to do by the end, in one sentence |
| 2 | Why it matters | The mistake or problem this prevents |
| 3 | The core idea | One concept, model or rule, shown as a picture |
| 4 | Worked example | One real case, walked through step by step |
| 5 | Practice | A short exercise or question the audience answers |
| 6 | Common mistakes | The two or three errors to avoid |
| 7 | Recap and reference | The steps on one slide, and where to find the detail |
Each step depends on the one before it. When the audience is senior and the goal is a decision, the explanation becomes one section of an answer-first deck; our guide to explaining a technical project to executives shows how, and the webinar structure guide adapts this order to a 45-minute online session.
Story arc: contrast what is with what could be
Use a story arc when the audience must commit to a direction rather than approve a specific item. Describe the world as it is, contrast it with what could be, move between the two, and end with a call to action and a picture of the future once the change is made.
Nancy Duarte described this shape in her 2011 TEDxEast talk: establish "what is", contrast it with "what could be", move back and forth, and finish with a call to action and the world with the idea adopted (Nancy Duarte, The secret structure of great talks).
| Slide | Job | What goes on it |
|---|---|---|
| 1 | What is | The current reality, in terms the audience recognizes |
| 2 | What could be | The better future, made concrete |
| 3–5 | Contrasts | Today's problem against the future solved, one pair per slide, each with evidence |
| 6 | The obstacles | What stands in the way and how it will be handled |
| 7 | Call to action | What each person should do, starting when |
| 8 | The new normal | A specific picture of the future once the change is made |
A story arc without a concrete ask is a pep talk; give every "what could be" slide one fact that makes it believable.
Build the structure in 10 steps
Build the structure before the slides: write the action and the message, choose the framework, group the content into three to five sections, write one full-sentence title per slide, test the titles as a ghost deck, and only then fill the slides with evidence. Steps 1 to 8 need no slide software.
| Step | What you do | What you have at the end |
|---|---|---|
| 1 | Write the audience's next action | One sentence: who does what, by when |
| 2 | Write the message | One sentence of 25 words or fewer that, remembered alone, leads to that action |
| 3 | Choose the framework | One structure from the chooser for the whole deck |
| 4 | List the audience's questions | The five to ten questions they will ask, in their words |
| 5 | Group the questions into sections | Three to five sections, each with a one-line summary that supports the message |
| 6 | Order the sections | The framework's order; inside a section, by importance, time or sequence |
| 7 | Write the ghost deck | One full-sentence title per slide, with a sketch of the evidence it needs |
| 8 | Read the titles alone | A sequence that tells the whole story; merge, cut or add slides until it does |
| 9 | Budget time and slides | Minutes per section, with discussion time reserved |
| 10 | Fill the slides, then write the opening and close | Evidence that proves each title, an appendix for the rest, and a scripted first and last minute |
Step 4 is the one most people skip, and it is what fits the structure to the audience. Write the questions in their words: "Will this need more people?", not "Resourcing implications." For step 9, our slides-per-minute table converts a time slot into a realistic slide count.
Write action titles and test them as a ghost deck
An action title is a full-sentence slide title that states the slide's conclusion; a ghost deck is the sequence of those titles written before any slide is designed. If the titles alone tell the story in order, the structure works; if they do not, no amount of design will fix it.
There is experimental support for sentence titles. Among 110 engineering students who heard the same technical presentation with different slides, those whose slides used a sentence headline supported by visual evidence showed better comprehension, fewer misconceptions and lower perceived mental effort than those shown topic-and-bullet slides, and recalled more at a delayed test (Garner and Alley, 2013). It comes from the approach's developers and a student sample, so treat it as support, not final proof.
A title that hides the finding can be costly. The Columbia Accident Investigation Board's 2003 report examined a briefing slide titled "Review of Test Data Indicates Conservatism for Tile Penetration". It notes that the title referred to the test models rather than the predicted damage, and that the key fact, an estimate of the debris hundreds of times larger than the data behind the model, appeared only near the bottom of a slide with six levels of bullets (Columbia Accident Investigation Board, Report Volume I, page 191).
Rules for action titles
- A full sentence that states the finding: "Routine tickets are 62% of volume", not "Ticket volume"; a number with its unit beats "significantly".
- Two lines at most, about 15 words; longer usually means two messages.
- Provable by the slide, and the next sentence of the story after the title before it.
For eight before-and-after rewrites, see our guide to consulting-style slides.
The ghost-deck test
- Slide 1 carries the message and the ask.Someone who leaves after one minute knows what you want.
- The titles read as one argument.You can join neighboring titles with "because", "so", "but" or "and then".
- No title is a label."Background", "Data" and "Next steps" become sentences or disappear.
- Every title can be proved.A title you cannot prove changes or goes.
- A colleague from the audience gets it in two minutes.From the titles alone, they can state the ask and the main reason.
Worked example: one recommendation in two structures
The same content can fail or succeed depending only on its order. Here a support team presents one recommendation twice, first in the order the team did the work and then answer first, with the same facts and the same 20-minute slot.
Version A: the order of work
| Slides | Titles | What the audience experiences |
|---|---|---|
| 1–2 | Customer Support Review; Agenda | A topic and a list of topics; no reason to listen yet |
| 3–5 | Background: our team; Ticket volume analysis; Satisfaction trends | Charts without a point; the COO asks "what are you proposing?" |
| 6–7 | The pilot; Pilot results | Good evidence for an idea not yet named |
| 8–9 | Options we looked at; The two-tier model | The recommendation first appears on slide 9, about 13 minutes in |
| 10–12 | Costs and staffing; Next steps; Questions? | The ask arrives at about minute 17; discussion gets the last 3 |
At about 1.7 minutes per slide (20 minutes over 12 slides), slide 9 starts about 13 minutes in. Every fact in version A is correct; the structure is what fails.
Version B: answer first
| Slide | Action title | What proves it | Part |
|---|---|---|---|
| 1 | Two support tiers would answer routine tickets in under 2 hours, with no new hires | The ask: $60,000 one-off and a 12-week rollout from 5 January 2027 | Answer and ask |
| 2 | One shared queue makes 11,160 routine tickets a month wait behind 6,840 technical ones | 18,000 tickets a month; median first response 9 hours; satisfaction 78% | Situation, complication |
| 3 | A six-week Payroll pilot cut routine first response from 9 hours to 1.5 | 4,500 tickets; technical resolution 3.2 to 2.1 days; satisfaction 84% against 78% | Key line 1: it works |
| 4 | Tier 1 resolves routine tickets so Tier 2 specialists take only technical work | Routing flow: triage rules, two queues, one-click transfer | Key line 1: how |
| 5 | Two tiers beat hiring four agents or adding a chatbot on cost and speed | Options table including business as usual | Key line 2: best option |
| 6 | Today's 24 people cover both tiers: 9 in Tier 1 and 15 in Tier 2, split by workload | Handling hours: 1,116 routine, 2,052 technical | Key line 3: feasible |
| 7 | Misrouting and Tier 1 turnover are the main risks, and both have owners | 7% misrouted in the pilot, target under 5% by week 8; a path from Tier 1 into Tier 2 | Risks |
| 8 | A 12-week rollout puts all four product lines on two tiers by 30 March 2027 | Payroll done in the pilot; weeks 1–2 training and routing, 3–5 Time & Attendance, 6–8 HR Records, 9–12 Integrations | Plan |
| 9 | Approve $60,000 and the 5 January start today; we report four measures on 13 April | Decision, owner, success measures | Decision |
The options slide (slide 5) uses the same criteria for every option:
| Option | Cost | Routine first response | Basis |
|---|---|---|---|
| Business as usual | $0 | 9 hours | Current median |
| Hire four agents | $208,000 a year (4 × $52,000) | About 7 hours | Queue-model estimate |
| Self-service chatbot | $45,000 a year | About 8 hours | Estimate; deflects about 10% of routine tickets (1,116 a month) |
| Two tiers (recommended) | $60,000 one-off ($38,000 training + $22,000 routing set-up) | 1.5 hours in the pilot; target under 2 | Six-week pilot, 4,500 tickets |
Check the arithmetic before the meeting, because a decision-maker who finds one wrong number stops trusting the rest. The ticket types add up: 11,160 + 6,840 = 18,000. The staffing split follows workload, not ticket count: at about 6 minutes per routine ticket and 18 per technical one, routine work is 1,116 hours a month and technical work 2,052, so technical work is 65% of the 3,168 hours, which is why Tier 2 gets 15 of the 24 people. The pilot's 7% misrouting is 315 of 4,500 tickets, and 12 weeks from 5 January 2027 ends on 30 March 2027.
In version B, slide 1 takes 2 minutes, slides 2 to 8 about 10 and slide 9 another 2, leaving 6 for discussion; a COO called away after five minutes has already heard the recommendation, the evidence and the ask. Slide 9 lists the four measures for the 13 April review: routine first response under 2 hours, technical resolution under 2.5 days, misrouting under 5% and satisfaction of 82% or more.
To see the answer-first version as finished slides, we generated it as a deck in NOXI from the nine titles and their numbers above and exported it to PDF without edits. Two of its slides:
How to open and end a presentation
Open with the purpose and the main message or ask within the first minute, then a short roadmap of the sections. End by restating the message, the ask and the next steps with owners and dates, and take questions before the final slide so that your last word is the message, not the last question.
| Moment | What to say | What to avoid |
|---|---|---|
| First minute | Why the audience is here, the message or ask, and the three to five sections as the questions they answer | A long introduction of yourself; an agenda of topic labels |
| Hook | A story, number or question that leads straight to the message | A three-minute anecdote that connects to nothing |
| Last two minutes | The message and key lines in one sentence each, then the decision, owner, date and first step | New content, or rushing because the body overran |
| Final slide | The ask, shown again after questions | "Thank you" or "Questions?" in the position people remember best |
Time budget for a decision meeting
| Slot | Opening | Body | Close | Discussion |
|---|---|---|---|---|
| 10 minutes | 1 minute | 6 minutes | 1 minute | 2 minutes |
| 20 minutes | 2 minutes | 10 minutes | 2 minutes | 6 minutes |
| 30 minutes | 3 minutes | 17 minutes | 2 minutes | 8 minutes |
| 60 minutes | 5 minutes | 35 minutes | 5 minutes | 15 minutes |
These are rules of thumb for meetings that end in a decision. With no discussion, move that time into the body; when the deck was sent in advance, move body time into discussion.
How to make a presentation flow between sections
A presentation flows when each section ends by answering its question and the next begins by naming the question it will answer. Make the logic audible with short bridge sentences, and show the structure on screen without filling the deck with divider slides.
| Bridge | When to use it | Example from the worked example |
|---|---|---|
| So | The next section follows from this one | "Routine tickets wait behind technical ones. So what happened when we separated them?" |
| But | The next section tests or qualifies this one | "The pilot worked. But would hiring have been cheaper?" |
| Which means | The next section draws the implication | "Technical work is 65% of handling time, which means Tier 2 needs 15 people." |
A small section label on each slide is usually enough; keep divider slides for the major parts of a long talk. If a bridge has to start with "also", the two sections may belong together.
Adapt the structure to the room
Keep the framework and change its proportions when the slot shrinks, when the deck will be read rather than presented, or when the audience is skeptical. A well-built structure survives being cut to five minutes, because the message is on the first slide.
| Situation | What to change | Why |
|---|---|---|
| Your 20 minutes become 5 | Present slide 1, one slide per key line and the decision slide; point to the rest as backup | Slide 1 already carries the message and the ask |
| The deck is a pre-read | Full-sentence titles, more explanatory text per slide, a summary that stands alone, detail in the appendix | No presenter is there to fill the gaps |
| Skeptical audience | Agree the situation and complication first; answer the main objections inside the body, not in Q&A | An answer is easier to hear once the problem is shared |
| Mixed expertise | Pitch the main deck at the decision-maker; put technical depth in a backup section | Experts can read the backup; the decision-maker cannot skip ahead |
| Recurring meeting | Use the same structure every time | Changes since last time stand out |
| Online meeting | Shorter sections, a visible section tracker, a check-in question between sections | You cannot see who has drifted, so check in on purpose |
Design should make the structure visible; our guide to professional presentation design covers the layout, type and color rules that do that.
3 AI prompts for structuring a presentation
Use them in NOXI, or in any AI tool, after you have written the action sentence and the ghost deck. Replace the brackets.
Create a [9]-slide presentation for [the COO and the CFO], who must [approve a $60,000 budget and a 5 January start] in a [20]-minute [operations review]. Use an answer-first structure: recommendation and ask, situation and complication, three key lines with evidence, risks, plan, decision. Use these slide titles exactly: [paste your ghost-deck titles]. Prove each title with [the attached data]. Do not invent numbers; mark anything missing as [to confirm].
Restructure the attached deck for [audience], who must [action] by [date]. Use the [options, then recommendation] structure, with business as usual among the options. Rewrite every slide title as a full-sentence finding of 15 words or fewer. Put the recommendation and the ask on slide 1 and repeat them on the last slide. Move slides that do not support the message to an appendix. Keep every number unchanged.
Make a [5]-minute version of this deck for [audience]. Keep slide 1 with the answer and the ask, one slide for each of the [three] key lines, and the decision slide. Move everything else to an appendix. Keep every title a full sentence and every number unchanged, and end on the ask with [owner] and [date].
How to build a well-structured deck in NOXI
NOXI turns a structured brief into a full deck and can restructure a deck you already have. It is free, with no card and no watermark; uploading files needs a free account, and a full deck uses about 25 of the 1,000 monthly credits.
Step 1: Write the brief
Put the action sentence, the message and your ghost-deck titles in a short document, and attach it with any supporting data. NOXI accepts PDF, Word, PowerPoint, Excel, CSV, text and image files up to 200 MB each.
Step 2: Match your template
Choose Match reference and attach your company PowerPoint template, a previous deck as PPTX or PDF, or a screenshot of one slide. NOXI builds the new deck in that style.
Step 3: Review the outline first
Paste Prompt 1 and choose Plan mode to review the outline before anything is generated. Read the titles alone, as a ghost deck, and fix them; then generate and watch each slide being built.
Step 4: Refine slides with AI
Ask for changes to one slide or the whole deck in plain English or Arabic, such as "rewrite every title as a full-sentence finding." Click any element and tell the AI what to change; text, tables and chart numbers are editable on the slide.
Step 5: Restructure or shorten
To fix a deck you already have, attach it and use Prompt 2; NOXI can restructure, complete or reformat an existing deck. For the five-minute version, make a copy from version history and use Prompt 3 on the copy.
Step 6: Test, export and present
Invite one person from the audience by email to read the titles and edit with you in real time, or share a view-only link. Download an editable PowerPoint (.pptx) or a PDF, free and with no watermark, or present full-screen from NOXI.
Frequently asked questions
- What is the best structure for a presentation?
- The best structure is the one that matches what the audience must do afterwards. Use answer first for a decision, options then recommendation for a choice, problem–solution–benefit for a change, a status structure for a progress report, explain-and-teach for training and a story arc for a new direction. For a business audience, answer first is the safest default.
- What are the main parts of a presentation?
- A presentation has five working parts: an opening that states the purpose and the main message or ask, a short roadmap, a body of three to five sections that each answer one audience question, a close that restates the message, the ask and the next steps, and time for questions or discussion. An appendix holds the detail.
- What is the SCQA framework?
- SCQA stands for situation, complication, question and answer. It is a four-part opening: a situation the audience accepts, what changed or went wrong, the question that change raises, and your answer, which becomes the main message. For example: support runs one queue; routine tickets now wait 9 hours; how do we answer faster without hiring; split support into two tiers.
- What is the pyramid principle in presentations?
- The pyramid principle, developed by Barbara Minto, puts one main message at the top, supported by a small group of key points, each backed by evidence. In a presentation, the message goes on the first slide, the key points become the sections, and the evidence fills the slides. It suits decisions and senior audiences, who need the conclusion before the reasons.
- How do you start a presentation?
- In the first minute, say why the audience is there, give your main message or ask, and preview the three to five sections, ideally as the questions they will answer. Keep any introduction of yourself to one line. A story or a striking number can open the talk if it leads straight to the message.
- How do you end a presentation?
- Restate the main message and the key points in one sentence each, then make the ask: the decision, the owner, the date and the first step. Take questions before the final slide and return to it afterwards, so the last thing the audience hears is your message. Do not end on a "Thank you" or "Questions?" slide.
- How many main points should a presentation have?
- Three to five main points, grouped under one message, suit most presentations. Working-memory research suggests people can hold about three to five meaningful items in mind at once, and listeners cannot scroll back. If you have more, group related points under a broader one or move the less important ones to backup slides.
- How do you make a presentation flow?
- Write slide titles as full sentences that follow from one another, then link sections with bridge sentences such as "So what happened when we tried it?" or "But would hiring have been cheaper?". Each section should end by answering its question, and the next should begin by naming the question it answers.
Sources & methodology
How this guide was made: it applies the cited sources on argument structure, slide titles and persuasive speaking to everyday presentation practice. The framework chooser, the outline templates, the 10-step process, the time budgets and the checklists are editorial recommendations, not published standards. Fenmore Software and every name and figure in the worked example are fictional. All sources were checked on 9 October 2026.
- [1] The pyramid principle as a way of organizing ideas under a single thought, for documents and presentations; the SCQ framework for identifying the reader's question — Barbara Minto, The Minto Pyramid Principle concept; Barbara Minto, home page.
- [2] Checking that a grouping such as "three reasons" contains exactly three valid reasons and a real insight — Barbara Minto, the Minto Pyramid Principle course.
- [3] "Bottom line up front" as one of two essential requirements of Army writing, paragraph 1-38 — US Army, AR 25-50 Preparing and Managing Correspondence (10 October 2020, administrative revision 4 October 2024).
- [4] Sentence headlines with visual evidence: better comprehension, fewer misconceptions, lower perceived load and stronger delayed recall among 110 engineering students — Garner and Alley, How the Design of Presentation Slides Affects Audience Comprehension, International Journal of Engineering Education 29(6), 2013.
- [5] The briefing slide whose title and six-level bullet structure obscured the key finding — Columbia Accident Investigation Board, Report Volume I (August 2003), "Engineering by Viewgraphs", page 191.
- [6] The "what is / what could be" shape, ending with a call to action and the future with the idea adopted — Nancy Duarte, The secret structure of great talks, TEDxEast (November 2011), transcript.
- [7] Monroe's motivated sequence and the limited experimental evidence for it — Stand Up, Speak Out: The Practice and Ethics of Public Speaking, section 17.3 (LibreTexts, CC BY-NC-SA 3.0).
- [8] Business as usual carried to the shortlist as a benchmark; a shortlist of around five including a "do minimum" option, paragraphs 2.16 and 5.17–5.18 — HM Treasury, The Green Book (2026).
- [9] A central working-memory store limited to about three to five meaningful items in young adults — Nelson Cowan, The Magical Mystery Four, Current Directions in Psychological Science 19, 2010.
Build your next structured deck in NOXI, free: start from your ghost deck, review the outline before generating, match your company template, and export an editable PowerPoint or PDF.
