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: Change Management Deck.

## Required content and structure

Explain the change, affected workflows, rollout stages, support and feedback channels.

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

Define the change, affected teams, current and future workflows, rollout dependencies and support routes. Separate approved dates from targets that still depend on decisions.

## Layout and behavior

Explain what changes for each audience and what they need to do. Pair rollout stages with readiness conditions, training and feedback channels.

## Task-specific acceptance check

- Show confirmed dates and unresolved dependencies separately.
- Ask whether a team member can identify the action required of them.
- Keep unresolved dependencies visible and avoid presenting a proposed process as already mandatory.

## 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 Change Management 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: Explain the change, affected workflows, rollout stages, support and feedback channels. Use the following task-specific layout guidance when translating the image into editable elements: Explain what changes for each audience and what they need to do. Pair rollout stages with readiness conditions, training and feedback channels.

## 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. Explain what changes for each audience and what they need to do. Pair rollout stages with readiness conditions, training and feedback channels. Keep navigation outside exported slide content. Show confirmed dates and unresolved dependencies separately.

## Visual comparison and delivery

1. 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.
2. Then test the narrow layout without squeezing desktop text into tiny labels.
3. 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.