PPTX.gallery

Strategy Block

Problem Statement

A focused problem slide that names the pain, affected audience, and cost of inaction.

problem-statement1 slidebalanced density

Problem

The current path is too slow

Frame the pain in plain language and show what it costs.

Before

Pain

After

Audience

OPF Config

blocks:problem-statement
OPF JSON
{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "name": "Problem Statement",
  "description": "A focused problem slide that names the pain, affected audience, and cost of inaction.",
  "tone": "persuasive",
  "narrative": "problem-solution",
  "takeaway": "Establish urgency around a problem before presenting a solution.",
  "tags": [
    "content-block",
    "gallery:blocks/problem-statement"
  ],
  "design": {
    "colorScheme": "bold-red",
    "fontScheme": "montserrat",
    "background": {
      "type": "solid",
      "color": "#ffffff"
    }
  },
  "slides": [
    {
      "id": "problem-statement",
      "layout": "two-column",
      "title": "The current path is too slow",
      "subtitle": "A focused statement of pain, audience, and cost.",
      "items": [
        "Who feels the pain",
        "What breaks today",
        "What delay costs"
      ]
    }
  ],
  "catalogs": {
    "default": {
      "source": "https://www.pptx.gallery",
      "narratives": {
        "problem-solution": {
          "name": "Problem → Solution",
          "summary": "Classic business arc: name the pain, raise the stakes, present your fix, show how it works, prove it, ask. The default for sales decks, internal proposals, and most general business presentations.",
          "audienceFit": [
            "customers",
            "stakeholders",
            "executives",
            "internal-teams"
          ],
          "duration": {
            "min": 5,
            "max": 30
          },
          "tags": [
            "business",
            "sales",
            "general",
            "proposal"
          ],
          "beats": [
            {
              "id": "hook",
              "name": "Hook",
              "description": "Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.",
              "layout": "statement"
            },
            {
              "id": "problem",
              "name": "The Problem",
              "description": "Name the pain in concrete terms. Make it visceral and specific — describe who hurts, how, and what they're trying to do today that isn't working. Avoid abstractions; use real examples or scenarios the audience recognizes."
            },
            {
              "id": "stakes",
              "name": "Why It Matters",
              "description": "Quantify the cost of inaction or the upside of action. Use numbers, trends, customer impact, competitive pressure — whatever makes the audience feel the size of the problem and care about solving it now rather than later."
            },
            {
              "id": "solution",
              "name": "The Solution",
              "description": "Reveal your approach and what it produces for the customer. Lead with the outcome, not the architecture. Keep it concrete: what does the audience get, and what changes for them?"
            },
            {
              "id": "mechanism",
              "name": "How It Works",
              "description": "Show the moving parts that make the solution credible. Walk through the key mechanism, workflow, or technical insight that explains why this approach succeeds where others have failed. Enough detail to earn trust; not so much that you lose the room."
            },
            {
              "id": "evidence",
              "name": "Proof",
              "description": "Demonstrate the solution works. Use customer logos, before/after metrics, demos, case studies, third-party validation — whatever de-risks the claim. One strong piece of proof beats three weak ones."
            },
            {
              "id": "ask",
              "name": "The Ask",
              "description": "State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.",
              "layout": "list"
            }
          ]
        }
      },
      "tones": {
        "persuasive": {
          "name": "Persuasive",
          "summary": "Argument-led voice for sales, fundraising, and recommendation-driven decks.",
          "description": "Frame every section as an argument that builds toward an ask. Surface objections, answer them, and pair claims with the strongest available proof. Read more like a memo than a report.",
          "voiceCues": [
            "Lead each section with the claim it's making.",
            "Surface the strongest counter-argument and address it.",
            "Pair every claim with proof — customer, benchmark, or analyst.",
            "End on a clear ask with named owner and date."
          ],
          "avoid": [
            "Buried leads.",
            "Symmetrical 'on one hand / on the other' framing without a verdict.",
            "Information for its own sake — every chart should advance the argument.",
            "Passive endings without a clear ask."
          ],
          "samplePhrases": [
            "Adopting our runtime cuts inference latency 8× while preserving accuracy.",
            "The most common objection — 'we'll be locked in' — is addressed by our open OPF spec.",
            "We're asking for a $30M Series B to ship into the enterprise tier."
          ],
          "recommendedNarratives": [
            "pitch-deck",
            "venture-pitch",
            "early-startup-pitch",
            "persuasive-sales",
            "project-proposal"
          ],
          "tags": [
            "sales",
            "pitch",
            "argumentative"
          ]
        }
      },
      "colorSchemes": {
        "bold-red": {
          "name": "Bold Red",
          "accent1": "#A41410",
          "accent2": "#2693A1",
          "accent3": "#EFA517",
          "accent4": "#E86D1F",
          "accent5": "#324472",
          "accent6": "#EFECCA",
          "dark1": "#000000",
          "dark2": "#232323",
          "followedHyperlink": "#2693A1",
          "hyperlink": "#324472",
          "light1": "#FFFFFF",
          "light2": "#DCDCDC",
          "summary": "Confident red and teal accents for urgent, high-salience stories.",
          "description": "A bold red-led scheme with teal and navy support. Use it when the deck needs urgency, contrast, and clear emphasis.",
          "tags": [
            "bold",
            "urgent",
            "energetic",
            "decisive",
            "impactful"
          ]
        }
      },
      "fontSchemes": {
        "montserrat": {
          "name": "Montserrat",
          "app": "google-slides",
          "languageFamily": "latin",
          "languages": [],
          "major": "Montserrat",
          "minor": "Montserrat",
          "textSample": "This is beautiful",
          "type": "sans-serif",
          "description": "Montserrat is a sans serif OPF font scheme for Latin presentations, using Montserrat for both headings and body text."
        }
      },
      "layouts": {
        "two-column": {
          "name": "Two columns",
          "summary": "Two independent columns of any content.",
          "tags": [
            "Text"
          ],
          "design": {
            "imageFit": "contain"
          },
          "direction": "column",
          "regions": [
            {
              "name": "title"
            },
            {
              "direction": "row",
              "regions": [
                {
                  "name": "first",
                  "accepts": [
                    "text",
                    "list",
                    "quote",
                    "code",
                    "image",
                    "video",
                    "chart",
                    "table",
                    "metric",
                    "timeline",
                    "group"
                  ],
                  "role": "primary",
                  "flow": "none"
                },
                {
                  "name": "second",
                  "accepts": [
                    "text",
                    "list",
                    "quote",
                    "code",
                    "image",
                    "video",
                    "chart",
                    "table",
                    "metric",
                    "timeline",
                    "group"
                  ],
                  "role": "primary",
                  "flow": "none"
                }
              ]
            }
          ],
          "description": "Place two bodies of content beside each other. Use it for paired explanations or an argument with supporting evidence. Pictures remain visible in full unless an explicit fit overrides the layout default.",
          "preview": {
            "vectorSrc": "https://www.pptx.gallery/layout-previews/two-column.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 a deck needs to create urgency before proposing a solution.

When to Use

Early in sales, product, transformation, and investor narratives.

When to Avoid

Avoid if the audience already accepts the problem and needs solution detail.

Block Structure

two-column

The current path is too slow

A focused statement of pain, audience, and cost.

  • -Who feels the pain
  • -What breaks today
  • -What delay costs

Best Practices

1

Write the problem in the audience's words.

2

Quantify the consequence where possible.

3

Do not introduce the solution too early.

Playground deep link: config=blocks:problem-statement