Define the result and what proves it
Result-first starts with a visible product state, then explains how it was reached. Reaction-first begins with a creator or text reacting to a feature, followed by the product view. In either case the result must be real, understandable and supported by the app. A result cannot be an invented customer outcome or a generated screenshot presented as evidence.
This fictional planning example uses a call note with a next-step section. It does not describe an actual edited video or an experiment.
Plan a result-first sequence
Show the sanitized note and its next-step section. Overlay: “the next step is in the call note.” Then show a reaction and the steps used to open the note. The first frame gives a concrete answer, but it must remain legible and the following shots should explain how to reach it. If the result requires a user to enter information, do not suggest the app created it automatically.
Use result-first when the screen can be understood quickly and the viewer benefits from seeing the destination before the navigation.
| Choice | First thing shown | Check |
|---|---|---|
| Result first | Real note and next-step section | Result is legible and reproducible |
| Reaction first | Feature-matched reaction | Product proof follows clearly |
| Neither | The result is not supported | Revise the claim or capture proof |
| Comparison | Two actual versions | Record audience and sample limitations |
Plan a reaction-first sequence
Open with the exact words “wait, the next steps are right here” and a brief reaction. Cut to the project, open the note and hold the section. This can set up curiosity, but it needs to show the promised feature promptly and accurately. If the first product screen lacks context, add a concise bridge or change the starting frame.
Keep the task, underlying claim and next action consistent between the plans if you later compare them. Do not change several other variables and claim that the opening order alone caused a difference.
Review the real versions before drawing conclusions
If you make both versions, record the actual assets, export dates, captions and distribution conditions. Ask viewers what the product does after one viewing and document real feedback. Platform distribution and audience differences can affect metrics, so small or unequal samples may be inconclusive.
If you do not have both approved clips, treat the comparison as a decision guide. It is not a claim that either version has been tested or is guaranteed to perform better.
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.
Verified result: __. Result-first first frame: __. Reaction-first opening: __. Shared proof: __. Actual review and conditions: __.Browse the founder guide library for the next task in your workflow.