Problem-Solution: The Most Direct Narrative for Persuasion
When your goal is to move an audience from doubt to conviction, the Problem-Solution framework is your most reliable tool. It mirrors how decisions actually get made: someone feels pain, someone offers relief.
This structure works because it earns the solution. You don't ask for buy-in before you've established why it matters.
The Story Arc
1. Hook — Open with something that stops the room. A striking statistic, a question, a short anecdote that frames the territory.
2. Problem — Define the problem with precision. Generic problems produce skeptical audiences. Specific problems ("teams at 200-person companies lose 11 hours per week to manual reporting") produce attentive ones.
3. Implications — Make the cost of inaction concrete. This is the step most presenters skip. Without it, the audience can choose to live with the problem.
4. Solution — Introduce your answer. After three slides of pain, the solution lands with relief rather than suspicion.
5. Benefits — Translate features into outcomes. Not "automated reporting" — "11 hours back per team member, every week."
6. Call to Action — One clear next step. Not "questions?" but "here's what we do next."
When to Use It
Problem-Solution is the right choice when:
- You're pitching a product, service, or initiative to an audience who hasn't committed yet
- The audience may not fully recognize the problem — you need to surface it
- You need a decision at the end of the meeting
- Time is limited and you can't afford narrative complexity
It's less suited for deeply technical audiences who already understand the problem space and want to jump straight to the how.
Example Slide Sequence
| Slide | Content |
|---|---|
| 1 | Title + punchy problem statement |
| 2 | The problem — specific, quantified |
| 3 | Why it's getting worse / cost of inaction |
| 4 | "There's a better way" — transition |
| 5 | The solution, simply explained |
| 6 | Key benefits (3 max) |
| 7 | Social proof or evidence |
| 8 | Clear CTA |
Common Mistakes
Rushing to the solution. Spend real time on the problem. If the audience doesn't feel the pain, they won't value the cure.
Vague implications. "This wastes time" isn't an implication — it's an observation. "This costs your team $400,000 in lost productivity annually" is an implication.
Feature dumping at the solution slide. One clear mechanism, not a feature list. Save the details for follow-up materials.
Generating a Problem-Solution Presentation
Use the PPTX.gallery API to generate a presentation with this narrative structure:
POST /api/generate
{
"narrative": "problem-solution",
"topic": "Your topic here",
"colorScheme": "corporate-trust",
"slides": 8
}
Related: Situation-Complication-Resolution — a more analytical take on the same core structure