Motion design craft / Storyboard

30-second render issue diagnosis storyboard

Use this structure to explain an actual production defect and its verified correction. The storyboard deliberately requires captured evidence instead of a polished fictional success story.

By AnimroUpdated 2 min readAI-assisted · independently agent-reviewed

Who this is for: Motion producers planning timed educational and brand studies.

What to prepare

  • Original encoded file and defect frame/time
  • Source revision and suspected cause
  • Revised encoded file and actual retest observations

Copyable creative brief

An authored planning example. Replace illustrative details with your approved product facts and assets.

Assemble a review reel only from real captured artifacts. Keep observed symptom, suspected cause, implemented change and retest result distinct. The bracketed copy slots are required evidence fields; do not publish them as completed findings until the corresponding artifacts exist.

Scene-by-scene storyboard

30-second planning sequence · illustrative copy and visual direction

  1. 01

    0–6s

    Show the observed defect

    Display the original decoded frame and a short surrounding clip with exact file/time labels.

    On screen:[Observed defect] • [file and frame/time]

  2. 02

    6–13s

    Isolate the suspected cause

    Show a relevant source or layout overlay without presenting the hypothesis as proven.

    On screen:Hypothesis: [specific layout, mask or timing cause]

  3. 03

    13–22s

    Compare the revised artifact

    Place matched original and revised states side by side, each with its version label.

    On screen:Change: [implemented correction] • comparison evidence

  4. 04

    22–30s

    Record the retest

    Show adjacent-frame inspection and actual playback findings with unresolved items visible.

    On screen:Retest: [observed result] • [remaining concerns or verified checks]

Make it your own

DEFECT_EVIDENCE
Identify the real file, frame or timestamp and observed symptom.
CAUSE_HYPOTHESIS
State a suspected cause separately from what was observed.
CORRECTION_EVIDENCE
Supply the actual changed artifact and matched comparison frames.
RETEST_STATUS
Record passed, failed or unresolved checks with evidence.

Prepare evidence before editing the reel

Capture the frame before, affected frame and frame after from the original encode. Preserve its identifier and source revision. For an illustrative example of the format, the symptom might be a clipped accent during a heading entrance, but that example is not a finding until it appears in a real supplied artifact.

Match the comparison carefully

If the correction changes timing, compare equivalent visual states as well as the original timestamp. Show the actual revised encode, not only a clean design preview. For a longer investigation, use 60 seconds to explain multiple hypotheses; keep this 30-second version focused on one defect.

Avoid a premature success conclusion

A larger mask in source code is evidence of a change, not proof that clipping is gone. Replay the encoded interval and inspect adjacent frames. Record shared-component regression checks when relevant. If the retest still fails, say so in the reel and preserve the next investigation step.

Review checklist

  • The defect is backed by a real captured artifact.
  • Hypothesis and observation are labeled separately.
  • Comparison uses actual original and revised encodes.
  • The conclusion reports only performed retest observations.
Explore motion design craft ↗

Use case / Motion design craft

Motion production review reels

Assemble a review reel from real encoded evidence with exact frame references, observed defects, matched corrections and sign-off tied to inspected files.

Read resource