mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-11-15 22:08:03 +00:00
71 lines
2.7 KiB
Plaintext
71 lines
2.7 KiB
Plaintext
---
|
|
title: "Create a faceless explainer"
|
|
description: "Turn notes, an article, or a difficult idea into a visual explanation without product footage."
|
|
---
|
|
|
|
Use a faceless explainer when the source is an idea or piece of text—not a product website or existing talking-head video.
|
|
|
|
The agent invents the visual language from typography, diagrams, abstract graphics, data visualization, icons, and generated media.
|
|
|
|
Use a [product and website video](/guides/product-launch-video) when the real product interface should provide the visual proof. Use captions or a recut when existing footage must remain underneath.
|
|
|
|
## Start with the point
|
|
|
|
```text
|
|
/hyperframes Create a 60-second explainer from the attached notes.
|
|
The audience is new product managers. Explain why confidence intervals
|
|
matter without assuming a statistics background. Calm, editorial, and
|
|
diagram-led. End with one practical rule they can remember.
|
|
```
|
|
|
|
Include:
|
|
|
|
- the source text or topic;
|
|
- what the audience already knows;
|
|
- the one idea they should remember;
|
|
- the desired length and format;
|
|
- whether narration is wanted;
|
|
- claims or examples that must remain exact.
|
|
|
|
## Approve the explanation before the visuals
|
|
|
|
Confirm:
|
|
|
|
- the question the opening creates;
|
|
- what the audience already knows;
|
|
- the minimum sequence needed to explain the idea;
|
|
- which facts or examples require verification;
|
|
- the visual language and narration choice;
|
|
- the one conclusion the viewer should remember.
|
|
|
|
## Review the explanation
|
|
|
|
Check the storyboard before judging visual polish:
|
|
|
|
1. Does the opening establish the question?
|
|
2. Does each scene add one useful idea?
|
|
3. Are examples concrete?
|
|
4. Does the visual make the idea easier, or merely decorate it?
|
|
5. Can the audience repeat the conclusion afterward?
|
|
|
|
Use the [Storyboard](/studio/storyboard) for the reasoning and [Studio](/studio) for timing, type, diagrams, and animation.
|
|
|
|
## Common problems
|
|
|
|
| Problem | Better direction |
|
|
| --- | --- |
|
|
| The visuals decorate but do not explain | Ask what each visual makes easier to understand. |
|
|
| Too many abstract claims arrive at once | Use one concrete example before the general rule. |
|
|
| The pace is fast because the script is crowded | Remove ideas rather than shortening every hold. |
|
|
| A generated statistic sounds authoritative | Verify the source or remove the claim. |
|
|
| Every scene uses a different visual metaphor | Choose a small, consistent visual system. |
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="Review in Studio" icon="palette" href="/studio">
|
|
Refine the storyboard, typography, diagrams, timing, and animation.
|
|
</Card>
|
|
<Card title="Choose another workflow" icon="route" href="/workflows">
|
|
Return to the source-and-outcome chooser.
|
|
</Card>
|
|
</CardGroup>
|