Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- The approved reproduction conditions.
- Old symptom evidence or a clearly labeled reconstruction.
- Verified corrected behavior and remaining scope.
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 file tool correcting a stale filename after attachment replacement. Establish a draft record and two labeled illustrative files. Identify the previous symptom: the old filename could remain visible after replacement in the affected workflow. If the old state is reconstructed, label it as an illustration. Show the same replacement action in the updated version, including the real completion feedback, then hold on the confirmed new filename. Keep the record and file identities consistent. Use the bounded line “The filename refreshes after the supported replacement action,” adjusted to the approved facts. Do not say all upload problems are fixed or imply a new transfer-speed result. End with the affected scope and the verified support route if the symptom persists.
Make it your own
- Symptom
- Name the observable defect rather than only its technical cause.
- Conditions
- Keep the required record state, role and input consistent.
- Correction scope
- Use the exact behavior verified by the release owner.
Prepare a faithful comparison
A new upload is not a valid substitute for attachment replacement when that is the affected path. Capture the relevant conditions and identify the released version. Keep any unrelated improvements outside this brief.
Adapt when old footage is unavailable
Use a labeled symptom diagram or concise description rather than a fake recording. The corrected behavior still needs evidence. Do not make a reconstructed failure look like a newly observed production incident.
Repair overbroad reassurance
Replace “Everything works now” with the specific correction. If the confirmed state is missing, do not use an animated checkmark to imply it. Any troubleshooting step in the ending must come from the approved support procedure.
Review checklist
- The shown action matches the reported defect conditions.
- Reconstructed symptom imagery is labeled.
- The new state is supported by actual release evidence.
- The ending avoids system-wide reliability claims.