One idea per scene means the viewer can say what they learned from that scene. It does not mean one object, one sentence or one animation. Several actions can belong together when they explain a single relationship.
In a scheduling product, choosing a time, seeing a conflict and selecting an available slot can form one idea: the scheduler helps you avoid a clash. Adding team permissions, reminder settings and billing to the same scene introduces separate questions. The editor should move those topics to other scenes or remove them from this film.
Name the change in understanding
Write a plain sentence for each scene: “The viewer learns that the scheduler blocks confirmation of a conflicting booking.” This is more useful than “Show calendar animation” because it identifies the meaning the animation needs to carry.
Next, write the evidence. A second booking overlaps an occupied slot, the conflict becomes visible, and confirmation remains unavailable. When the booking moves to an open slot, the conflict clears. Use the actual product behavior; some schedulers warn about a conflict while still allowing an override.
The distinction matters. A calendar turning red could mean an error, a selection or a busy period. The scene must establish which meaning applies instead of relying on color alone.
Find where a scene changes the question
An overloaded scheduling scene might contain this sequence:
Open the team calendar.
Choose a time and show an overlap.
Move the booking to an available slot.
Add a guest and choose their permissions.
Configure a reminder.
Confirm the booking.
The first three actions answer whether the proposed time works. Guest permissions answer who can do what. The reminder answers when the scheduler will notify the guest. Confirmation may close the scheduling task, but it does not make those intervening ideas identical.
Split at the change of question. You might keep availability as the main scene, cut permissions entirely, and give the reminder one later beat if it matters to the film's purpose. More scenes are not automatically better. Removing an unnecessary question often improves the film more than finding another transition.
Give each beat a clear before and after
A useful scene has an observable difference between its opening and closing state. In the availability scene, the booking begins in conflict and ends in an available slot. The changed slot and cleared conflict identify the evidence the scene needs to keep readable.
Plan the sequence around that change:
| Part | What the viewer sees | Why it is there |
|---|---|---|
| Context | The existing booking and the proposed time | Establishes the overlap |
| Action | The proposed booking moves | Shows how the user changes it |
| Result | The conflict clears and the new time remains | Confirms the outcome |
Hold the result long enough to inspect it. A still frame can be useful when it gives the viewer time to read. Continuous decorative movement is not a substitute for a meaningful next event.
Preserve continuity when you split
Splitting a scene should not force the viewer to relearn the interface. Keep the same booking, date and participant names in the next shot. If the next beat uses the confirmation panel, show how that panel relates to the calendar the viewer just saw.
Shared positions and repeated visual identifiers make continuity easier to maintain. Reframing can bring a small control into view without pretending that the whole workspace has changed. A purposeful cut is often sufficient; each new idea does not need an elaborate transition.
Check the boundary frames. A selected booking should not become unselected accidentally, and a panel should not move without an apparent reason. Reviewers can miss these inconsistencies when they inspect scenes separately.
Fit narration to the visual beat
With the scene defined, write a line that explains the useful relationship: “The conflict clears when the user moves the booking to an open slot.” The visual action and the sentence now share a clear event.
A longer explanation may still fit if it serves the same question. If the line starts introducing permissions or reminders, reconsider its scope. Sentence count is a clue, not a rule. Judge whether the viewer can follow the picture and the voice together.
Use this prompt when reviewing a draft board:
For each scene, state the one question it answers.
List the visible actions and the evidence of the result.
Identify any action that answers a different question.
Recommend keeping, moving, or removing it, with a reason.
Preserve the example and visual continuity across scene boundaries.
Check the scene in motion
- Can a viewer describe what changed without your extra explanation?
- Does each action contribute to the same idea?
- Is the crucial result visible when the narration discusses it?
- Does the final state remain long enough to understand?
- Do colors, highlights and movement keep the same meaning throughout?
- Does the next scene begin from a believable continuation?
Test at the intended viewing size. A tidy storyboard can still produce an unreadable interaction in a small player. Use the explainer review process to separate problems of meaning from problems of timing and finish.
A scene-editing exercise
Create two versions of the scheduling board. The first contains the overloaded sequence above; the second retains only the actions needed to explain availability. Keep the same booking and date in both. Write the question, starting state, and result beside each scene in the revised board.
Give the revised pictures to someone who has not read your explanation. The board passes when they can identify the conflicting time, explain why confirmation stays unavailable, and identify the available time that clears the conflict. They should not need information about permissions or reminders to answer those questions. Keep the removed actions in a separate list with a reason for each decision so later revisions do not casually restore the overloaded scene.