Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- The exact control labels and default state.
- Verified effects of each option.
- Any role restriction or save requirement.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Create a 30-second planning explanation for a fictional task tool adding an optional Show completed tasks setting to a personal list view. Begin with the supplied initial view and make its current selection explicit. Introduce “Choose whether completed tasks appear in this view.” Show the exact option labels and the verified visibility difference. Keep the same illustrative task identifiers before and after the change. Use a deliberate selection followed by the real save action if the workflow requires one. Hold on the confirmed saved preference and resulting list. Do not depict hidden tasks as deleted, archived or reassigned. Do not imply that another member's view changes unless the product owner confirms that scope. Keep the tone informational rather than treating either option as correct for everyone. End with the selected preference and the approved way to restore the other view. If persistence or scope is undocumented, mark that dependency instead of presenting a guessed saved state.
Make it your own
- Control and options
- Supply exact labels and the actual initial state.
- Bounded effect
- Describe which list and task visibility the setting changes; do not imply deletion, archiving or a team-wide effect.
- Save behavior
- Specify whether selection saves immediately or requires confirmation.
Confirm what the choice controls
Record affected and unaffected behavior before drafting. In this illustrative example, the choice changes whether completed tasks appear in a personal view. Confirm that hiding is the correct description and that task records are not changed. The final list should retain the same active-task identifiers so the viewer can connect the selected option to its bounded effect.
Adapt for personal or administrative scope
For a personal view preference, keep the account and list context visible. For an administrator-controlled default, identify the verified workspace scope and whether members can choose a different view. These are separate variants; do not reuse the personal-view ending when the actual setting affects other people.
Repair copy that makes the choice sound mandatory
Replace “Turn this off to work better” with the tradeoff: showing completed items provides task history in the view, while hiding them focuses the displayed list on the remaining items, if those are the verified options. Do not animate hidden records into a trash icon. If saved-state evidence is missing, label the scene as a preview instead of asserting persistence.
Review checklist
- The initial visibility option is explicit.
- The same task identifiers make the view change traceable.
- Optional does not become mandatory through the copy.
- The result shows the actual saved preference.
- Hidden tasks are not presented as deleted or changed records.