The five narrative frameworks that make presentations persuasive — and when to use each one
Most AI-generated presentations are forgettable because they have no persuasive logic. Choosing the right narrative framework before generating changes the slide order, the tone, and the closing argument — and it takes 10 seconds to decide.
The problem with structure-free presentations
Ask most AI tools to generate a presentation about a topic and you'll get organised information — probably accurate, probably well-formatted, almost certainly not persuasive.
Persuasion isn't about having the right facts. It's about sequencing them in a way that creates emotional momentum: a problem the audience recognises, stakes that make them care, evidence that builds confidence, and a conclusion that makes the next step feel obvious.
A deck with no narrative framework is a collection of points. A deck with the right framework is an argument.
Slides Lab builds the framework into the generation step itself. You choose before the AI writes a single slide. Here's how to decide.
PAS — Problem → Agitation → Solution
What it does: Opens by naming a specific pain, then dwells in it — making the stakes feel real and urgent — before presenting the solution.
When to use it: Cold outreach, pitches to audiences who don't yet believe they have the problem, sales decks for competitive markets.
Why it works: People don't act when they understand they have a problem. They act when they feel it. The Agitation phase converts intellectual awareness into emotional urgency.
Example arc:
- Slide 1–3: The problem (specific, relatable, costed)
- Slide 4–6: The agitation (what happens if nothing changes, who else is affected, what it's already cost)
- Slide 7–10: The solution with evidence
Mistake to avoid: Don't rush to the solution. The agitation phase does most of the persuasive work. If the audience doesn't feel the problem by slide 6, the solution won't land.
BAB — Before → After → Bridge
What it does: Starts from the current reality, paints the desired future state, then explains the exact path between them.
When to use it: Change proposals, transformation pitches, product demos where the audience already knows they want improvement but hasn't committed to a specific approach.
Why it works: The Before slide creates identification — the audience sees themselves in it. The After slide creates desire — they want to be there. The Bridge slide answers the only remaining question: how.
Example arc:
- Slide 1–3: Before — the current state (grounded in specifics, not generalities)
- Slide 4–6: After — the desired state (concrete outcomes, not aspirational language)
- Slide 7–10: Bridge — the steps, tools, or changes that connect them
Mistake to avoid: The After state needs to be concrete. "A more productive team" is aspirational. "30% fewer status meetings, with every project tracked in one place" is a destination.
Feature Presentation
What it does: Leads with a clear product or idea overview, then dedicates slides to each key capability in depth.
When to use it: Product launches, technical audiences, stakeholders who need to understand what something does before they can evaluate it, onboarding decks.
Why it works: For audiences evaluating a product, the persuasive work happens at the feature level. They need enough detail to imagine using it. The framework builds that depth systematically.
Example arc:
- Slide 1–2: What it is (clear, jargon-free one-sentence description)
- Slide 3–8: Feature-by-feature walkthrough (one major capability per slide)
- Slide 9–10: Summary of what's possible + CTA
Mistake to avoid: Don't list every feature — select the 4–6 that address the audience's primary concerns. A deck that tries to cover everything convinces no one of anything specific.
Social Proof Cascade
What it does: Opens with the outcome ("here's what this made possible"), then layers in the evidence that validates it — numbers, case studies, testimonials, third-party recognition.
When to use it: Pitches to investors and buyers who are risk-averse, any situation where credibility is the main obstacle, re-pitching after an initial rejection.
Why it works: Sceptical audiences stop listening when you tell them what your product does. They start listening when you show them what it has already done for people they recognise.
Example arc:
- Slide 1: The headline result (the most compelling outcome, stated plainly)
- Slide 2–4: Quantified evidence (numbers, growth, before/after)
- Slide 5–7: Case studies (specific, named if possible)
- Slide 8–9: Testimonials or third-party validation
- Slide 10: CTA built on the established credibility
Mistake to avoid: Don't open with who you are. Open with what you've done. Context and credentials belong in the middle, not at the start.
Objection Handling
What it does: Structures the entire presentation around the objections the audience will raise — naming each one and dismantling it before they can voice it.
When to use it: High-stakes decisions, budget approval decks, re-engagement after a deal stalled, any situation where the audience has pre-formed resistance.
Why it works: When you name an objection before the audience does, three things happen: they feel understood, their guard drops slightly, and your credibility increases because you're clearly not hiding anything.
Example arc:
- Slide 1–2: The core proposal (brief — the audience knows why they're here)
- Slide 3: Objection 1 + response
- Slide 5: Objection 2 + response
- Slide 7: Objection 3 + response
- Slide 9–10: Summary + risk-reducing CTA
Mistake to avoid: Don't get defensive in your objection responses. State the objection fairly — even more strongly than the audience would — then answer it. The fairness is what makes the answer land.
How to choose in 10 seconds
Before selecting a framework in Slides Lab, ask one question: What is the biggest reason my audience might not act after seeing this deck?
- They don't believe they have a problem → PAS
- They know they want change but haven't committed to an approach → BAB
- They need to understand what it does before they can evaluate it → Feature Presentation
- They're sceptical that it works → Social Proof Cascade
- They have specific objections they'll raise → Objection Handling