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: Customer Journey Deck.
Required content and structure
Map stages, user goals, touchpoints, friction and improvement opportunities.
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
Choose a specific customer scenario and gather stages, goals, touchpoints, observed friction and opportunities. Label assumed emotions rather than inventing a research voice.
Layout and behavior
Align stages along one journey and connect each opportunity to a concrete friction point. Keep evidence close to the observation it supports.
Task-specific acceptance check
- Keep observed evidence separate from assumed emotions.
- Walk through the journey from the customer's perspective.
- Separate what users actually reported from the team's interpretation, and avoid combining several incompatible journeys into one smooth story.
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 Customer Journey 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: Map stages, user goals, touchpoints, friction and improvement opportunities. Use the following task-specific layout guidance when translating the image into editable elements: Align stages along one journey and connect each opportunity to a concrete friction point. Keep evidence close to the observation it supports.
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. Align stages along one journey and connect each opportunity to a concrete friction point. Keep evidence close to the observation it supports. Keep navigation outside exported slide content. Keep observed evidence separate from assumed emotions.
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 Customer Journey Deck Design Prompt
Use this customer journey deck design prompt to map stages, user goals, touchpoints, friction and improvement opportunities.
The reference is an AI-generated concept. The instructions below describe what to build and test; the image does not demonstrate working behavior.
Separate Observed Friction from Assumed Emotion
A customer journey deck maps a task over time.
Stage labels are useful only when goals, touchpoints and evidence explain what actually happens at each stage. Align stages along one journey and connect each opportunity to a concrete friction point. Keep evidence close to the observation it supports.
From the Prompt
Align stages along one journey and connect each opportunity to a concrete friction point.
Make It Your Own
Map [STAGES] with user goals, touchpoints and observed friction. Attach [EVIDENCE] to findings and label inferred emotions or untested opportunities explicitly.
Prepare the Customer Journey Deck Content
Stages run left to right while goals, touchpoints and evidence occupy separate rows. Prepare observations for each stage rather than inferring the whole journey from a funnel diagram.
Choose a specific customer scenario and gather stages, goals, touchpoints, observed friction and opportunities. Label assumed emotions rather than inventing a research voice.
From the Prompt
Map stages, user goals, touchpoints, friction and improvement opportunities.
Make It Your Own
For [PROJECT], use [APPROVED_CONTENT] as the source for this customer journey deck. Choose a specific customer scenario and gather stages, goals, touchpoints, observed friction and opportunities. Label assumed emotions rather than inventing a research voice. Identify missing inputs before replacing them with demonstration content.
Check a Claimed Pain Point
The lower rows explicitly distinguish assumed emotions from friction and possible improvements. Validate assumptions with research and trace each opportunity to a specific observed problem.
Trace a friction statement to an observation. If it is only a hypothesis, the slide should propose a way to investigate it rather than presenting it as established behavior. Walk through the journey from the customer's perspective. Separate what users actually reported from the team's interpretation, and avoid combining several incompatible journeys into one smooth story.
From the Prompt
Keep observed evidence separate from assumed emotions.
Make It Your Own
Review the customer journey deck against this requirement: Keep observed evidence separate from assumed emotions. Walk through the journey from the customer's perspective. Separate what users actually reported from the team's interpretation, and avoid combining several incompatible journeys into one smooth story. Preserve approved content and revise only the parts that fail this check.
Review Your Customer Journey 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.
- Walk through the journey from the customer's perspective. Separate what users actually reported from the team's interpretation, and avoid combining several incompatible journeys into one smooth story.
Follow-Up Prompt
Use this after the first result. It narrows the revision to the most important part of this task.
Refine the current customer journey deck. Walk through the journey from the customer's perspective. Separate what users actually reported from the team's interpretation, and avoid combining several incompatible journeys into one smooth story. Preserve the approved content and visual direction; change only the parts needed to resolve these issues.
