PPTX.gallery

Story Framework

Business Review

Full-loop review of recent activities to identify achievements, address challenges, and plan improvements. Goes deeper than a status update — closer to a customer-facing or partner-facing relationship review.

Beat Diagram

  1. 1Logocover / text
  2. 2Openingtext / text
  3. 3Reviewtext / text
  4. 4Successestext / text
  5. 5Challengestext / text
  6. 6Solutionstext / text
  7. 7Outcometext / text
  8. 8Insightstext / text
  9. 9Future Strategytext / text
  10. 10Feedbacktext / text
  11. 11Next Reviewtext / text
  12. 12Closingclosing / text

OPF Config

narratives:business-review
OPF JSON
{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "PPTX.gallery — narratives/business-review",
  "narrative": "business-review",
  "tags": [
    "gallery:narratives/business-review"
  ],
  "slides": [
    {
      "id": "gallery-preview-1",
      "layout": "text",
      "title": "Narrative preview",
      "subtitle": "Storyline scaffolded by the \"business-review\" narrative."
    }
  ],
  "catalogs": {
    "default": {
      "source": "https://www.pptx.gallery",
      "narratives": {
        "business-review": {
          "name": "Business Review",
          "summary": "Full-loop review of recent activities to identify achievements, address challenges, and plan improvements. Goes deeper than a status update — closer to a customer-facing or partner-facing relationship review.",
          "audienceFit": [
            "customers",
            "partners",
            "stakeholders",
            "leadership"
          ],
          "duration": {
            "min": 30,
            "max": 90
          },
          "tags": [
            "customer-relationship",
            "review",
            "operations"
          ],
          "beats": [
            {
              "id": "logo",
              "name": "Logo",
              "description": "Cover slide with logos and the review period. Establishes brand identity and signals the level of formality the rest of the deck will hold to.",
              "layout": "cover",
              "instructions": "Identity & representation",
              "type": "text"
            },
            {
              "id": "opening",
              "name": "Opening",
              "description": "Frame the meeting context and the goals for the next hour. What you'll cover, what decisions you want, what you don't intend to relitigate.",
              "instructions": "Meeting context & goals",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "review",
              "name": "Review",
              "description": "Outline the recent activities in scope: launches, projects, programs. Just enough scope-setting that the rest of the deck has shared vocabulary.",
              "instructions": "Outline recent activities",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "successes",
              "name": "Successes",
              "description": "Recognize the achievements in the review window. Lead with outcomes the audience cares about, not effort. Specific moves earn more credibility than aggregate progress.",
              "instructions": "Recognize achievements",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "challenges",
              "name": "Challenges",
              "description": "Address the problems faced honestly. What didn't work, what's still hard. Naming challenges in front of the audience earns more trust than letting them ask.",
              "instructions": "Address problems faced",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "solutions",
              "name": "Solutions",
              "description": "Discuss the fixes already implemented. Pair each with the result it produced, or, if it's still in flight, with the leading indicator you're watching.",
              "instructions": "Discuss implemented fixes",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "outcome",
              "name": "Outcome",
              "description": "Display the results achieved across the review window. Let the data carry the slide; supporting commentary should explain context, not inflate the numbers.",
              "instructions": "Display results achieved",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "insights",
              "name": "Insights",
              "description": "Highlight the key learnings. What was confirmed, what surprised you, what the audience should take away. Insights are the slides people quote in follow-on meetings.",
              "instructions": "Highlight key learnings",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "future-strategy",
              "name": "Future Strategy",
              "description": "Define the next steps and the strategic direction that follows from the review. Specific enough to sequence; flexible enough to adapt.",
              "instructions": "Define next steps",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "feedback",
              "name": "Feedback",
              "description": "Capture audience thoughts. Two or three explicit prompts where you want input or alignment. The strength of a relationship review is in the conversation it provokes.",
              "instructions": "Capture audience thoughts",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "next-review",
              "name": "Next Review",
              "description": "Plan for follow-up: when the next review happens, what evidence you'll bring, what decisions are deferred until then. Continuity is the point of the cadence.",
              "instructions": "Plan for follow-up",
              "type": "text",
              "layout": "text"
            },
            {
              "id": "closing",
              "name": "Closing",
              "description": "Recap and express optimism about the path forward. Close with the next concrete step and the people responsible for it.",
              "layout": "closing",
              "instructions": "Recap and express optimism",
              "type": "text"
            }
          ]
        }
      },
      "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

30-90 minutes

12 beats, one slide each

Audience Fit

customerspartnersstakeholdersleadership

Tags

customer-relationshipreviewoperations

Beat-by-Beat Guide

1

Logo

Cover slide with logos and the review period. Establishes brand identity and signals the level of formality the rest of the deck will hold to.

Instruction: Identity & representation

2

Opening

Frame the meeting context and the goals for the next hour. What you'll cover, what decisions you want, what you don't intend to relitigate.

Instruction: Meeting context & goals

3

Review

Outline the recent activities in scope: launches, projects, programs. Just enough scope-setting that the rest of the deck has shared vocabulary.

Instruction: Outline recent activities

4

Successes

Recognize the achievements in the review window. Lead with outcomes the audience cares about, not effort. Specific moves earn more credibility than aggregate progress.

Instruction: Recognize achievements

5

Challenges

Address the problems faced honestly. What didn't work, what's still hard. Naming challenges in front of the audience earns more trust than letting them ask.

Instruction: Address problems faced

6

Solutions

Discuss the fixes already implemented. Pair each with the result it produced, or, if it's still in flight, with the leading indicator you're watching.

Instruction: Discuss implemented fixes

7

Outcome

Display the results achieved across the review window. Let the data carry the slide; supporting commentary should explain context, not inflate the numbers.

Instruction: Display results achieved

8

Insights

Highlight the key learnings. What was confirmed, what surprised you, what the audience should take away. Insights are the slides people quote in follow-on meetings.

Instruction: Highlight key learnings

9

Future Strategy

Define the next steps and the strategic direction that follows from the review. Specific enough to sequence; flexible enough to adapt.

Instruction: Define next steps

10

Feedback

Capture audience thoughts. Two or three explicit prompts where you want input or alignment. The strength of a relationship review is in the conversation it provokes.

Instruction: Capture audience thoughts

11

Next Review

Plan for follow-up: when the next review happens, what evidence you'll bring, what decisions are deferred until then. Continuity is the point of the cadence.

Instruction: Plan for follow-up

12

Closing

Recap and express optimism about the path forward. Close with the next concrete step and the people responsible for it.

Instruction: Recap and express optimism