Process

How we storyboard a technical sequence

Most technical animations fail in the storyboard, not the render. By the time a sequence is in 3D, the expensive decisions are already made — so that's where we spend the first, and most, of our time.

The Seagull CompanyEditorial
June 26, 2026Published
6 min read
A frame from a molecular mechanism sequence
A single frame only works if the frames around it earned it. RNA-mechanism sequence, Oligon.

Most technical animations fail in the storyboard, not the render. By the time a sequence is in 3D, the expensive decisions — what to show, in what order, at what depth — are already made. So that's where we spend the first and most of the time, long before anything moves.

Start with the one hard idea

We begin every board with the single hardest thing the audience has to understand. Not the product, not the brand — the one mechanism that, once it clicks, makes everything else obvious. For a drug it might be how a molecule engages its target. For a tool, the moment a force is redirected. Everything in the board earns its place against that one idea.

If a beautiful shot doesn't help the viewer understand the hard idea, it doesn't go in. That sounds obvious. In practice it's the hardest discipline on the team, because the beautiful shots are tempting and the science is generous with detail.

Clarity is usually a subtraction, not an addition.

Work backwards from the click

Once we know the moment that matters, we work backwards. What does the viewer need to see just before it for the moment to land? What context can we establish in three seconds that saves thirty seconds of confusion later? And — the question we ask most — what can we cut entirely?

Most first drafts are too full. An expert hands us everything that's true, and all of it is true, and almost none of it belongs in the same ninety seconds. The board is where we negotiate that down to a sequence a non-expert can follow without losing what an expert would defend.

What a board actually contains

  • The hard idea, stated in one sentence at the top of the page.
  • Rough frames — ugly on purpose, so no one falls in love with a look before the logic is right.
  • The transitions, because the cut between two ideas is usually where understanding breaks.
  • A note on depth: how far inside the system we go, and where we deliberately stop.
A cutaway showing internal flow
The depth decision: a cutaway shows enough to be true, and stops before it becomes noise.
Have a sequence that isn't landing?

Bring us the board, the script, or just the problem. We'll tell you where the clarity is breaking.

Discuss a project

Review with the expert, not around them

We put the rough board in front of the subject-matter expert early, while it's still cheap to change. The goal isn't approval — it's to find the place where we've made something clear but wrong, which is worse than confusing. An SME catches that in a board in five minutes. They catch it in a finished render after a week of work.

Respecting the expert is a design constraint, not a courtesy. The science stays intact. What changes is how much of it the viewer has to carry at once.


By the time we light the first real shot, the argument is already won or lost on paper. The render makes it beautiful. The board makes it clear.

The Seagull CompanyScientific & technical animation. Clarity over complexity.
Start a project