A storyboard gives the production team a picture of each step in an explanation. It records what changes on screen, why that change matters, and which product facts support it. An animator should be able to build a rough sequence from the board without inventing the workflow.
Our production order is concept flow, visuals, narration, then audio. The board establishes the visual sequence before anyone writes final narration. Drawing a rectangle around each paragraph of a script leaves the hardest decision unresolved: what the viewer will actually see.
The material you need before drawing
Gather a short brief, current screenshots, and a recording of the relevant product task. Include the product version or recording date. A screenshot establishes a label and its location; a recording also shows the action that changes it. A product owner should resolve any disagreement between those sources before detailed animation.
The brief needs an audience and a question. For the fictional support product in this tutorial, the viewer is a support lead who understands tickets but has never configured routing. The question is, “How does a returns request reach the right team with the order details available?” Reporting and billing fall outside this film.
Create a small sample-data record that every scene uses:
Product: ParcelDesk, an invented teaching example
Ticket: PD-1042
Subject: Blue jacket arrived in the wrong size
Order: ORD-731
Item: Blue jacket, size M
Category: Returns
Initial team: Unassigned
Destination team: Returns
Initial status: Open
Final status: Open
The unchanged status matters. Assigning a ticket does not resolve the customer's request. For a real product, use sanitized data and verify the fields and behavior in a demo account.
Step 1: Define the result the viewer should understand
Write the intended understanding as a complete sentence: “A category rule assigns the request to Returns, and the agent can open the matching order from the ticket.” The final picture must provide evidence for both parts.
This choice determines the film's endpoint. A team field that reads Returns proves assignment. An open order panel with ORD-731 proves that the relevant order is available. Neither proves that an agent has approved an exchange or sent a replacement, so those claims do not belong in the narration.
Record the initial condition beside that result. The ticket starts unassigned, with its order reference visible. This gives the viewer a comparison and prevents the board from opening on a result whose cause remains unexplained.
Step 2: List the changes in their actual order
Write the product path before choosing camera moves. In this example, the product matches a category rule, updates the team, and lets an agent open the linked order. The order lookup requires a click. It does not happen automatically.
| Beat | Starting state | Visible action | Ending evidence |
|---|---|---|---|
| Request | PD-1042 appears in the unassigned queue. | A user opens the ticket. | Subject, category, and order reference remain readable. |
| Rule | PD-1042 remains open. | A labeled explanatory view shows Category equals Returns and destination Returns. | The ticket's category matches the rule condition. |
| Assignment | The team field reads Unassigned. | The routing rule changes the team to Returns. | PD-1042 shows Returns and still shows Open. |
| Order | The assigned ticket shows ORD-731. | An agent opens the order link. | The order panel shows ORD-731 and the blue jacket. |
| Handoff | The ticket and order remain visible. | The frame settles on both records. | The agent has the context needed to decide the next action. |
The explanatory rule view needs a label if the product does not display it beside the ticket. A diagram can explain the relationship without pretending that the customer will find that combined screen in the app.
Step 3: Draw the beginning and end of each change
Create two rough frames for each row. Rectangles and typed labels are enough while you decide composition. The opening frame should contain the information the viewer needs before the action; the closing frame should expose its result.
For the assignment beat, draw the ticket header with PD-1042, the category, and the team field. In the second frame, change only the team from Unassigned to Returns. Keep the status Open. This isolates the effect of the rule and makes accidental changes easy to catch.
Record the animation between the frames in plain language: “The matching condition highlights; the team field updates; both remain visible.” Avoid descriptions such as “a dynamic routing moment,” which leave the action undefined.
Keep the same ticket position when the next scene continues on that surface. When the order panel opens, reserve space for it in the wider composition. Otherwise the animator may shrink the ticket so much that the order reference becomes unreadable.
Step 4: Specify framing and reading requirements
Identify the exact evidence each frame must preserve. For the rule beat, the viewer needs to compare Returns in the ticket's Category field with Returns in the rule condition. For the order beat, they need to compare ORD-731 across both surfaces.
Test the rough frames at the intended player size. If the film will appear in a narrow mobile page, view the frames there before committing to a side-by-side layout. A close view of the ticket followed by the linked order may work better than two tiny panels.
Record what can leave the frame. Irrelevant navigation can disappear in a crop, but the crop should retain enough context to identify the surface. A magnified team field needs a recognizable connection to PD-1042.
Reading time belongs in the board as a requirement, even when the duration remains provisional. “Hold until a viewer can compare both order references” gives the timing pass a purpose. A fixed two-second hold may be too short for unfamiliar information or unnecessarily long for a familiar label.
Step 5: Add narration intent to the visual board
Once the frames explain the path, describe what the voice needs to add. The assignment beat already shows which team receives the ticket. Narration can explain the condition: “Because the category is Returns, the rule assigns this request to the Returns team.”
Mark the phrase “assigns this request” beside the team change. For the order beat, “The agent opens the linked order before deciding how to respond” should accompany the click and the order panel. The sentence preserves the human decision that still follows.
Write final narration after the visual draft works. Record the audio afterward, then check each marked phrase against the corresponding event. Measuring a clip's duration prevents speech from extending past the scene; it does not establish where a particular word occurs within that clip.
Step 6: Assemble the board for production
The completed artifact should contain the brief, sample-data record, scene table, frame pairs, and unresolved questions. A single scene entry can use this format:
Beat ID: assignment
Viewer question: Which team receives this request?
Entry: PD-1042, Category Returns, Team Unassigned, Status Open.
Cause: The active category rule matches Returns.
Action: Team changes from Unassigned to Returns.
Exit: The same ticket shows Team Returns and Status Open.
Framing: Ticket ID, category, team, and status remain readable.
Narration intent: Explain why this rule matches the request.
Phrase cue: "assigns this request" accompanies the team change.
Product evidence: Attach the verified recording and rule configuration.
Next beat: The agent opens ORD-731 from this ticket.
Use the storyboard template for a reusable document. Give the board a version and date so reviewers can distinguish a proposed change from the current production plan.
Problems to resolve before animation
If a scene contains no visible change, determine whether it provides needed reading time. The handoff frame in this example earns a hold because viewers must compare the ticket and order. A second hold on the same information may add nothing.
If the board requires a control that the product lacks, change the depicted action or use a labeled conceptual illustration. An attractive invented button would teach the wrong workflow.
If a scene explains several unrelated settings, split it where the viewer's question changes. One idea per scene means one relationship the viewer can understand; it does not impose one click per scene.
If the narrator has to explain how the example jumped between states, add the missing cause to the pictures. Faster narration will not repair an absent interaction.
A practice board with pass criteria
Create a board for assigning an incoming request to a team in a product you know. Use one request throughout and include the real prerequisite for assignment. Produce the brief, a sample-data record, four to six scene rows, and opening and closing frames for each row.
Ask a colleague to inspect the pictures without hearing your narration. The board passes when they can identify the request, explain what caused its assignment, name the final team, and distinguish assignment from resolution. They should also locate the evidence for those answers without your pointing at the frame.
Record any mistaken answer against the relevant scene and revise that scene. When the silent board passes, build a rough motion draft and use the video review process to check the timing in playback.