Who this is for: Product marketers and motion producers preparing an original launch brief.
What to prepare
- One approved screenshot at useful resolution
- The exact region and label supporting the promise
- Approved product identity and availability copy
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second launch sequence using only SCREENSHOT as product evidence. Introduce PRODUCT_NAME and the specific task described by TASK_LINE. Treat the screenshot as a static source, not an interactive recording. Do not create new controls, change displayed values or animate a cursor click into an invented resulting state. Begin with the whole screen long enough to establish orientation. Move toward FOCUS_REGION while preserving ORIENTATION_ANCHOR. Place CALLOUT_TEXT outside important UI and connect it unambiguously to the supplied element. Allow a readable hold before introducing a second label. Use no more than the supplied callouts. Return to a wider composition that makes the relationship between the highlighted area and the product clear. Keep the final product state identical to the source image. End with CURRENT_STATUS and NEXT_ACTION. Use a restrained background and keep essential meaning visible without narration. If the required crop becomes unreadable or loses its anchor, propose a different framing rather than recreating the interface.
Make it your own
- FOCUS_REGION
- Name the exact area visible in the screenshot.
- ORIENTATION_ANCHOR
- Choose a nearby title or navigation label that remains in frame.
- CALLOUT_TEXT
- Explain only what the image establishes.
- CURRENT_STATUS and NEXT_ACTION
- Use the verified access state and supported destination.
- SCREENSHOT
- Supply the exact approved source image, its implementation status and any region that must not be cropped.
- PRODUCT_NAME and TASK_LINE
- Use approved product spelling and one task statement the static image can actually support.
Prepare the single source
For an illustrative planning board, the focus might be a visible owner field. Supply a clean screenshot with fictional task names and identify the board title as the orientation anchor. A callout can explain where the owner appears; it cannot prove how assignment works.
If the source contains private data or an obsolete control, replace the source before production. A crop that hides one issue may expose another when the camera moves.
Adapt the framing
For a compact viewport, begin nearer the useful region and preserve the title rather than showing an unreadable full-screen miniature. For a wider composition, keep explanatory copy beside the image instead of covering the interface.
If two callouts are essential, give them separate reading moments. A second callout should answer a different question about the same image, not introduce an unsupported feature.
Correct misleading movement
If motion implies that a control was activated, replace the click with a neutral emphasis treatment. If a value changes, restore the original source unless a separate approved state exists.
A static screenshot launch may need a supporting walkthrough for the actual action. That limitation is acceptable; inventing behavior to make the clip feel more complete is not.
Review checklist
- The screenshot remains factually unchanged.
- The focus retains an orientation anchor.
- Callouts do not cover important labels.
- No click or transition invents an unsupported state.