Story Framework
Problem → Solution
Classic business arc: name the pain, raise the stakes, present your fix, show how it works, prove it, ask. The default for sales decks, internal proposals, and most general business presentations.
Beat Diagram
- 1Hookstatement
- 2The Problem
- 3Why It Matters
- 4The Solution
- 5How It Works
- 6Proof
- 7The Asklist
OPF Config
narratives:problem-solution{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "PPTX.gallery — narratives/problem-solution",
"narrative": "problem-solution",
"tags": [
"gallery:narratives/problem-solution"
],
"slides": [
{
"id": "gallery-preview-1",
"layout": "text",
"title": "Narrative preview",
"subtitle": "Storyline scaffolded by the \"problem-solution\" narrative."
}
],
"catalogs": {
"default": {
"source": "https://www.pptx.gallery",
"narratives": {
"problem-solution": {
"name": "Problem → Solution",
"summary": "Classic business arc: name the pain, raise the stakes, present your fix, show how it works, prove it, ask. The default for sales decks, internal proposals, and most general business presentations.",
"audienceFit": [
"customers",
"stakeholders",
"executives",
"internal-teams"
],
"duration": {
"min": 5,
"max": 30
},
"tags": [
"business",
"sales",
"general",
"proposal"
],
"beats": [
{
"id": "hook",
"name": "Hook",
"description": "Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.",
"layout": "statement"
},
{
"id": "problem",
"name": "The Problem",
"description": "Name the pain in concrete terms. Make it visceral and specific — describe who hurts, how, and what they're trying to do today that isn't working. Avoid abstractions; use real examples or scenarios the audience recognizes."
},
{
"id": "stakes",
"name": "Why It Matters",
"description": "Quantify the cost of inaction or the upside of action. Use numbers, trends, customer impact, competitive pressure — whatever makes the audience feel the size of the problem and care about solving it now rather than later."
},
{
"id": "solution",
"name": "The Solution",
"description": "Reveal your approach and what it produces for the customer. Lead with the outcome, not the architecture. Keep it concrete: what does the audience get, and what changes for them?"
},
{
"id": "mechanism",
"name": "How It Works",
"description": "Show the moving parts that make the solution credible. Walk through the key mechanism, workflow, or technical insight that explains why this approach succeeds where others have failed. Enough detail to earn trust; not so much that you lose the room."
},
{
"id": "evidence",
"name": "Proof",
"description": "Demonstrate the solution works. Use customer logos, before/after metrics, demos, case studies, third-party validation — whatever de-risks the claim. One strong piece of proof beats three weak ones."
},
{
"id": "ask",
"name": "The Ask",
"description": "State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.",
"layout": "list"
}
]
}
},
"layouts": {
"text": {
"name": "Text",
"summary": "Prose. Several blocks sit side by side when short and stack when long.",
"tags": [
"Text"
],
"direction": "column",
"regions": [
{
"name": "title"
},
{
"name": "body",
"accepts": [
"text",
"list",
"quote",
"code",
"group"
],
"role": "primary",
"flow": "auto"
}
],
"description": "Explain one idea in continuous prose. Use paragraphs or flowing blocks for detail that needs to be read in sequence.",
"preview": {
"vectorSrc": "https://www.pptx.gallery/layout-previews/text.svg"
}
}
}
}
}
}Load this config in the gallery's visual editor, or in the Inspector at pptx.dev.
Pace
6-12 slides
5-30 minutes
7 beats, one slide each
Audience Fit
Tone
Persuasive - positions the presenter as a problem-solver and advocate.
Best For
Sales pitches, proposals, product launches
Example Deck Types
Product pitch, Consulting proposal, Grant application
Example
Begin with a relatable pain point, quantify the cost of inaction, introduce your solution, demonstrate results, and close with next steps.
Beat-by-Beat Guide
Hook
Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.
The Problem
Name the pain in concrete terms. Make it visceral and specific — describe who hurts, how, and what they're trying to do today that isn't working. Avoid abstractions; use real examples or scenarios the audience recognizes.
Why It Matters
Quantify the cost of inaction or the upside of action. Use numbers, trends, customer impact, competitive pressure — whatever makes the audience feel the size of the problem and care about solving it now rather than later.
The Solution
Reveal your approach and what it produces for the customer. Lead with the outcome, not the architecture. Keep it concrete: what does the audience get, and what changes for them?
How It Works
Show the moving parts that make the solution credible. Walk through the key mechanism, workflow, or technical insight that explains why this approach succeeds where others have failed. Enough detail to earn trust; not so much that you lose the room.
Proof
Demonstrate the solution works. Use customer logos, before/after metrics, demos, case studies, third-party validation — whatever de-risks the claim. One strong piece of proof beats three weak ones.
The Ask
State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.