Structuring presentations that persuade

0:00 Structuring presentations

Picture a senior leadership meeting. You have fifteen minutes and forty slides. By slide six, the chief executive is checking her phone. By slide twelve, she interrupts: sorry, what are you actually asking us for? That moment happens in boardrooms every day. The problem is rarely the slides. It's the structure. In this lecture, you'll learn to start with the audience and the ask, use proven structures like SCQA, put the executive summary first, design clean slides, and storyboard before you open any software. By the end, you'll have a seven-headline storyboard.

0:40 Why it matters

Why does this matter? Because presentations are often where decisions are made, budgets approved and reputations built. A well-structured presentation lets a busy audience understand your point in the first minute, and then spend the rest of the time on the questions that matter. A poorly structured one wastes everyone's time and can sink a good idea. And structure is a skill you can learn in an afternoon.

1:10 Audience and ask

Here's the first concept. Before you think about slides, answer two questions. Who is the audience: what do they know, what do they care about, and what are they worried about? And what's the ask: what do you want them to think, feel or do at the end? Everything in the presentation should serve that ask. If a slide doesn't move the audience towards it, cut it or move it to an appendix. Here's the key idea: a presentation isn't a report of everything you did. It's an argument for a decision.

1:50 Show the destination first

Here's an analogy. Think of a satnav journey. Before you set off, the screen shows you the destination and the whole route. You know where you're going and roughly how long it'll take. Then it guides you turn by turn. Imagine a satnav that only revealed the destination when you arrived. That's what many presentations do, saving the recommendation for the last slide. Audiences relax when they know the destination. Tell them upfront, then take them there.

2:23 Proven structures

Now proven structures. The most useful for business is SCQA, from Barbara Minto's pyramid principle. Situation: what the audience already accepts. Complication: what's changed or gone wrong. Question: the question that raises. Answer: your recommendation. Other structures work too: problem, solution, benefits; past, present, future; or options compared against criteria. Whichever you choose, put the executive summary first: the answer and the ask on slide one or two. Then the supporting evidence, then the risks, then the ask again.

2:57 Slide design

Next, slide design. Use one message per slide, and write it as the slide title, as a full sentence. Not sales, but sales grew twelve per cent in the Gulf, driven by repeat orders. That's called an action title, and it means someone skimming just the titles gets your whole argument. Keep text minimal. Use visuals that prove the headline, such as a chart, a diagram or a before-and-after. Use consistent fonts and colours, generous white space, and large enough text to read at the back of the room or on a laptop.

3:37 Worked example 1: Mariam in Karachi (illustrative)

A simple worked example. Mariam is a team lead at a bank in Karachi. She wants approval for a new customer onboarding process. Her first draft opens with three slides on the history of onboarding. She restructures with SCQA. Situation: onboarding takes five days. Complication: two competitors now do it in one. Question: how do we close the gap without adding risk? Answer: a digital onboarding pilot for salaried customers. Slide one is the answer and the ask. Her director approves the pilot in the first ten minutes.

4:15 Worked example 2: Ben in Leeds (illustrative)

Now a realistic business scenario, illustrative. Ben is head of marketing at an online homeware brand in Leeds. He needs board approval for an illustrative budget of one hundred and twenty thousand pounds to relaunch the loyalty programme. He writes seven action titles first and reads them aloud to a colleague. She points out that slide four asserts that customers find rewards too slow, with no evidence. He adds exit-survey data. On the day, the board skims the titles in the pre-read, spends the meeting on the margin risk, and approves a capped budget. Structure turned a forty-minute debate into twenty.

4:59 Tailoring to audiences

Different audiences need different emphasis. Executives want the answer, the options, the cost and the risk, in the fewest slides. Technical audiences want to see method and evidence, and they'll test your assumptions. Clients want to see themselves in the story: their problem, their outcome. Mixed audiences benefit from a short main deck and a well-labelled appendix. And for many internal decisions, consider sending a one-page pre-read instead of a long deck. The meeting then starts with questions rather than a performance.

5:35 Watch me: storyboard → outline

Watch me do it. I storyboard an illustrative deck before opening any slide software. Audience: the operations director and finance. Ask: approve an October loyalty relaunch. I write SCQA in four lines, then seven action titles. I read the titles aloud. The argument holds. Then I paste the headlines into an AI assistant and ask for a seven-slide outline, keeping my headlines exactly, one suggested visual each, and flagging where I need data. It suggests a line chart for slide three and flags slide five as needing costs. Then I build the slides, and check every number against the source.

6:18 Measuring success

How do you measure success? Did you get the decision? How early in the meeting was your point understood? How much time went on the questions that mattered, rather than clarifying what you meant? After important presentations, ask one trusted attendee: what was the main message, and what was unclear? If their answer matches your slide one, your structure worked. If not, rework the structure before the next one, not the design.

6:49 Common mistakes

Common mistakes. Starting in the slide software instead of with the audience and the ask. Hiding the recommendation until the end. Slide titles that are labels, not messages. Walls of text you then read aloud. Too many slides for the time. Decorative charts that don't support the point. And using AI to generate a deck from nothing, which produces generic slides that look polished and say very little. Structure is your job. Tools only help you draw it.

7:23 Recap and try this now

Let's recap. Start with the audience and the ask. Use SCQA or another proven structure. Put the answer and the ask first. Write action titles, so the headlines alone tell the story. Design clean slides that prove each headline, and tailor to your audience. Storyboard before you build. Your try this now: for your next presentation, spend thirty minutes writing the SCQA and seven action titles from the lesson, and read the headlines aloud to someone before you open any slide software. Next, we'll look at how to tell honest, clear stories with data.