Timelines Block
Process Overview
A process-flow block for explaining stages, handoffs, or operating rhythm.
process-overview1 slidebalanced density
Process
From intake to decision
Map the handoffs that turn inputs into outcomes.
Intake
Review
Decision
Close
OPF Config
blocks:process-overviewOPF JSON
{
"$schema": "https://openpresentation.org/schema/opf/v1",
"name": "Process Overview",
"description": "A process-flow block for explaining stages, handoffs, or operating rhythm.",
"tone": "technical",
"narrative": "what-so-what-now-what",
"takeaway": "Explain a workflow from first input to final outcome.",
"tags": [
"content-block",
"gallery:blocks/process-overview"
],
"design": {
"colorScheme": "forest-green",
"fontScheme": "open-sans",
"background": {
"type": "solid",
"color": "#ffffff"
}
},
"slides": [
{
"id": "process-overview",
"layout": "process",
"title": "From intake to decision",
"subtitle": "A simple operating flow with visible handoffs.",
"timeline": {
"events": [
{
"what": "Intake"
},
{
"what": "Review"
},
{
"what": "Decision"
},
{
"what": "Close"
}
]
}
}
],
"catalogs": {
"default": {
"source": "https://www.pptx.gallery",
"narratives": {
"what-so-what-now-what": {
"name": "What-So What-Now What",
"summary": "Concise framework that connects information to meaning to action. Perfect for executive audiences.",
"description": "A concise framework that connects information to meaning to action. Present the facts or findings objectively, explain why they matter to this audience, then state the decisions or next steps they require. The tone is analytical: data-forward and respectful of executive time, with no scene-setting beyond what the facts need. Best for executive briefings, status updates, and research findings; typical decks run 3-6 slides (analytics report, team performance review, strategy update).",
"audienceFit": [
"executive",
"senior-managers",
"board"
],
"duration": {
"min": 5,
"max": 15
},
"tags": [
"executive",
"briefing",
"analytical",
"action"
],
"beats": [
{
"id": "what",
"name": "What",
"description": "Present the facts, data, or findings objectively and clearly.",
"instructions": "Present the facts, data, or findings objectively and clearly.",
"type": "chart",
"layout": "chart"
},
{
"id": "so-what",
"name": "So What",
"description": "Explain the significance. Why should your audience care about this information?",
"instructions": "Explain the significance. Why should your audience care about this information?",
"type": "metric",
"layout": "metrics"
},
{
"id": "now-what",
"name": "Now What",
"description": "Define the action required. What decisions or next steps follow from this?",
"instructions": "Define the action required. What decisions or next steps follow from this?",
"type": "text",
"layout": "list"
}
]
}
},
"tones": {
"technical": {
"name": "Technical",
"summary": "Precise, evidence-led voice for engineering, research, and product-detail audiences.",
"description": "Lead with the question or claim, then walk through the mechanism and the numbers. Use exact terminology; assume the audience can handle and prefers it. Diagrams, tables, and benchmarks are first-class.",
"voiceCues": [
"State the claim, then the mechanism, then the evidence.",
"Use exact terminology — don't soften technical terms for general readability.",
"Quote benchmarks with conditions (cold/warm, p50/p95/p99, dataset, hardware).",
"Prefer diagrams and tables over prose paragraphs for structural information."
],
"avoid": [
"Vague claims ('much faster', 'better', 'easier').",
"Marketing framing without supporting data.",
"Glossing over caveats and tradeoffs.",
"Casual register that obscures precision."
],
"samplePhrases": [
"p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.",
"We replaced the streaming serializer with a batched protobuf path; throughput rose 4.2× under load.",
"The result holds for context windows up to 32k tokens; beyond that, see appendix B."
],
"recommendedNarratives": [
"challenge-resolution",
"innovation",
"conference-talk",
"status-update"
],
"tags": [
"technical",
"engineering",
"research"
]
}
},
"colorSchemes": {
"forest-green": {
"name": "Forest Green",
"accent1": "#4A7C59",
"accent2": "#68B0AB",
"accent3": "#8FC0A9",
"accent4": "#C8D5B9",
"accent5": "#FAF3DD",
"accent6": "#BFBFBF",
"dark1": "#000000",
"dark2": "#263F2E",
"followedHyperlink": "#68B0AB",
"hyperlink": "#4A7C59",
"light1": "#FFFFFF",
"light2": "#EEF5F0",
"summary": "Organic green palette for growth, health, and sustainability stories.",
"description": "A green and soft-neutral scheme for decks about growth, renewal, wellness, and environmental impact.",
"tags": [
"organic",
"healthy",
"sustainable",
"fresh",
"balanced"
]
}
},
"fontSchemes": {
"open-sans": {
"name": "Open Sans",
"app": "google-slides",
"languageFamily": "latin",
"languages": [],
"major": "Open Sans",
"minor": "Open Sans",
"textSample": "Modern and sleek",
"type": "sans-serif",
"description": "Open Sans is a sans serif OPF font scheme for Latin presentations, using Open Sans for both headings and body text."
}
},
"layouts": {
"process": {
"name": "Process",
"summary": "Steps in order, in one row.",
"tags": [
"Groups of items"
],
"design": {
"contentBox": false,
"contentDirection": "horizontal"
},
"direction": "column",
"regions": [
{
"name": "title"
},
{
"name": "steps",
"accepts": [
"timeline",
"list",
"text",
"metric",
"group"
],
"role": "primary",
"flow": "grid"
}
],
"description": "Explain an ordered sequence of steps. Give each step a clear action and enough context to understand the transition.",
"preview": {
"vectorSrc": "https://www.pptx.gallery/layout-previews/process.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 workflow needs to be understood end to end.
When to Use
For operations, onboarding, service delivery, and implementation decks.
When to Avoid
Avoid when the process is non-linear and needs a journey map instead.
Block Structure
process
From intake to decision
A simple operating flow with visible handoffs.
- -Intake
- -Review
- -Decision
- -Close
Best Practices
1
Use verbs for stages.
2
Keep exceptions out of the main flow.
3
Show ownership only when it changes the decision.
Playground deep link: config=blocks:process-overview