Who this is for: Product teams writing a precise visual brief for a software update.
What to prepare
- The current known-issue record.
- Approved workaround and its limitations.
- A status destination and escalation instructions.
Copyable creative brief
An authored planning example. Replace illustrative details with your approved product facts and assets.
Plan a 30-second notice for a fictional reporting tool with a known issue affecting a particular saved-view refresh. Open with the precise affected condition and avoid alarming unaffected users. Explain that the issue remains open. Show the team's verified temporary path using exact supplied controls; do not invent refresh, reset or deletion steps. Keep the illustrative report identity consistent before and after the workaround. Hold on the result the owner says users should verify, while labeling the path “Temporary workaround.” State any cases where the workaround does not apply. End with the approved status destination and the action to take if the check fails. Do not promise a resolution date, describe the issue as fixed or claim that the workaround preserves all data unless those facts are supplied.
Make it your own
- Affected condition
- Supply the exact scope and relevant exclusions.
- Workaround steps
- Use an approved ordered procedure with no guessed actions.
- Verification and escalation
- Name the expected check and the approved failure route.
Separate issue status from user action
The team can provide a useful next step while the defect remains unresolved. Keep those two facts visible together. A successful workaround demonstration does not change the underlying issue status.
Adapt when the procedure is too long
Use the video to identify the issue and orient viewers to the approved written procedure. Do not compress consequential steps into an unreadable montage. A longer walkthrough can follow one verified path with explicit checkpoints.
Repair unsafe inferences
If the draft suggests clearing data or resetting configuration without approval, remove those steps. If the workaround is conditional, put the condition before the action. The ending should help viewers recognize failure and seek the correct support, not repeat the procedure indefinitely.
Review checklist
- The issue remains accurately labeled as unresolved.
- The procedure is verified for the stated condition.
- No destructive or guessed troubleshooting step appears.
- Failure has an approved escalation path.