Who this is for: Design teams communicating a product concept.
What to prepare
- Approved prototype exports
- Implementation-status register
- Exact design question
- Unresolved decision list
Scene-by-scene storyboard
30-second planning sequence · illustrative copy and visual direction
- 01
0–5s
Declare the concept
Show the prototype overview with a persistent label that will survive every crop.
On screen:Prototype concept · Not a released workflow
- 02
5–11s
Describe the intended task
Focus the proposed sample request list and identify the design question.
On screen:Help reviewers find the next request
- 03
11–17s
Show the proposed selection
Use supplied concept frames to explain selecting R-074; keep the concept label visible.
On screen:Proposed request selection
- 04
17–23s
Inspect the proposed detail
Show the designed status and reviewer fields, avoiding claims of saved behavior.
On screen:Proposed review detail
- 05
23–27s
Name unresolved choices
Display the specific open decisions beside the relevant region.
On screen:Open: save behavior and reviewer permissions
- 06
27–30s
Request focused feedback
Hold the concept overview and a precise review prompt.
On screen:Can you identify the next action?
Make it your own
- Design question
- Choose the precise navigation, layout or task decision the concept is meant to explore.
- Frame status
- Classify each supplied frame as a concept or verified reference and preserve the concept label through crops.
- Unresolved decisions
- Name the remaining behavior or permission questions and request focused feedback rather than implying release readiness.
Prepare design intent
Supply approved concept frames and a per-screen status register. Separate implemented references from proposals. A polished mockup does not establish working search, persistence or permissions.
Adapt the feedback goal
For navigation feedback, emphasize labels and hierarchy. For a field-layout decision, use a matched comparison of alternatives. Keep the ending focused on a design question rather than a signup or availability promise. A 60-second version can compare one alternative.
Review concept labels
Ensure the label remains visible in detail crops and thumbnails. If a later product build implements the flow, replace the assets and verify behavior before removing the concept framing. Do not inherit a shipping claim from an approved design.
Review checklist
- Concept status remains visible.
- Proposed behavior is not described as released.
- The ending asks for focused design feedback.