SynthMock
A storyboard review is most useful when it catches a weak product story before lighting and export make it expensive to change. Give each shot a purpose, a source state and a clear relationship to its neighbors.
Try it in SynthMock
Start with a Duo scene.
Use a reusable template as your starting point, then apply the choices in this article.
A paid plan is required to use templates and export.
Review information before polish
A rough contact sheet can reveal that three shots repeat the same view or that the app remains unreadable until the end. These are structural decisions. Refining reflections first can make them harder to challenge because the team has already invested in the look.
For a proposed six-shot sequence, attach one sentence to each representative frame. Describe the information added: identify the cover task, reveal the expanded workspace, inspect one detail, or establish the final hero. A sentence such as make it look cool does not tell reviewers what the shot contributes.
A useful shot-sheet structure
Keep the sheet compact enough to review as a whole. Add exact settings only where another person needs them to understand or reproduce a decision.
| Column | Question it answers |
|---|---|
| Representative frame | What does the viewer actually see? |
| Product purpose | What new information does this shot add? |
| Source state | Which task and screen artwork should be visible? |
| Start and end | How does the movement connect to adjacent shots? |
| Reading moment | Where can important content be understood? |
| Open issue | What must be resolved before final export? |
Inspect transitions as their own moments
A contact sheet of beautiful endpoints can hide a bad journey. Scrub the joins, check that effect spans cover the intended shots, and confirm that the next starting pose matches the previous ending pose where continuity is intended. Review the physical fold and its screen optics with the final settings.
Then watch the rough from beginning to end without stopping. Decide whether to remove a redundant shot, simplify a source or change the final composition. Record the decisions so later reviews do not reopen settled questions accidentally. A final render should confirm an approved story, not be the first time anyone discovers that the device spends most of the sequence hiding the app.
See a Duo sequence in motion
Final pass
Before you call it finished
- Give each shot a distinct information goal.
- Inspect the joins as well as representative frames.
- Record unresolved issues before approving a final render.
Make the next version yours.
Explore Duo templates ↗