Who this is for: Product teams planning an accurate update storyboard.
What to prepare
- Approved issue scope and affected conditions.
- Old symptom evidence or labeled reconstruction.
- Corrected-state evidence and support instructions.
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Symptom
Show a labeled illustration of the old filename remaining after a replacement.
On screen:Old filename after replacing an attachment?
- 02
5–10s
Affected condition
Identify the draft-record replacement workflow, excluding unrelated uploads.
On screen:This concerns the documented replacement path.
- 03
10–18s
Corrected action
Show the same illustrative record using the approved updated workflow.
On screen:Replace the attachment through the verified controls.
- 04
18–25s
Proof
Hold on completion feedback and the matching new filename.
On screen:The confirmed filename now matches the replacement.
- 05
25–30s
Scope
Display the bounded correction and approved support route.
On screen:Other attachment issues remain outside this claim.
Make it your own
- Symptom
- Use the observable problem.
- Condition
- Keep the affected workflow precise.
- Correction
- State the behavior actually verified.
Match the reproduction
Keep the record state, input type and role aligned between versions. A successful first upload does not prove a correction to replacement behavior. Capture the released version that contains the fix.
Adapt missing old-state evidence
Use an explicitly labeled illustration when historical footage is unavailable. Do not create a fake screen recording. The updated state still needs evidence, and the final claim must remain tied to the documented conditions.
Review reliability language
Remove blanket assurances such as all file problems are fixed. A bounded correction can be useful without a system-wide guarantee. Any retry or recovery instruction needs approval from the support procedure.
Review checklist
- The comparison exercises the affected path.
- Reconstruction is labeled.
- The final filename matches the replacement example.
- Reliability claims stay within the fix scope.