Data Story Insight

{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "Data Story Insight",
  "description": "A single-insight analytical slide that connects evidence to implication.",
  "tone": "technical",
  "narrative": "data-story",
  "takeaway": "Turn one analytical finding into a clear narrative slide.",
  "tags": [
    "content-block",
    "gallery:blocks/data-story-insight"
  ],
  "design": {
    "colorScheme": "slate-gray",
    "fontScheme": "open-sans",
    "background": {
      "type": "solid",
      "color": "#ffffff"
    }
  },
  "slides": [
    {
      "id": "data-story-insight",
      "layout": "chart-beside",
      "title": "The gap opens after onboarding",
      "subtitle": "One finding, one implication, one action.",
      "blocks": [
        {
          "items": [
            "Finding: activation splits by segment",
            "Implication: onboarding needs branching",
            "Action: test segment-specific paths"
          ]
        },
        {
          "chart": {
            "type": "bar",
            "data": {
              "columns": [
                "Category",
                "Example"
              ],
              "rows": [
                [
                  "Current",
                  12
                ],
                [
                  "Next",
                  19
                ],
                [
                  "Target",
                  27
                ]
              ]
            }
          }
        }
      ]
    }
  ],
  "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"
            }
          ]
        }
      },
      "tones": {
        "technical": {
          "name": "Technical",
          "summary": "Precise, evidence-led voice for engineering, research, and product-detail audiences.",
          "description": "Lead with the question or claim, then walk through the mechanism and the numbers. Use exact terminology; assume the audience can handle and prefers it. Diagrams, tables, and benchmarks are first-class.",
          "voiceCues": [
            "State the claim, then the mechanism, then the evidence.",
            "Use exact terminology — don't soften technical terms for general readability.",
            "Quote benchmarks with conditions (cold/warm, p50/p95/p99, dataset, hardware).",
            "Prefer diagrams and tables over prose paragraphs for structural information."
          ],
          "avoid": [
            "Vague claims ('much faster', 'better', 'easier').",
            "Marketing framing without supporting data.",
            "Glossing over caveats and tradeoffs.",
            "Casual register that obscures precision."
          ],
          "samplePhrases": [
            "p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.",
            "We replaced the streaming serializer with a batched protobuf path; throughput rose 4.2× under load.",
            "The result holds for context windows up to 32k tokens; beyond that, see appendix B."
          ],
          "recommendedNarratives": [
            "challenge-resolution",
            "innovation",
            "conference-talk",
            "status-update"
          ],
          "tags": [
            "technical",
            "engineering",
            "research"
          ]
        }
      },
      "colorSchemes": {
        "slate-gray": {
          "name": "Slate Gray",
          "accent1": "#9E9E9E",
          "accent2": "#424242",
          "accent3": "#616161",
          "accent4": "#757575",
          "accent5": "#9E9E9E",
          "accent6": "#212121",
          "dark1": "#000000",
          "dark2": "#1B1B1B",
          "followedHyperlink": "#424242",
          "hyperlink": "#212121",
          "light1": "#FFFFFF",
          "light2": "#F8F8F8",
          "summary": "Neutral gray palette for understated executive communication.",
          "description": "A disciplined gray scale with strong neutral contrast. Use it when the content should feel calm, mature, and analytical.",
          "tags": [
            "neutral",
            "minimal",
            "mature",
            "analytical",
            "restrained"
          ]
        }
      },
      "fontSchemes": {
        "open-sans": {
          "name": "Open Sans",
          "app": "google-slides",
          "languageFamily": "latin",
          "languages": [],
          "major": "Open Sans",
          "minor": "Open Sans",
          "textSample": "Modern and sleek",
          "type": "sans-serif",
          "description": "Open Sans is a sans serif OPF font scheme for Latin presentations, using Open Sans for both headings and body text."
        }
      },
      "layouts": {
        "chart-beside": {
          "name": "Chart beside",
          "summary": "A chart with the takeaway beside it.",
          "tags": [
            "Visuals"
          ],
          "direction": "column",
          "regions": [
            {
              "name": "title"
            },
            {
              "direction": "row",
              "regions": [
                {
                  "name": "chart",
                  "size": 3,
                  "accepts": [
                    "chart"
                  ],
                  "role": "primary",
                  "flow": "none"
                },
                {
                  "name": "notes",
                  "size": 2,
                  "accepts": [
                    "text",
                    "list",
                    "metric",
                    "quote",
                    "chart"
                  ],
                  "role": "supporting",
                  "flow": "column"
                }
              ]
            }
          ],
          "description": "Pair a chart with an explanation of its result. Keep the text focused on the pattern or decision supported by the data.",
          "preview": {
            "vectorSrc": "https://www.pptx.gallery/layout-previews/chart-beside.svg"
          }
        }
      }
    }
  }
}