PPTX.gallery

OPF Audience

Engineering Team

Engineers tune out generalities and tune in to specifics. Show benchmarks with conditions, architecture diagrams with constraints, and tradeoffs you actually considered. Internal jargon is fine — assume the room shares it. Leave room for questions; engineering audiences engage best when they can poke at the proposal.

engineering-teamadvisoryhigh density

Audience

Engineering Team

advisory · 45 min

technical
casual

Density

high

Seniority

IC

Technical Fluency

High

Decision Power

Advisory

Attention Budget

45 minutes

Recommended Tones

Technical, Casual, Conversational

Slide Count

15-30 slides

Industry Fit

technology, engineering, software

Design Principles

1

Benchmarks with their conditions

2

Architecture diagrams with constraints

3

Show the tradeoffs you considered

4

Leave room for questions

Recommended Companions

OPF Config

audiences:engineering-team
OPF JSON
{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "PPTX.gallery — audiences/engineering-team",
  "description": "Practitioners building the system; they want depth, mechanism, and tradeoffs.",
  "audience": [
    "engineering-team"
  ],
  "narrative": "status-update",
  "tone": "technical",
  "takeaway": "Practitioners building the system; they want depth, mechanism, and tradeoffs.",
  "tags": [
    "gallery:audiences/engineering-team"
  ],
  "design": {
    "colorScheme": "steel-blue"
  },
  "slides": [
    {
      "id": "gallery-preview-1",
      "layout": "text",
      "title": "Engineering Team",
      "subtitle": "Practitioners building the system; they want depth, mechanism, and tradeoffs."
    }
  ],
  "catalogs": {
    "default": {
      "source": "https://www.pptx.gallery",
      "narratives": {
        "status-update": {
          "name": "Status Update",
          "summary": "Concise progress-report arc for keeping a stakeholder informed: headline, brief, progress, results, plan, feedback. Optimized for short, repeated updates rather than one-time deep dives.",
          "audienceFit": [
            "stakeholders",
            "managers",
            "customers",
            "executives"
          ],
          "duration": {
            "min": 5,
            "max": 15
          },
          "tags": [
            "reporting",
            "operations",
            "customer-relationship",
            "weekly"
          ],
          "beats": [
            {
              "id": "headline",
              "name": "Headline",
              "description": "Open with the single most important sentence the audience needs to know — on track, off track, or shifted. The headline replaces 'how's it going' with a clear answer.",
              "layout": "cover",
              "instructions": "Title & date",
              "type": "text"
            },
            {
              "id": "brief",
              "name": "Brief",
              "description": "State the objective for the period and what was promised. One slide, three lines. Frames the rest of the update so progress is read against a clear bar.",
              "instructions": "Summary/objectives",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "progress",
              "name": "Progress",
              "description": "Walk through the actions taken since the last update. Specific, attributable, dated. Avoid effort theater — list outcomes and material moves, not activity for its own sake.",
              "instructions": "Explain actions taken",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "results",
              "name": "Results",
              "description": "Show the outcomes those actions produced. Metrics, customer signals, decisions made. Keep the comparison crisp — versus plan, versus last period, versus benchmark.",
              "instructions": "Show outcomes",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "action-plan",
              "name": "Action Plan",
              "description": "Outline the next steps and who owns them. Be specific about the next decision point and what would have to happen to slip the schedule.",
              "instructions": "Outline next steps",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "feedback",
              "name": "Feedback",
              "description": "Invite the audience to weigh in: where you'd like input, where you need a decision, where help would unblock you. End the update with an open hand, not a closed file.",
              "layout": "text",
              "instructions": "Ask for response",
              "type": "text"
            }
          ]
        }
      },
      "audiences": {
        "engineering-team": {
          "name": "Engineering Team",
          "summary": "Practitioners building the system; they want depth, mechanism, and tradeoffs.",
          "description": "Engineers tune out generalities and tune in to specifics. Show benchmarks with conditions, architecture diagrams with constraints, and tradeoffs you actually considered. Internal jargon is fine — assume the room shares it. Leave room for questions; engineering audiences engage best when they can poke at the proposal.",
          "seniority": "ic",
          "technicalFluency": "high",
          "decisionPower": "advisory",
          "attentionBudgetMinutes": 45,
          "recommendedNarratives": [
            "status-update",
            "challenge-resolution",
            "innovation",
            "weekly-progress"
          ],
          "recommendedTones": [
            "technical",
            "casual",
            "conversational"
          ],
          "tags": [
            "internal",
            "engineering",
            "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"
          }
        }
      }
    }
  }
}
Open in visual editorOpen in Inspector

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