Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- A realistic supplied manual process
- Verified product steps
- Matched illustrative inputs
- A shared completion definition
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Define the task
Show one illustrative request and the need to pass its context to a colleague.
On screen:Hand over the request and its context.
- 02
5–11s
Show the manual path
Present the supplied manual steps neutrally: record the note and separately identify the recipient.
On screen:The note and recipient sit in separate places.
- 03
11–17s
Introduce the product path
Show the approved product record with the same example request.
On screen:Bring the handoff into one record.
- 04
17–23s
Demonstrate the difference
Use verified states to place the note and owner together. Preserve any actual manual prerequisite.
On screen:Keep the note and owner together.
- 05
23–27s
Inspect equivalent completion
Hold both final representations or the product result with the completion condition clear.
On screen:The same handoff, with connected context.
- 06
27–30s
Close accurately
Show approved identity and current access status.
On screen:See current availability.
Make it your own
- Manual process
- Use a supplied realistic sequence.
- Matched input
- Keep task and example content equivalent.
- Completion
- Define the same finish condition for both paths.
Keep the comparison fair
The request example is illustrative. The comparison concerns information placement, not measured time saved or guaranteed fewer errors.
Use the real supplied workaround, even if it is less visually dramatic than a pile of chaotic windows. Added failures would change the evidence.
Adapt the depth
For a 60-second version, explain the most important prerequisite in each path. For a 15-second version, show one representative step and the equivalent final states rather than speeding through every action.
A side-by-side layout works only when both paths remain legible. Sequential matched views may be clearer for dense interfaces.
Review checklist
- The two paths have equivalent starting material and completion.
- The manual process is represented neutrally.
- Required work is not hidden.
- No speed or savings metric is fabricated.