PPTX.gallery

Story Framework

Data Story

A data-first narrative that builds from evidence to insight to action. Set the analytical context and the question the data answers, reveal the headline finding, walk through the supporting analysis and its sources, explain what it means for the business, then make a specific recommendation with its confidence level and assumptions. The tone is analytical and inductive: it builds up from data to insight. Best for analytical briefings, data team presentations, research readouts, and business reviews; typical decks run 6-15 slides.

Beat Diagram

  1. 1Contextlist / list
  2. 2Key Findingmetrics / metric
  3. 3Analysischart / chart
  4. 4Implicationstwo-column / text
  5. 5Recommendationlist / text

OPF Config

narratives:data-story
OPF JSON
{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "PPTX.gallery — narratives/data-story",
  "narrative": "data-story",
  "tags": [
    "gallery:narratives/data-story"
  ],
  "slides": [
    {
      "id": "gallery-preview-1",
      "layout": "text",
      "title": "Narrative preview",
      "subtitle": "Storyline scaffolded by the \"data-story\" narrative."
    }
  ],
  "catalogs": {
    "default": {
      "source": "https://www.pptx.gallery",
      "narratives": {
        "data-story": {
          "name": "Data Story",
          "summary": "A data-first narrative that builds from evidence to insight to action, ideal for analysts and data-driven teams.",
          "description": "A data-first narrative that builds from evidence to insight to action. Set the analytical context and the question the data answers, reveal the headline finding, walk through the supporting analysis and its sources, explain what it means for the business, then make a specific recommendation with its confidence level and assumptions. The tone is analytical and inductive: it builds up from data to insight. Best for analytical briefings, data team presentations, research readouts, and business reviews; typical decks run 6-15 slides.",
          "audienceFit": [
            "data-teams",
            "operations-and-finance",
            "product-managers",
            "analytics-stakeholders"
          ],
          "duration": {
            "min": 10,
            "max": 30
          },
          "tags": [
            "analytics",
            "data",
            "insight",
            "recommendation"
          ],
          "beats": [
            {
              "id": "context",
              "name": "Context",
              "description": "Frame why this analysis matters now. What question is this data answering?",
              "instructions": "Set up the business question and data scope.",
              "type": "list",
              "layout": "list"
            },
            {
              "id": "key-finding",
              "name": "Key Finding",
              "description": "State the single most important thing the data shows. One slide, one insight.",
              "instructions": "State the one finding the audience must remember.",
              "type": "metric",
              "layout": "metrics"
            },
            {
              "id": "analysis",
              "name": "Analysis",
              "description": "Unpack the data rigorously. Show sources, methodology, and supporting charts.",
              "instructions": "Explain the drivers behind the finding.",
              "type": "chart",
              "layout": "chart"
            },
            {
              "id": "implications",
              "name": "Implications",
              "description": "Translate findings into business language. What does this mean for strategy, operations, or customers?",
              "instructions": "Translate the analysis into business consequences.",
              "type": "text",
              "layout": "two-column"
            },
            {
              "id": "recommendation",
              "name": "Recommendation",
              "description": "Make an explicit, actionable recommendation backed by the data. Include confidence level and assumptions.",
              "instructions": "Recommend the next decision or action.",
              "type": "text",
              "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"
          }
        }
      }
    }
  }
}
Open in visual editorOpen in Inspector

Load this config in the gallery's visual editor, or in the Inspector at pptx.dev.

Pace

6-15 slides

10-30 minutes

5 beats, one slide each

Audience Fit

data-teamsoperations-and-financeproduct-managersanalytics-stakeholders

Tone

Analytical and inductive - builds up from data to insight.

Best For

Analytical briefings, data team presentations, research readouts, business reviews

Example Deck Types

Analytics deep-dive, Research readout, Business review

Example

Set the analytical context, reveal the headline finding, walk through the supporting analysis, explain what it means for the business, then make a specific recommendation.

Beat-by-Beat Guide

1

Context

Frame why this analysis matters now. What question is this data answering?

Instruction: Set up the business question and data scope.

2

Key Finding

State the single most important thing the data shows. One slide, one insight.

Instruction: State the one finding the audience must remember.

3

Analysis

Unpack the data rigorously. Show sources, methodology, and supporting charts.

Instruction: Explain the drivers behind the finding.

4

Implications

Translate findings into business language. What does this mean for strategy, operations, or customers?

Instruction: Translate the analysis into business consequences.

5

Recommendation

Make an explicit, actionable recommendation backed by the data. Include confidence level and assumptions.

Instruction: Recommend the next decision or action.

Recommended Pairings