Our animated-explainer process develops the concept flow, then the visuals, narration, and audio. The visual sequence demonstrates the viewer's task before the narrator explains it. After recording, the editor adjusts local timing against the actual read and reviews the complete cut.
This order exposes missing actions and unsupported product claims while the team can still revise rough pictures. A fluent script alone may conceal those gaps.
The worked example uses Petal, a fictional invoicing product. In this demonstration, Petal tracks an invoice from sent to paid and shows overdue invoices in a separate list. Use verified behavior from your own product when applying the method.
Define the viewer's question
Write what the viewer should understand or be able to do after watching. For Petal, the question is: “How can I tell which invoices still need attention?” This establishes a practical task and a way to judge the explanation.
Map the shortest useful chain of ideas: a user sends an invoice, a payment updates its status, and the overdue list retains items that need follow-up. A feature belongs in the film when it helps explain that chain. Other features can become separate lessons.
Avoid turning the outcome into an unsupported promise. “Petal handles everything for you” claims more than this sequence demonstrates. The reviewer can verify “The overdue list shows which invoices still need attention” against the actual screen.
Make a storyboard with visible evidence
For each scene, record the initial state, action, result, and meaning. Give it a stable name such as payment-updates-status, along with the important product facts and its relationship to the next scene.
| Scene | Visible change | Viewer learns |
|---|---|---|
| Send invoice | Draft becomes sent. | The invoice has entered the tracked workflow. |
| Receive payment | The same invoice becomes paid. | A payment changes its status. |
| Find overdue work | An unpaid overdue invoice appears in the list. | The list identifies a follow-up task. |
The storyboard template has fields for these decisions. Estimate duration from the action and reading load. There is no required number of scenes or universal number of seconds per scene.
A scene you cannot describe visually needs more design work. Sketch alternatives, use a simple diagram, or reconsider whether a written explanation would serve it better.
Verify the product before polishing the picture
Create the intended example in a safe demo or test environment. Save references for the screens, labels, state changes, and output. Use fictional or sanitized data where appropriate; it must still follow the product's rules.
Separate confirmed behavior from assumptions. If the film needs an automatic payment update, verify that behavior before animating it. A reconstructed interface can be useful, but it should preserve the relevant controls and relationships. The product truth prompt helps identify gaps in the evidence.
Review stills, then motion
Build and inspect the major framings before adding detailed motion. Look for unreadable labels, cropped content, unsupported values, and a focal point that disappears at the intended viewing size. Stills expose these problems while the cost of changing the composition is relatively small.
Then animate the approved direction and watch it at normal speed. A still cannot establish whether the viewer can follow a transition or connect an action to its result. Keep useful reading holds, and use movement to show a change or direct attention rather than to fill every quiet moment.
Record changes to the storyboard when the explanation evolves. The document should describe the current cut, with earlier versions retained for comparison.
Write and record narration to the scene
The picture can show an invoice changing to paid. Narration can explain what triggered that update: “When the payment arrives, Petal marks this invoice paid.” Write complete, speakable sentences tied to visible events. Keep on-screen labels and captions where they help the viewer; repeating a necessary term is not automatically a defect.
Measure the actual audio rather than assuming a fixed speaking rate. A scene's duration should accommodate both its visual minimum and the retained audio, including any lead-in and ending pause. VO sync explains that calculation.
Then check phrase synchronization. The word “paid” should refer to a status the viewer can find at that moment. A duration calculation prevents clipping, but it cannot make that editorial decision.
Approve the complete experience
Watch the full video with sound, at normal speed and its intended display size. Check product accuracy, continuity, timing, captions, and the final call to action. Use timestamped notes tied to a specific version, then review the revised cut.
A structural failure may require restaging a scene. A local problem may need only a label correction, a new take, or a timing adjustment. Choose the size of the repair from the cause of the problem. Preserve approved assets and keep revision time in the production schedule.
Use the review scorecard for your own project, watch examples, or request a preview of a production direction.