Technical

{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "PPTX.gallery — audiences/technical",
  "description": "Engineers, data scientists, and technical specialists requiring precision, methodology details, and system-level understanding.",
  "audience": [
    "technical"
  ],
  "narrative": "data-story",
  "tone": "technical",
  "takeaway": "Engineers, data scientists, and technical specialists requiring precision, methodology details, and system-level understanding.",
  "tags": [
    "gallery:audiences/technical"
  ],
  "design": {
    "colorScheme": "steel-blue"
  },
  "slides": [
    {
      "id": "gallery-preview-1",
      "layout": "text",
      "title": "Technical",
      "subtitle": "Engineers, data scientists, and technical specialists requiring precision, methodology details, and system-level understanding."
    }
  ],
  "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"
            }
          ]
        }
      },
      "audiences": {
        "technical": {
          "name": "Technical",
          "summary": "Engineers, data scientists, and technical specialists requiring precision, methodology details, and system-level understanding.",
          "description": "Engineers, data scientists, and technical specialists who expect precision, methodology, and system-level understanding. Show the methodology and cite data sources, prefer technical diagrams to metaphors, and do not shy away from dense information. Chart density can be high; 20-40 slides is normal.",
          "seniority": "ic",
          "technicalFluency": "high",
          "decisionPower": "advisory",
          "attentionBudgetMinutes": 45,
          "recommendedNarratives": [
            "data-story",
            "situation-complication-resolution"
          ],
          "recommendedTones": [
            "technical",
            "authoritative",
            "conversational"
          ],
          "tags": [
            "internal",
            "technical",
            "practitioner"
          ]
        }
      },
      "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": {
        "steel-blue": {
          "name": "Steel Blue",
          "accent1": "#4A66AC",
          "accent2": "#629DD1",
          "accent3": "#297FD5",
          "accent4": "#7F8FA9",
          "accent5": "#5AA2AE",
          "accent6": "#9D90A0",
          "dark1": "#000000",
          "dark2": "#182238",
          "followedHyperlink": "#3EBBF0",
          "hyperlink": "#9454C3",
          "light1": "#FFFFFF",
          "light2": "#EAEDF6",
          "summary": "Cool steel blues for credible, data-forward presentations.",
          "description": "A steel-blue palette that combines credibility, precision, and calm. Useful for analysis-heavy decks.",
          "tags": [
            "calm",
            "precise",
            "measured",
            "professional",
            "analytical"
          ]
        }
      },
      "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"
          }
        }
      }
    }
  }
}