Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- The approved bulk action and eligible item rules.
- Matching before, selected and confirmed-result screens.
- Any required confirmation, exceptions or undo behavior.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second update explanation for a fictional request tool adding bulk owner assignment. Use five clearly labeled illustrative requests, of which three are eligible for the demonstrated action. Show the initial list, then select the three intended records one at a time or through the verified selection control. Keep the count “3 selected” visible. Open the actual bulk-action control, choose the supplied example owner and include the required confirmation step. Hold on the resulting list with those same three records showing the new owner. Leave the other two records visibly unchanged. Do not imply that selection affects hidden pages or all filtered results unless the product owner confirms that scope. Do not invent undo, instant completion or exception handling. End by restating the eligible scope and the verified result rather than claiming a productivity percentage.
Make it your own
- Bulk action
- Replace owner assignment with one supported operation.
- Selection scope
- Specify visible items, selected items or all results exactly as implemented.
- Exception rule
- Supply handling for ineligible records and partial failures.
Prepare a bounded example
A small labeled list makes the scope inspectable. Include at least one unchanged item when that accurately represents the product. Avoid sample records whose eligibility is ambiguous; otherwise the viewer may mistake a permission exclusion for a random omission.
Adapt for larger selections honestly
If the real use case spans pages, show the product's scope label and explain its meaning. An editorial counter can summarize a supplied selection but must not replace the actual confirmation rule. Longer versions can demonstrate one supported exception after the successful path.
Fix an unproven result
If the ending only shows a toast, add a verified inspection of the affected records where feasible. If only some records changed, disclose that result rather than animating every row into success. The selection count and outcome should agree with the same example data.
Review checklist
- Selection count matches the demonstrated records.
- The commit step is separate from selecting items.
- Unselected records remain unchanged in the example.
- Hidden-page and exception scope is not invented.