Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- Verified desktop and mobile paths for the same task.
- Matching illustrative object and account state.
- Supported device, version and role conditions.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second planning sequence for a fictional review tool that newly supports resolving one's own comment on mobile. Begin with the familiar comment thread on desktop, identifying the task without replaying the whole workflow. Cut to the same illustrative thread on the approved mobile interface. Preserve the comment text and author identity. Show the verified mobile action and hold on the resolved state. Use the line “Resolve your own comments on mobile,” qualified by the actual release scope. Do not claim full desktop parity, offline use or cross-device synchronization unless supplied. Keep device framing secondary to readable controls. If the thread is merely a matched example rather than a recorded live handoff, make the editorial transition clear. End with supported availability and the visible result, not a montage of unrelated mobile screens.
Make it your own
- New mobile task
- Name one action verified in the mobile release.
- Matching object
- Keep the same sample content and identity on both devices.
- Support scope
- Supply approved device, version and role conditions.
Prepare matched device evidence
Check that both interfaces show the same object and user role. A desktop administrator screen paired with a mobile member screen can hide a permission difference. Capture legible mobile states rather than shrinking a desktop layout into a phone frame.
Adapt when the audience already understands the desktop task
Shorten the desktop reference to one stable frame and give the mobile path more time. For new viewers, add a sentence explaining what resolving the comment means. Retain any mobile-specific exception where it affects the decision.
Repair parity overclaims
Replace “Everything, anywhere” with the actual supported action. If the result requires a connection or a later refresh, use the verified behavior instead of an instant synchronized flourish. The final scope line should match the demonstrated release.
Review checklist
- The claim names one supported mobile task.
- The example object and role match across devices.
- The mobile controls remain readable.
- Offline or full-parity claims are not inferred.