One idea per scene means every scene in an explainer video teaches exactly one thing — a thing you can state in a single sentence before the scene is built. If you can't write the sentence, the scene isn't understood yet; if the sentence needs an "and," you're looking at two scenes.
Across sixty-odd produced explainers and every review note they earned, this is the rule the other rules reduce to. Scene length, camera moves, what gets animated, what the voice says — all of it follows from what the scene's one idea is.
What "one idea" actually means
An idea, in this sense, is a claim — a sentence the viewer should believe after the scene that they didn't believe before it. "The join waits for all inputs." "Every run leaves a record." "Change the reference and everything downstream updates." Claims, with a truth value.
What an idea is not: a topic. "The dashboard" is not an idea. "Parallel execution" is not an idea. Topics can absorb unlimited screen time because they have no finish line; a claim is done the moment the viewer believes it, which is what makes it schedulable into 8–12 seconds of screen time.
The discipline runs at two levels. The whole video argues one sentence — one thesis everything on screen exists to make feel obvious. Each scene then owns one link of that argument. So the plan for a good explainer is a hierarchy of sentences: one for the video, one per scene, written down before any prose and any pictures. A scene sentence that doesn't push the video sentence toward "obvious" marks a scene to cut, no matter how good it would look.
Why the rule holds
Attention is a budget, and a scene is one withdrawal.
Viewers don't parse scenes the way readers parse paragraphs. They infer meaning from what changes, and they can track one focal change at a time. In our graded builds, when three things animated at full strength at once, the viewer picked one at random — usually the wrong one. The fix that survived review: one focal element per moment, everything else dimmed to about a third of full strength.
A two-idea scene breaks this at the structural level. It has two payoffs, so neither gets staged at full scale; two claims, so the narration rushes; two changes, so the sync between voice and picture — the thing that actually carries meaning — lands on neither. One of our worst-graded builds hid its climax in a one-word change occupying about 1/40 of the frame while the scene busied itself with everything else. The director's verdict: "don't see anything cool." The payoff had happened; it had just never become visible, because the scene was spending its attention budget in two places.
There's a second reason, quieter but just as real: the one-idea sentence is the earliest failure detector you have. A beat you can't picture is a beat you haven't thought through — and the inability to write its sentence fires before a single dollar is spent.
How to spot a two-idea scene
Four tests, in the order we apply them:
- The "and" test. Write the beat intent — what the viewer must take from the scene. "The viewer sees that branches run in parallel and that the join waits" is two intents wearing one scene. Split it.
- The two-payoff test. Every scene has a moment the whole thing exists for. If you can point at two, the second one is being wasted — a payoff the viewer isn't set up for is just an event. Give it its own setup.
- The shape test. Good scenes have a nameable shape: here is a thing (things assemble), watch it work (a run crosses it), change one part (one element morphs, everything dependent updates), what did it leave behind (a record surface rises). When no single shape fits a beat, the beat is usually two beats. Mapping a beat to a shape is a selection problem; when it starts feeling like an invention problem, that's the smell.
- The narration test. If the voice has to explain something the picture isn't currently doing, the scene is carrying an idea it doesn't show. Either the picture is wrong or the idea belongs to a different scene.
The most common two-idea scene we see is behavior plus anatomy: the machine runs, and mid-run the scene also tries to explain what's inside one of the parts. The fix is a specific cut we use constantly — freeze the run at its interesting moment, hold that exact state across the scene boundary, and open the next scene inside the held moment to look around. The run is one idea; the anatomy is another; the held frame is the seam between them. What you never do is finish the run and then run it again for the close-up — viewers pay full attention to a machine's first run and almost none to its third, so every extra traversal spends attention the video needs elsewhere.
Sequencing beats: the chain
If every scene is one idea, the video is a sequence of ideas — and the sequence has a correct shape. The order that survives review:
Orient from what they know → the macro claim → the micro mechanism → one worked example.
Each beat is a link in one causal chain, and each scene teaches exactly one link. Take a video about a product's audit log:
- You already run things here. (Orient — the frame they walk in with.)
- Every run writes a record. (Macro — the claim.)
- The record has one entry per step. (Micro — the mechanism, just enough of it to make the behavior predictable.)
- Here is one failed run, read backwards to the broken step. (The worked example — one run, not three.)
Four scenes, four sentences, one chain. Note what the shape did to scope: an internals deep-dive has no link to live on, so it never gets in.
Two sequencing rules that fall out:
- The camera moves between ideas, and cuts happen inside one. A camera move tells the viewer "new idea"; that signal only stays honest if the scene boundaries are the idea boundaries. When scenes and ideas drift out of alignment, viewers report the video feels "jarring" without being able to say why.
- Name what each scene refuses to teach. Every idea has neighbors, and the neighbors are the threat. In practice we write, per scene, what NOT to say — and keep a standing list of topics deliberately not taught, each with a destination (another video, the docs). Scope isn't what you ran out of time for; it's a list of named exclusions.
What the rule does not mean
One idea per scene is not one element per scene, and it's not stillness. The best-graded builds keep several surfaces alive at once — a table filling, a status column flipping, a live ring burning — all serving a single focal idea. Density is fine; divided focus is the failure. A frame can be rich as long as you can still answer, at any moment, "what is this scene arguing?"
It also doesn't mean short. A scene earns whatever time its one idea needs to land and settle — usually 8–12 seconds, occasionally more for a worked example. Cutting a scene before its idea lands is the same mistake as stuffing two ideas in: either way, the viewer leaves the scene without the sentence.
The rule ends up governing everything downstream. It decides scene count (storyboards get one contract row per idea), video length (the runtime is the sum of what the ideas need), and narration (the voice gets one intent per scene to serve). It's the closest thing this craft has to a first principle.
FAQ
How do I know if my idea is too big for one scene? Try to name its payoff moment. A real scene-sized idea has one moment the viewer must see. If the idea needs a sequence of moments to believe — first this, then this, then this — it's a chain, and each link gets a scene.
Can two scenes share an idea? Only as a deliberate pair: a run that freezes mid-flight, and a second scene that completes the same run after a close look inside. That's one idea told across a seam, and the held frame makes the continuity explicit. Two scenes that independently half-teach the same idea both fail — decide which scene owns it and cut the claim from the other.
Does this apply to a 30-second video? More, if anything. Thirty seconds is three or four ideas at most. The discipline of writing one sentence per scene is what tells you — before production — whether your script is a 30-second video or a 90-second video wearing a 30-second runtime.
What about the hook — is that an idea? Yes, and it's usually the video's thesis stated visually. The opening scene's one idea is "here is the claim this video will make obvious." See the hooks guide for how the first five seconds carry it.
When you're ready to see scenes instead of read about them, send us your product's URL and judge twenty directions built one idea at a time.