Start with the unresolved question
If viewers ask what a problem is and why a product category matters, an explainer may help. If they ask whether your product can perform a task, a demo needs visible product evidence. If they ask how to complete that task themselves, a tutorial should preserve the necessary steps.
These are useful editorial distinctions, not rigid industry definitions. Real assets can combine formats. Choose a primary job so the opening and ending do not compete.
Compare two briefs for the same fictional product
Imagine a fictional booking app for independent tutors. An explainer brief asks: why do missed scheduling details cause confusion? Its outline introduces the problem, describes a shared booking process and gives a qualified next step. It must not invent customer losses to make the problem dramatic.
A demo brief asks: can a tutor change a sample appointment and see the updated booking? Its outline shows the current slot, the real rescheduling control and the confirmed new time. That visible change is evidence an abstract explainer cannot supply.
| Decision or state | Example | Review |
|---|---|---|
| Explainer | Why is a shared booking process useful? | Explain the mechanism without fabricated outcomes. |
| Demo | Can this app move an appointment? | Show the action and confirmed time. |
| Tutorial | How do I reschedule my appointment? | Include prerequisites and necessary steps. |
| Announcement | What changed in the reschedule feature? | Show the released difference and eligibility. |
Choose the evidence before the production style
The same camera style, animation or presenter could appear in either format. An AI presenter does not turn a generic explanation into a product demonstration. Likewise, a screen recording without a clear task may fail to demonstrate anything useful.
Write the claim and the evidence needed to support it. For a tutorial, add prerequisites and recovery steps. For an announcement, add release eligibility. If the necessary evidence does not exist, narrow the brief rather than decorating an unsupported claim.
Avoid building two pages or videos that answer the same thing
If an existing demo already explains the booking task, do not make a second asset with a different label but identical substance. Add the missing prerequisite or context to the existing asset unless the audience’s question truly differs.
Ask a reviewer which question the proposed video answers and what they can do next. If the answer shifts between category education, feature proof and setup instructions, choose one primary purpose and link to the appropriate follow-up.
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 question:
Primary format and reason:
Specific claim:
Evidence required:
What the video deliberately leaves to a follow-up:
Prerequisites or eligibility:
Existing asset to improve instead:
Next-step destination:Browse the founder guide library for the next task in your workflow.