Who this is for: Editors planning readable product demonstrations.
What to prepare
- Task storyboard
- Exact interface labels and callout copy
- Observed processing states
- Target runtime and viewing context
Label every beat by its job
Mark each storyboard interval as action, processing, inspection or explanation. Action shows a user input. Processing shows that the system is working. Inspection lets the audience read the result. Explanation adds context that the interface alone does not provide.
Several jobs can overlap, but do not introduce a new callout while the viewer is still trying to identify the changed field. A quiet hold can be useful work. Removing every pause may leave a film that looks energetic but cannot be followed.
Illustrative 30-second timing pass
This planning example follows fictional report “Sample review queue.” A configured account and a verified reporting workflow are prerequisites. These intervals are proposed editing choices, not measured response times.
- 0–4: explanation. State the question: “Which requests still need review?” Keep the report name visible.
- 4–8: action. Open the status filter and select Awaiting review; hold long enough to read the option.
- 8–11: processing. Use observed feedback. If actual waiting is shortened, identify the elapsed-time cut.
- 11–19: inspection. Show the two illustrative matching rows with the active filter still visible.
- 19–25: explanation. Highlight the oldest example request and explain why it is the next item in this demonstration.
- 25–30: inspection and close. Hold its detail panel with the same identifier and status.
Cut an extra subject before cutting comprehension
Suppose the first draft also opens the chart settings and changes the color palette. Removing that detour saves time without weakening the task. Cutting the results hold instead would preserve more features but remove the evidence the audience needs.
If a filter has an important second condition, show it and extend or simplify the film. Do not omit the condition and leave a result that the shown input cannot produce. Consequential choices deserve time even when their controls look ordinary.
Review the reading load at the intended size
Play or step through the draft at its intended display size. Ask a reviewer to identify the selected filter and the resulting record before advancing. Use what they miss to revise holds; do not present this informal exercise as a benchmark.
For a shorter version, reduce the number of records inspected and remove a secondary explanation. Preserve the starting question and final proof. If narration is added, leave room for its meaning to finish before the screen changes to another subject.
Review checklist
- Each interval has a comprehension purpose.
- Edited waits do not imply measured product speed.
- The result receives a readable hold.
- Any shorter cut still includes prerequisites and proof.