Who this is for: Teams producing focused product support videos.
What to prepare
- Symptom screen
- Evidence of the specific cause
- Supported corrective action
- Successful retry state
Scene-by-scene storyboard
60-second planning sequence · illustrative copy and visual direction
- 01
0–8s
Name the symptom
Show the sample request list without R-086 and keep the current filters visible.
On screen:Cannot find sample request R-086
- 02
8–18s
Inspect the scope
Highlight the active Approved filter and the current workspace. Avoid implying the record was deleted.
On screen:Check the active view conditions
- 03
18–29s
Compare the known record
Use supplied evidence that R-086 is Awaiting review, clearly labeled as the known sample record.
On screen:R-086 is Awaiting review
- 04
29–39s
Apply the bounded fix
Clear the Approved filter through the actual control, preserving other view settings.
On screen:Remove the conflicting status filter
- 05
39–49s
Retry the original task
Search or locate R-086 in the resulting list using the verified product behavior.
On screen:Find R-086 again
- 06
49–56s
Verify the result
Open the matching request and hold its identifier and status.
On screen:R-086 is visible in the corrected view
- 07
56–60s
State the limit
Close with the diagnosis specific to this example.
On screen:This case was caused by the active filter
Make it your own
- Known symptom and cause
- Supply evidence linking the chosen symptom to the specific cause before prescribing a fix.
- Corrective action
- Use the actual bounded control or procedure that addresses that cause.
- Retry proof
- Inspect the same original object and task after the correction, keeping the conclusion case-specific.
Prepare the known cause
Supply evidence connecting the symptom to the filter. Do not prescribe clearing filters as a universal fix for missing data. Permission, workspace or deletion issues would require different investigation.
Adapt the diagnostic path
For a validation problem, inspect the actual message before correcting the input. For 30 seconds, use one known cause and one verified retry. Keep the symptom, inspection and result; remove decorative context first.
Review the scope of the fix
The final screen should prove the original task now works for the same object. Do not claim the underlying product is repaired or all missing records are recovered. This storyboard is a hypothetical teaching case until matched to real product evidence.
Review checklist
- Diagnosis precedes the correction.
- The fix addresses the observed cause.
- The original object is verified after retry.