Hand off a product demo brief with fewer ambiguities

Name the viewer, question, runtime and intended placement. State which setup has already happened and which role performs the action. Identify the end state that counts as completion. These choices let the designer make composition decisions without inventing product behavior.

Separate verified facts from creative treatment and open questions. A note such as “make the result feel fast” can accidentally become an unsupported performance claim; specify readable pacing without asserting unmeasured speed.

This sample packet concerns fictional request R-132 and is not a rendered or tested project.

• Viewer and goal: an evaluator should understand how a configured reviewer assigns the next owner of a request.
• Runtime and placement: 30-second planning target for a product explanation page; inspect readability in the actual page layout.
• State inventory: 01-unassigned.png, 02-owner-menu.png, 03-selected.png and 04-saved.png. All show R-132 and the same sample workspace.
• Action list: open Owner, select Example reviewer, activate the verified Save control, then inspect the confirmed field.
• Exact copy: opening “Give this request an owner”; action “Choose the reviewer”; result “Assignment confirmed.” Use the result line only with the saved state.
• Motion direction: stable camera during selection; one close-up with the request identifier preserved; no invented controls or notification effects.
• Open question: whether the queue reorders after saving. Obtain evidence before planning the return shot.

Acceptance means the same request remains identifiable, every action follows the supplied workflow, the selected owner is readable and the final frame proves the assignment. Include a check that captions do not cover the menu or saved value.

Ask the product owner to verify behavior and the content owner to verify wording. Visual approval does not automatically cover product accuracy. Record the exact asset version being reviewed so later swaps do not inherit stale approval.

Deliver full-frame images, approved crops, logo files and a concise source register. Put annotations in a separate note or clearly identified overlay so they cannot be mistaken for native interface elements.

For Animro-oriented planning, the public workflow is framed around brief and assets, storyboard approval and revision. Prepare the packet accordingly: supply the files themselves rather than expecting a direct import from design or product tools.