A storyboard exposes tacit assumptions in the flow
Aliases: storyboard as assumption probe · gaps between frames · tacit procedural premises
What it is
Prose can say “then the user uploads ID.” Drawn as frames, someone must decide where the ID comes from, which hand holds the phone, whether the light is enough, and what the next frame is if this one fails. A storyboard uses a sequence of pictures to force unwritten assumptions onto the seams between frames. Its analytic value is not likeness. It is the blank that makes visible which bodily acts, waits, and confirmations the proposal skipped.
Why it happens
Language permits ellipsis. Pictures will not let the same ellipsis pass a review at the same speed—a missing frame makes the audience ask “are we here yet?” Frames also force a viewpoint: whose eyes, how far, whether screen and surroundings can be seen at once. Picking a viewpoint drops the others, so a god-narration like “the system has already sent it” is hard to smuggle in. Teams rarely argue about drawing skill; they argue whether the middle frame must exist. If it must, the proposal has an undesigned step. If they refuse to draw it, the assumption is now public.
Studying it
Align a verbal script of the same flow with a storyboard and code actions, waits, and confirmations that appear only in frames, plus internal system states the prose kept and the pictures cannot show. Ask people who did not design it to write “what happens between these two frames” from the storyboard alone; what they supply counts as an exposed assumption. Outcomes: steps filled in between frames, and bodily acts judged unskippable.
Where it stops holding
Concept films and ad boards chase mood and skip paperwork on purpose; they are not analytic storyboards. Pure back-office batch work has almost no drawable body; forcing frames invents a frontstage. Matchstick fidelity is enough to expose steps; over-rendering the UI drags the talk onto visuals. A storyboard exposes an assumption; it does not verify it. Truth still goes back to observation or a test.
Applying it
- Draw each consequential flow until “I cannot say what sits between these two frames”; list those positions as assumptions.
- Do not replace a frame with a caption (“the system has already validated”); either draw the wait or admit the person cannot see it.
- In review, ask first how this frame connects to the next, not whether it looks good.
- Send filled-in middle steps back to design: build them in, or exclude them explicitly and accept the matching failure.