Who this is for: Product marketers and motion designers briefing a specific software update.
What to prepare
- The exact query and controlled dataset.
- Verified old and new results for that query.
- The release explanation for the changed behavior.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second search-update explanation for a fictional knowledge tool. Use the same labeled illustrative document set and the same supplied query in both versions. The example change is support for searching approved document tags; do not assume any other ranking improvement. First show the old query and its verified result state with a “Previous behavior” label. Cut to the new version without changing the query or dataset. Identify the matching tag on the relevant document and show its verified appearance in the results. Retain the query, active filters and tag label together long enough to connect cause and result. Do not fill the old screen with deliberately poor results or add invented relevance scores. End with “Search the supported tags as well as the documented existing fields,” adjusted to the actual release scope. Include any indexing delay or access condition only when confirmed.
Make it your own
- Controlled query
- Use one exact query in both versions.
- Changed search rule
- Name the documented addition rather than a broad quality claim.
- Result evidence
- Supply matching captured or approved results from the controlled dataset.
Control the query context
Keep account permissions, filters and dataset version aligned. A newly added document can explain a result difference without any search-engine change. Record those conditions in the production packet before interpreting the pair.
Adapt to another documented change
For a new filter, hold the query constant and show the filter as the changed input. For a query parser change, use the owner's approved syntax example. Do not mix several search changes into a single comparison unless each cause can be explained.
Repair relevance overclaims
Replace “Always finds the right answer” with the specific behavior shown. If source results are unavailable, present an explicitly labeled conceptual diagram instead of a fabricated before-and-after product demonstration. Keep the final result linked to the supplied query.
Review checklist
- Query, dataset and access conditions are controlled.
- The changed rule explains the shown result.
- No fabricated scores or intentionally misleading old results appear.
- The conclusion stays within the documented search scope.