Choose an emotion that fits the message
A reference may use surprise, curiosity, frustration or calm explanation. Decide what role the emotion plays in the opening and whether it fits the intended viewer’s task. The emotion is a creative choice; it is not proof that a customer experienced it.
Plan three supported pairings
For a fictional note feature: surprise, “wait, the next steps are in the note”; curiosity, “where did the next action go?”; calm explanation, “open the call note to check the next action.” Each needs the actual screen showing the supported feature. These are draft pairings, not recorded outputs or measured winners.
| Emotion | Example direction | Review |
|---|---|---|
| Surprise | The next steps are here | Does the screen show the section? |
| Curiosity | Where is the next action? | Does the demo answer it? |
| Calm | Open the call note | Are the steps accurate? |
Avoid misleading performance
Do not make a generated presenter imply a genuine personal discovery or testimonial. Avoid exaggerated emotions that suggest the app did something it cannot do. Match the exact overlay and the next screen, and preserve any conditions such as manual entry.
Review actual variants
If creating multiple versions, keep the task and product proof consistent and document the genuine differences in expression. Record the actual assets, permission and feedback before describing a review. Different audiences and distribution conditions prevent a simple attribution of results to emotion alone.
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.
Audience and task: __. Verified product fact: __. Planned words and action: __. Asset source and permission: __. Actual review observations: __.Browse the founder guide library for the next task in your workflow.