Use the Prompt
Add Your Brief
Add your context below. It will be included with the prompt when you copy or download.
Create an editable HTML presentation with a 16:9 canvas, previous/next buttons, arrow-key navigation, a slide counter and a one-slide-per-page print layout for [PROJECT] and [AUDIENCE]. The task is: Data Story Presentation.
Required content and structure
Frame a question, show comparable values, explain uncertainty and recommend a decision.
Use [APPROVED_CONTENT] as the source of names, dates, figures, claims and destinations. List missing inputs before substituting anything. If a demonstration is needed, label its content as fictional. Do not invent customer quotes, rankings, partner logos or product capabilities.
Design direction
Use [BRAND_RULES] and the design system already selected in the project. If no system is supplied, start with this direction: white, midnight navy and restrained blue; strong alignment and simple evidence diagrams. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Frame one question and prepare the values, units, dates, sources and uncertainty needed to answer it. Decide which comparisons are valid before choosing chart types.
Layout and behavior
Build a sequence in which each chart answers a specific part of the question. Use consistent scales and annotate the evidence that changes the interpretation.
Task-specific acceptance check
- Keep axes, units, missing values and source dates visible.
- Inspect axes, missing values and denominators.
- A visually dramatic difference should remain proportionate to the actual data, and recommendations should acknowledge unresolved uncertainty.
Implementation and review
Keep text editable. Use semantic structure, descriptive controls, visible keyboard focus and appropriate empty/error states. Check narrow and wide layouts. Respect reduced-motion preferences. Preserve any existing project framework and dependencies; do not silently replace the stack. Return the editable files and explain any incomplete behavior or unsupported inputs. Review this specific task before proposing extra features.
Keep one main idea per slide. Use charts only when actual comparable values are supplied; include units, source dates and limitations. Keep speaker notes separate from visible slide content.
Reference attachment and reconstruction goal
Attach reference.webp from this prompt’s download bundle alongside this prompt in OpenDesign. Build an editable result with a similar composition and hierarchy; do not embed the whole reference image as the finished interface. Preserve approved project content and brand rules if they conflict with fictional sample labels. If the image is missing or unreadable, ask for it instead of claiming visual fidelity.
Reference composition and content
Use the attached reference.webp as the visual reference for Data Story Presentation. Before building, identify the major regions from top to bottom, their relative widths and heights, alignment, spacing, typography hierarchy, surface colors, borders, imagery and repeated components. Preserve those relationships rather than substituting a generic template. Required task content: Frame a question, show comparable values, explain uncertainty and recommend a decision. Use the following task-specific layout guidance when translating the image into editable elements: Build a sequence in which each chart answers a specific part of the question. Use consistent scales and annotate the evidence that changes the interpretation.
Visual direction from the example brief
white, midnight navy and restrained blue; strong alignment and simple evidence diagrams.
Slide structure and presentation behavior
Recreate the slide composition as editable title, body, visual and annotation elements. A pictured slide is one view, not evidence of a complete deck. Use the supplied narrative to build any requested additional slides; preserve its typography, margins, color roles and alignment. Build a sequence in which each chart answers a specific part of the question. Use consistent scales and annotate the evidence that changes the interpretation. Keep navigation outside exported slide content. Keep axes, units, missing values and source dates visible.
Visual comparison and delivery
- Compare the result with the attached image at matching proportions. Review major region placement, relative image sizes, line breaks, spacing, typography hierarchy, contrast, active states and content density before polishing decorative details.
- Then test the narrow layout without squeezing desktop text into tiny labels.
- Keep logos, photos and icons as separate assets and all meaningful labels editable. List any unavailable fonts/assets and any intentional departures. Return the working files plus a concise account of implemented behavior and remaining integrations; do not promise a pixel-identical result from the prompt alone.
Adapting the reference to slide dimensions
The attached visual reference is a 3:2 concept image, while the requested presentation uses 16:9 slides. Recompose its text, images, charts and spacing as separate editable elements on a 16:9 canvas. Do not stretch the reference or crop the whole composition to force a match. Preserve the hierarchy, keep the supplied content readable, and adapt each slide to its own message.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Data Story Presentation Design Prompt
Use this data story presentation design prompt to frame a question, show comparable values, explain uncertainty and recommend a decision.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Make Each Chart Answer a Question
A data story deck should move from a decision question to evidence and an interpretation.
More charts do not help if their periods or definitions are incompatible. Build a sequence in which each chart answers a specific part of the question. Use consistent scales and annotate the evidence that changes the interpretation.
From the Prompt
Build a sequence in which each chart answers a specific part of the question.
Make It Your Own
Open with [DECISION_QUESTION]. Use comparable [METRICS] with units, periods and source dates, then distinguish the observed pattern from its possible explanations.
Prepare the Data Story Presentation Content
Two charts compare the same transport options using different units. Provide source data, periods and units explicitly before making a recommendation.
Frame one question and prepare the values, units, dates, sources and uncertainty needed to answer it. Decide which comparisons are valid before choosing chart types.
From the Prompt
Frame a question, show comparable values, explain uncertainty and recommend a decision.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this data story presentation. Frame one question and prepare the values, units, dates, sources and uncertainty needed to answer it. Decide which comparisons are valid before choosing chart types. Identify missing inputs before replacing them with demonstration content.
Read the Chart Alone
The lower row places uncertainty ranges beside the proposed choice. Verify that the recommendation accounts for these ranges instead of relying solely on the lowest central estimate.
A screenshot of the chart should retain enough labeling to identify the measure, period and uncertainty. Its title should not claim causality the evidence cannot support. Inspect axes, missing values and denominators. A visually dramatic difference should remain proportionate to the actual data, and recommendations should acknowledge unresolved uncertainty.
From the Prompt
Keep axes, units, missing values and source dates visible.
Make It Your Own
Review the data story presentation against this requirement: Keep axes, units, missing values and source dates visible. Inspect axes, missing values and denominators. A visually dramatic difference should remain proportionate to the actual data, and recommendations should acknowledge unresolved uncertainty. Preserve approved content and revise only the parts that fail this check.
Review Your Data Story Presentation Result
A generated image cannot validate a complete deck or its evidence. Test every slide, keyboard navigation, print layout and any exported file separately.
- Inspect axes, missing values and denominators. A visually dramatic difference should remain proportionate to the actual data, and recommendations should acknowledge unresolved uncertainty.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current data story presentation. Inspect axes, missing values and denominators. A visually dramatic difference should remain proportionate to the actual data, and recommendations should acknowledge unresolved uncertainty. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
