Who this is for: Teams demonstrating configuration choices.
What to prepare
- Matched before-and-after screens
- Actual setting control
- Save and scope evidence
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second illustrative comparison in a fictional request workspace. Use supplied screens to change the default list grouping from None to Status, if that option exists. Show the initial flat list with stable sample records. Open the actual setting, select Status and perform the verified save or apply action. Return to the same list, same filters and same records, now grouped by status according to the observed behavior. Preserve record counts and titles. Use “Same requests, grouped by status” as the explanatory line. Do not imply the setting changes request statuses or improves productivity. If grouping is a temporary view choice rather than a persisted setting, use that accurate wording and avoid a save claim.
Make it your own
- Setting
- Choose one supported variable.
- Scope
- Identify personal, view or workspace scope.
- Observed effect
- Show the exact consequence supported by the paired screens.
Control other variables
Capture both states with the same workspace, date range, sort and sample records. A changed dataset prevents viewers from isolating the setting’s effect.
Adapt the comparison
For a display-density option, hold the same records and explain the layout difference. For a notification preference, show verified configuration without inventing delivery results. Match the proof to the type of setting.
Fix false causality
If records disappear in the after view, check whether a filter changed accidentally. If the setting applies only to the current user, do not describe it as a workspace-wide change. Retain the actual scope label.
Review checklist
- Only the intended variable changes.
- The effect is not overstated.
- Persistence and scope match the product.