Start with the same product task
A silent reaction can introduce a visual discovery; a talking-head explanation can give context the screen does not make obvious. Both still need a real product recording that demonstrates the promised action. Select the format after identifying what the audience needs to understand.
The fictional example is a notes app with a call note and next-step section. These are planning concepts, not recorded versions or performance results.
Plan a silent reaction version
Opening overlay: “wait, the next steps are right here.” Show a brief reaction, then cut to a sanitized recording opening the call note and revealing the section. The viewer needs to understand the task from the overlay and screen. If the initial product frame is unclear, add a short bridge label or show more context.
The reaction illustrates an emotion. It does not establish that a real customer discovered the feature or that the app automatically created the next steps.
| Decision | Silent reaction | Spoken explanation |
|---|---|---|
| Opening | Short feature-matched overlay | Problem or action in speech |
| Proof | Readable real product screen | Product screen timed to speech |
| Main burden | Enough visual context | Accurate audio and captions |
| Choose when | Discovery is easy to see | The task needs explanation |
Plan a spoken explanation version
Speaker: “After a call, open the project note and check the next-step section.” Show the project and the note while the instruction is spoken. Speaker: “That is where you can review the action you recorded.” Use the real interface labels and disclose any manual setup needed for the feature.
Speech gives the viewer more context but requires a clear transcript, delivery and captions that do not hide the control. It may be unnecessary if the action is obvious from the first screen and a brief overlay.
Choose with a comprehension review
Use the reaction plan when the feature is visible quickly and a short opening sets up the discovery. Use the explanation when the viewer needs a reason, condition or instruction before the screen makes sense. If neither version can demonstrate the claim, change the message or capture better proof.
Before publishing, record both actual versions only if you have permissioned assets and capacity, then ask viewers what action the app supports. A planning comparison cannot prove which format will earn more views or customers.
Copy the planning worksheet
Use this worksheet in your own notes. Fill it with verified product details and actual review observations before sharing an asset.
Viewer task: __. Verified feature: __. Silent opening and proof: __. Spoken script and proof: __. Choice and reason: __. Review: __.Browse the founder guide library for the next task in your workflow.