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: Product Retrospective Deck.
Required content and structure
Compare intended outcomes with evidence, identify lessons and prioritize follow-up experiments.
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: ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy. Keep type, spacing and color roles consistent. Prioritize the task over decorative elements and avoid a generic collection of unrelated cards.
Content preparation
Collect intended outcomes, delivered work, actual evidence, unexpected effects and unresolved questions. Define the time window and measures used to judge progress.
Layout and behavior
Compare intention and outcome before discussing lessons. Connect proposed experiments to a specific uncertainty and assign follow-up ownership where it is known.
Task-specific acceptance check
- Avoid turning correlation into causality.
- Check whether each lesson follows from the evidence.
- Separate correlation from cause and avoid rewriting the original goals to make the finished work appear successful.
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 Product Retrospective Deck. 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: Compare intended outcomes with evidence, identify lessons and prioritize follow-up experiments. Use the following task-specific layout guidance when translating the image into editable elements: Compare intention and outcome before discussing lessons. Connect proposed experiments to a specific uncertainty and assign follow-up ownership where it is known.
Visual direction from the example brief
ivory, charcoal and a single lime accent; oversized headlines, deliberate whitespace and clear information hierarchy.
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. Compare intention and outcome before discussing lessons. Connect proposed experiments to a specific uncertainty and assign follow-up ownership where it is known. Keep navigation outside exported slide content. Avoid turning correlation into causality.
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.
Adapt the reference to the slide canvas
The attached reference image uses a 3:2 composition. Recompose its editable text, shapes and separate image assets onto the requested 16:9 slide canvas. Preserve hierarchy and readable spacing by adjusting the layout; do not stretch the reference or crop essential content to force it into 16:9. Treat this single concept as a visual direction, not as a completed multi-slide deck.
Download Prompt + Image
Includes the complete prompt and full-size reference image. Attach both in OpenDesign to guide the layout.
How to Write a Product Retrospective Deck Design Prompt
Use this product retrospective deck design prompt to compare intended outcomes with evidence, identify lessons and prioritize follow-up experiments.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Compare Intent with Evidence
A product retrospective deck should explain what was intended, what happened and what remains uncertain.
A positive metric movement alone cannot prove the feature caused it. Compare intention and outcome before discussing lessons. Connect proposed experiments to a specific uncertainty and assign follow-up ownership where it is known.
From the Prompt
Compare intention and outcome before discussing lessons.
Make It Your Own
Pair [INTENDED_OUTCOME] with observed evidence, alternative explanations and lessons. Convert the most important uncertainty into a prioritized follow-up experiment.
Prepare the Product Retrospective Deck Content
The cover outlines outcomes, lessons and follow-up experiments; supply evidence and owners when expanding those sections.
Collect intended outcomes, delivered work, actual evidence, unexpected effects and unresolved questions. Define the time window and measures used to judge progress.
From the Prompt
Compare intended outcomes with evidence, identify lessons and prioritize follow-up experiments.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this product retrospective deck. Collect intended outcomes, delivered work, actual evidence, unexpected effects and unresolved questions. Define the time window and measures used to judge progress. Identify missing inputs before replacing them with demonstration content.
Check a Claimed Success
The road illustration is a framing device, not a performance chart; keep quantitative results in separate labeled evidence slides.
Look for the comparison period, metric definition and plausible confounders. If causality is unknown, use that uncertainty to shape the next test. Check whether each lesson follows from the evidence. Separate correlation from cause and avoid rewriting the original goals to make the finished work appear successful.
From the Prompt
Avoid turning correlation into causality.
Make It Your Own
Review the product retrospective deck against this requirement: Avoid turning correlation into causality. Check whether each lesson follows from the evidence. Separate correlation from cause and avoid rewriting the original goals to make the finished work appear successful. Preserve approved content and revise only the parts that fail this check.
Review Your Product Retrospective Deck Result
A generated image cannot validate a complete deck or its evidence. Test every slide, keyboard navigation, print layout and any exported file separately.
- Check whether each lesson follows from the evidence. Separate correlation from cause and avoid rewriting the original goals to make the finished work appear successful.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current product retrospective deck. Check whether each lesson follows from the evidence. Separate correlation from cause and avoid rewriting the original goals to make the finished work appear successful. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
