Who this is for: Product teams preparing a timed storyboard for an original launch asset.
What to prepare
- An approved product principle
- One design choice that expresses it
- Evidence of the resulting behavior
- Current identity and availability
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
State the principle
Show the approved principle as a readable sentence without abstract decorative clutter.
On screen:Important context should stay beside the work.
- 02
5–11s
Name the design choice
Introduce the supplied product view and identify the relevant layout relationship.
On screen:The note and owner share the request view.
- 03
11–19s
Demonstrate the behavior
Use approved states to inspect one illustrative request with its note and owner.
On screen:Open one request and see its context.
- 04
19–25s
Connect choice to principle
Hold the same view with a restrained highlight linking the related fields.
On screen:The design keeps this context together.
- 05
25–30s
Close with identity
Show approved product identity and current access status.
On screen:Explore the product's current availability.
Make it your own
- Principle
- Use approved wording without fabricated attribution.
- Design choice
- Identify a concrete inspectable decision.
- Evidence
- Show actual supplied behavior rather than a symbolic promise.
Ground the principle
The illustrative principle concerns information placement. It does not prove universal clarity, productivity or user satisfaction. The evidence is the supplied relationship between note, owner and request.
Use a genuine approved principle rather than inventing a founder quote or brand manifesto.
Adapt the claim
For a different product, choose a design decision that the viewer can inspect: a visible status, a deliberate confirmation or a stable reference view. Avoid principles so broad that almost any screen could illustrate them.
A 60-second version can compare an approved alternative and explain the tradeoff. A 15-second version should keep only the principle, the strongest proof detail and the identity.
Review the tradeoff
If the design choice has a relevant limitation, acknowledge it in supporting copy rather than claiming the principle solves every task.
The sequence should still communicate useful behavior if the principle line is removed. If only the slogan carries meaning, strengthen the demonstration.
Review checklist
- The principle connects to a visible design choice.
- No universal outcome is inferred.
- The example is explicitly illustrative.
- The final access statement is accurate.