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
Open Presentation Format
{
  "$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"
      ],
      "design": {
        "contentBox": false,
        "contentAlignment": "left",
        "titleAlignment": "left",
        "contentDirection": "horizontal"
      }
    }
  ]
}
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