Separate the tasks before writing
Two audiences can use the same broad product category for different reasons. Write down the person, the moment and the job they need to do. Then choose a product action that can genuinely support that job. Changing “founder” to “manager” in the same script is not enough if the situation and proof remain identical.
The following fictional examples use a notes product with project call notes and next-step sections. They are planning exercises, not real customer stories.
Script one: preparing a follow-up
Audience: a founder preparing for a follow-up after a discovery call. Speaker: “After a call, check what you agreed to do next before you reply.” Show the project, the call note and its next-step section. Speaker: “Open the note and start with the action you recorded.” The relevant proof is the specific note and section.
If the real product does not include a next-step section, replace the task with a capability you can verify. Do not claim that it writes or sends the reply automatically.
| Brief | Founder follow-up | Teammate handoff |
|---|---|---|
| Moment | After a discovery call | Taking over a project |
| Question | What did I agree to do next? | What context did the team record? |
| Evidence | Call note and next-step section | Project and relevant note |
| Next action | Prepare a follow-up | Understand the handoff |
Script two: handing context to a teammate
Audience: a teammate taking over an existing project. Speaker: “Taking over a project? Start by checking the notes from the last call.” Show the project and the relevant call note. Speaker: “Read the recorded next step before deciding what to do next.” The task is understanding handoff context, not preparing the original caller’s reply.
These scripts use related screens but a different moment, motivation and next action. If the product has no way to share a note with that teammate, do not imply sharing permissions or access; verify access before using the scenario.
Review both versions separately
For each script, match every factual statement to the actual interface and show only data that may be shared. Use a real speaker or an illustrative generated presenter without inventing a personal endorsement. Captions should match speech and stay clear of the control the viewer needs to see.
Ask one intended reader from each group, where available, to explain the task after watching. Record their feedback without fabricating a quote. Different audience fit is a hypothesis to review, not a claim that either version will 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.
Audience A and task: __. Audience B and task: __. Verified features: __. Complete script A: __. Complete script B: __. Access or permission check: __.Browse the founder guide library for the next task in your workflow.