Who this is for: Launch teams translating a specific creative job into a motion brief.
What to prepare
- Two verified participant roles
- One shared object or exchange
- Approved screens for each role
- Access and permission boundaries
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second launch for PRODUCT_NAME around ROLE_ONE and ROLE_TWO. Follow SHARED_OBJECT through one verified exchange. Introduce each role with a readable label and a consistent visual lane. Do not rely on color alone to identify participants. Show ROLE_ONE_ACTION first, then make the handoff explicit before showing ROLE_TWO_ACTION. Keep the shared object's name or identifier visible as it crosses contexts. Use only the supplied role-specific screens. Do not imply that either participant can see private fields or perform controls absent from their verified view. Bring the lanes together only at the confirmed exchange or outcome. Hold the resulting state with each role's contribution clear. Avoid a montage of avatars that suggests more participants or adoption than supplied. End with the product identity, CURRENT_STATUS and the next action appropriate to the intended viewer.
Make it your own
- ROLE_ONE and ROLE_TWO
- Name functional roles rather than vague user categories.
- SHARED_OBJECT
- Track one request, booking or item across the exchange.
- ROLE_ONE_ACTION and ROLE_TWO_ACTION
- Use verified permissions and distinct actions.
- PRODUCT_NAME and CURRENT_STATUS
- Supply the approved product identity and current access state for the intended role.
- Viewer next action
- Choose the actual next step for the audience watching this asset; do not assume both participant roles have the same access route.
Choose one exchange
An illustrative review product could show an author submitting an item and a reviewer returning a decision. The shared item anchors the sequence; the two roles should not appear to have identical controls.
Choose a completed exchange that is supported by the supplied states, or label an intermediate pending state accurately.
Adapt the lanes
Use sequential role scenes on a narrow canvas and a labeled two-lane composition when space permits. Keep the shared object consistent in both layouts.
For a longer explanation, add the prerequisite that determines access rather than introducing unrelated participant types.
Correct role confusion
If a transition makes a private control appear shared, separate the views and label the handoff. If a result is only visible to one role, show that context explicitly.
The ending should address the intended viewer's real next action; do not assume both roles can immediately join or purchase.
Review checklist
- Roles are labeled independently of color.
- The shared object remains identifiable.
- Permissions match the supplied views.
- The handoff and final status are explicit.