A storyboard prompt should supply verified product behavior and a specific viewer question. It also needs a continuing example and enough detail for an animator to build the scenes without inventing controls or transitions.
Use a writing assistant to explore treatments and organize a board. Review the result against evidence before treating it as a production plan. Plausible prose can conceal an invented interface or a missing causal step.
Give the prompt a bounded task
Prepare a short brief, a sanitized sample-data ledger and current product evidence. Describe the intended viewer and the one question the film should answer. State what the film excludes.
For this example, DispatchDesk is a fictional support-routing product. An urgent checkout ticket starts unassigned. A rule matching Category equals Checkout assigns it to Payments. The assignment preserves the ticket's priority. Those authored facts define this exercise; they do not describe a real customer's system.
The useful question is “How does the ticket reach its team?” A storyboard that introduces analytics, automatic replies or guaranteed resolution would exceed the evidence.
Compare treatments before requesting a full scene list
Request alternative structures that explain the same verified behavior. For DispatchDesk, the options might be following one ticket, comparing manual and routed assignment, or changing one condition to show which tickets match.
Judge the options by what they let the viewer understand. Following one ticket makes continuity easy to inspect. A controlled comparison can clarify a rule's boundary. A split-screen comparison needs enough room for both paths to remain legible.
Choose a treatment, then rewrite the selected ideas into one consistent world. Combining attractive scenes from several drafts without reconciling their data and visual language often creates a film that keeps restarting its explanation.
A copyable storyboard prompt
Plan a product explainer using only the supplied facts.
Audience and question: [fill in]
Desired understanding: [fill in]
Product evidence and version: [paste sanitized sources]
Sample-data ledger: [paste stable identities and values]
Selected treatment: [follow one example / comparison / other]
Exclusions: [fill in]
Return a scene table with:
- stable beat id and viewer question;
- entry state, including surface and example data;
- concrete visible action and its cause;
- final proof frame and exit state;
- source supporting the depicted behavior;
- narration intent, without final narration or audio timing;
- open questions that block an accurate depiction.
Keep each beat centered on one understandable change. Preserve example identity
and carry the previous result forward. Mark any reset explicitly. Do not invent
screens, controls, statistics or outcomes. Distinguish a product reconstruction
from a labeled conceptual illustration. Flag missing evidence instead of filling
it with a plausible guess.
The storyboard template provides a longer scene contract and a completed example you can adapt.
Audit the returned board
Read the entry and exit states independently of the descriptive language. They should tell a coherent story.
| Beat | Entry | Change | Exit |
|---|---|---|---|
| Request | DD-1042 is unassigned and urgent. | Frame the relevant ticket fields. | The viewer can identify the unassigned ticket. |
| Rule | The same ticket remains visible. | Reveal Category Checkout and destination Payments. | The viewer can compare the condition and destination with the ticket. |
| Assignment | Ticket and matching rule are visible. | Team changes to Payments. | Priority remains Urgent; the assignment is inspectable. |
Compare each row against the supplied facts. Assignment must not become resolution, the rule editor must remain on its actual surface, and DD-1042 must keep its subject. Record any disagreement against the relevant row before an animator builds it.
Test the visuals before writing the voice
Create stills or a simple visual draft from the selected board. Check the important framings at the intended player size. A scene description that sounds clear may require more space or a different sequence once it becomes a picture.
After reviewing the visuals, use the narration prompt to draft words for those actual beats. Record audio afterward, measure it and review the important phrase-to-event cues. Estimated scene lengths do not establish synchronization.
A storyboard audit exercise
Remove decorative adjectives from one storyboard row and give it to another person. They should still be able to draw its starting state, action, and result. Replace phrases such as “a dynamic transition” with the actual movement and the information it preserves.
The row passes when that person can identify the changed field, name the cause, and describe the final state without inventing an interaction. Keep the corrected row and its evidence reference as the exercise artifact.