People & Proof Block
Case Study Snapshot
A compact case-study block that links situation, action, result, and proof.
case-study-snapshot1 slidebalanced density
Case Study
One customer, measurable lift
Tell the situation, action, result, and proof in a compact structure.
01
Situation
02
Action
03
Result
04
Proof
OPF Config
blocks:case-study-snapshotOPF JSON
{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "Case Study Snapshot",
"description": "A compact case-study block that links situation, action, result, and proof.",
"tone": "persuasive",
"narrative": "star-method",
"takeaway": "Show one concrete example of impact using a compact case-study arc.",
"tags": [
"content-block",
"gallery:blocks/case-study-snapshot"
],
"design": {
"colorScheme": "steel-blue",
"fontScheme": "georgia",
"background": {
"type": "solid",
"color": "#ffffff"
}
},
"slides": [
{
"id": "case-study-snapshot",
"layout": "two-column",
"title": "One customer, measurable lift",
"subtitle": "Situation, action, result, and proof.",
"items": [
"Situation: slow cycle time",
"Action: guided workflow",
"Result: 31% faster decisions",
"Proof: cohort analysis"
]
}
],
"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": {
"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": {
"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"
]
}
},
"fontSchemes": {
"georgia": {
"name": "Georgia",
"app": "powerpoint",
"languageFamily": "latin",
"languages": [],
"major": "Georgia",
"minor": "Georgia",
"textSample": "Warm digital serif",
"type": "serif",
"description": "Georgia is a serif OPF font scheme for Latin presentations, using Georgia 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 one concrete example of impact.
When to Use
For sales, customer success, transformation, and portfolio decks.
When to Avoid
Avoid if the example is not close enough to the audience's context.
Block Structure
two-column
One customer, measurable lift
Situation, action, result, and proof.
- -Situation: slow cycle time
- -Action: guided workflow
- -Result: 31% faster decisions
- -Proof: cohort analysis
Best Practices
1
Pick an example close to the audience.
2
Use one measurable result.
3
Do not overgeneralize from the case.
Playground deep link: config=blocks:case-study-snapshot