Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- Approved feedback themes with source provenance.
- The verified revision and its current scope.
- Permission-cleared quotations only if quotations will be used.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second beta-update explanation for a fictional note tool. The supplied feedback theme is difficulty telling suggested groups from manually edited groups. Use that theme only if the team provides evidence and approved wording. Open with a neutral summary, “Feedback highlighted a need for clearer group status.” Do not invent a quote, user name or number of requests. Show the previous and updated status treatment using matched illustrative notes. Hold on the verified new label and explain exactly what it indicates. If the revision is still limited to beta participants, keep that status visible. End with a focused feedback request asking whether the status distinction is understandable in the supported task. Do not claim the change solved every reported problem or produced a measured satisfaction increase.
Make it your own
- Feedback theme
- Use a source-grounded summary, not an invented customer statement.
- Revision evidence
- Supply matched states that isolate the actual change.
- Follow-up question
- Ask about the specific uncertainty the revision addresses.
Verify the theme before making it the opening
Separate a repeated theme from one illustrative comment and from the team's own interpretation. The script can describe a design decision without invoking customers at all when evidence is insufficient. Public attribution also needs the appropriate permission.
Adapt the treatment without fake testimonials
A short neutral theme card is often enough. If an approved quotation is essential, reproduce only the authorized wording and context. Do not combine several comments into a quotation attributed to one invented person.
Repair causal overstatement
Show the revision and ask a bounded follow-up question. Replace “Users love the new design” with the observed change unless a supported evaluation exists. Keep the sample notes marked illustrative so they are not mistaken for submitted customer data.
Review checklist
- The feedback theme has a traceable approved source.
- Illustrative examples are separate from reported experiences.
- No fabricated quote or demand count appears.
- The conclusion stays within the revision's scope.