PPTX.gallery

People & Proof Block

Team Grid

A team slide block for roles, credibility, and coverage across the work.

team-grid1 slidebalanced density

Team

The team built for this moment

Show relevant roles and proof, not full resumes.

01

Lead

02

Product

03

Data

04

GTM

OPF Config

blocks:team-grid
OPF JSON
{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "Team Grid",
  "description": "A team slide block for roles, credibility, and coverage across the work.",
  "tone": "formal",
  "narrative": "star-method",
  "takeaway": "Build confidence in the team responsible for the work.",
  "tags": [
    "content-block",
    "gallery:blocks/team-grid"
  ],
  "design": {
    "colorScheme": "cool-horizon",
    "fontScheme": "segoe-ui",
    "background": {
      "type": "solid",
      "color": "#ffffff"
    }
  },
  "slides": [
    {
      "id": "team-grid",
      "layout": "team",
      "title": "The team built for this moment",
      "subtitle": "Relevant roles, credibility, and coverage.",
      "items": [
        "Lead",
        "Product",
        "Data",
        "GTM"
      ]
    }
  ],
  "catalogs": {
    "default": {
      "source": "https://www.pptx.gallery",
      "narratives": {
        "star-method": {
          "name": "STAR Method",
          "summary": "Results-focused framework that demonstrates impact through concrete examples.",
          "description": "A results-focused framework that demonstrates impact through a concrete example: the Situation, the Task you were responsible for, the Actions you took, and the measurable Result. The tone is evidential: every claim is grounded in a specific, verifiable outcome. Best for project reviews, portfolio presentations, and achievement showcases; typical decks run 4-8 slides (case study, customer success story, project retrospective).",
          "audienceFit": [
            "hr-and-talent",
            "performance-reviewers",
            "award-committees"
          ],
          "duration": {
            "min": 5,
            "max": 15
          },
          "tags": [
            "case-study",
            "proof",
            "results",
            "retrospective"
          ],
          "beats": [
            {
              "id": "situation",
              "name": "Situation",
              "description": "Describe the context and background of the scenario.",
              "instructions": "Describe the relevant context and constraints.",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "task",
              "name": "Task",
              "description": "Explain your specific role and responsibilities in this situation.",
              "instructions": "Explain the responsibility or target outcome.",
              "type": "list",
              "layout": "two-column"
            },
            {
              "id": "action",
              "name": "Action",
              "description": "Detail the specific steps you took to address the challenge.",
              "instructions": "Detail the actions taken and choices made.",
              "type": "timeline",
              "layout": "timeline"
            },
            {
              "id": "result",
              "name": "Result",
              "description": "Share the measurable outcomes and impact of your actions.",
              "instructions": "Show measurable impact and proof.",
              "type": "metric",
              "layout": "metrics"
            }
          ]
        }
      },
      "tones": {
        "formal": {
          "name": "Formal",
          "summary": "Polished, restrained voice for board, investor, and regulator audiences.",
          "description": "Authoritative without being cold. Use third-person constructions, full sentences, and concrete numbers. Avoid hedges and humor that depend on shared in-jokes; rely on clarity and precision to land.",
          "voiceCues": [
            "Use third person and the corporate 'we' sparingly.",
            "Lead with the recommendation, then evidence.",
            "Quote concrete numbers; avoid round-tripping ranges.",
            "Prefer full sentences to bullet fragments on key claims."
          ],
          "avoid": [
            "Slang, idioms, or in-jokes.",
            "Hedging language ('maybe', 'sort of', 'I think').",
            "Marketing superlatives ('world-class', 'best-in-class').",
            "Excessive emoji or exclamation points."
          ],
          "samplePhrases": [
            "Q4 revenue grew 18% year over year, led by enterprise expansion.",
            "We recommend approving the Series B raise at $30M.",
            "Net retention was 124%; gross retention was 96%."
          ],
          "recommendedNarratives": [
            "board-meeting",
            "qbr",
            "scqa",
            "strategic-narrative"
          ],
          "tags": [
            "business",
            "executive",
            "formal"
          ]
        }
      },
      "colorSchemes": {
        "cool-horizon": {
          "name": "Cool Horizon",
          "accent1": "#2874A6",
          "accent2": "#1B4F72",
          "accent3": "#5499C7",
          "accent4": "#7BDBB2",
          "accent5": "#3AC67A",
          "accent6": "#24A89E",
          "dark1": "#000000",
          "dark2": "#011842",
          "followedHyperlink": "#551A8B",
          "hyperlink": "#0000EE",
          "light1": "#FFFFFF",
          "light2": "#F0F0F0",
          "summary": "Cool blue-green palette tuned for professional business decks.",
          "description": "A balanced cool-toned scheme with deep navy, business blues, and teal accents. It works well across strategy, finance, and technical narratives.",
          "tags": [
            "professional",
            "trustworthy",
            "calm",
            "technical",
            "versatile"
          ]
        }
      },
      "fontSchemes": {
        "segoe-ui": {
          "name": "Segoe UI",
          "app": "powerpoint",
          "languageFamily": "latin",
          "languages": [],
          "major": "Segoe UI Semibold",
          "minor": "Segoe UI",
          "textSample": "Modern interface font",
          "type": "sans-serif",
          "description": "Segoe UI is a sans serif OPF font scheme for Latin presentations, using Segoe UI Semibold for headings with Segoe UI for body text."
        }
      },
      "layouts": {
        "team": {
          "name": "Team",
          "summary": "People: photo, name and role cards.",
          "tags": [
            "Mixed"
          ],
          "design": {
            "listBullet": "none"
          },
          "direction": "column",
          "regions": [
            {
              "name": "title"
            },
            {
              "name": "people",
              "accepts": [
                "group",
                "image",
                "text",
                "quote",
                "list"
              ],
              "role": "primary",
              "flow": "grid"
            }
          ],
          "description": "Introduce people and their roles. Use consistent names, descriptions and portraits when available.",
          "preview": {
            "vectorSrc": "https://www.pptx.gallery/layout-previews/team.svg"
          }
        }
      }
    }
  }
}
Open in visual editorOpen in Inspector

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

Use Case

Use when the audience needs confidence in who will execute.

When to Use

For investor, sales, agency, transformation, and project kickoff decks.

When to Avoid

Avoid when team identity is not material to the decision.

Block Structure

team

The team built for this moment

Relevant roles, credibility, and coverage.

  • -Lead
  • -Product
  • -Data
  • -GTM

Best Practices

1

Lead with role relevance, not biography.

2

Keep each bio to one credibility line.

3

Use consistent photo treatment if photos are included.

Playground deep link: config=blocks:team-grid