How to Explain a Process with an Animation Explainer

Mon, 26 Oct 2026 09:17:49 +0000

An animation explainer is a short moving picture that makes one idea clear. When the idea is a process, a before and after can carry the whole point: show the starting state, then the ending state, and let the viewer feel the change. Use this shape when the start and end are easy to picture and the middle is short. If the middle is long or branching, show the steps instead.

What matters when you choose an animation explainer?

The starting state and the ending state are both easy to picture.
The change solves a problem the viewer already feels.
The middle fits in a few visible moves.
The viewer can hold both states in mind on one pass.
The ending state removes a real cost, not just tidies it.

If two or three of these are weak, the format is probably wrong. That is not a failure of the idea; it is a sign to choose a different shape.

The decision is not about style; it is about what the viewer needs first. If the change is the news, lead with the change. If the steps are the news, lead with the steps and let the ending state arrive last.

How do you judge each criterion?

Start with the two pictures, not the steps. If you cannot sketch the before and after in a few seconds, the viewer will not hold them either. A messy shared drive and a tidy folder system works because both are visible, while "better data hygiene" is not. If the pictures need the words to make sense, the pictures are not doing the work.

The change has to solve a problem the viewer already feels. If the after state only saves time for the team that runs the process, the before and after will feel like an internal memo dressed up as a story. Tie the ending state to something the viewer loses today: lost files, repeated questions, a task that takes too long, or a handoff that fails. The before picture should make that loss visible in one glance.

Count the moves between the two pictures, not the minutes. If the middle needs more than a handful of actions, the before and after will skip the part that actually matters. In the shared drive example, rename, sort, and remove duplicates is short; adding permissions, naming rules, and training is not. When the middle grows, switch to a step-by-step explainer video and keep the before and after as the first and last frames.

The viewer should see both states without scrolling back or replaying. That means one screen, or one clear transition, not a long tour of details that only make sense in order. If you need a second viewing to compare, the change is too large for this format. A single animated video can still show detail, but only after the main change is locked in and the viewer knows what to look for.

The after state must look like relief, not like a different kind of work. If the new process only moves the pain somewhere else, the before and after will read as a trade, not a win. Name the cost that disappears, and make sure it disappears in the picture, not only in the voiceover. Show the moment the old cost stops, and let the new state stay on screen long enough to feel earned.

The trade-off is simple: clarity now versus completeness later. A before and after buys attention and care; it does not buy a full procedure. If you need the full procedure, plan a second piece.

When you judge the criteria, judge them in this order: pictures first, then pain, then middle, then memory, then relief. If the first fails, stop; the rest do not matter. This order saves time and protects the idea.

Which red flags show it is the wrong choice?

Some processes fight this format. The signs usually show up while you are still planning, before anyone draws a frame or writes a line. If two or more of these are true, plan a step-by-step explainer video instead and keep the before and after for a single closing shot.

The before and after look almost the same on screen.
The process has branches, exceptions, or approvals that carry the real point.
The viewer needs numbers, labels, or a legend to see the change.
The after state needs a long explanation of why it is better.
The middle contains a decision that changes the outcome.
The same process looks different for different people.

These are not small flaws; they are format mismatches. A before and after in an animation explainer works when the change is the story and the steps are short enough to trust. When the steps or the rules are the story, show them in order and let the ending state arrive last. The viewer will still feel the improvement, but they will also understand how to reach it.

Do not force a process into this shape because the pictures look good. The format is a promise that the change is visible and short. Break that promise and the viewer stops trusting the next animation explainer you make.

If only one red flag is true, you may still use the format, but name the limit in the script. Honesty about the limit keeps the piece useful. Hiding it turns a small mismatch into a broken promise.

What should you ask before you commit?

These questions force the change into words before it becomes pictures. If an answer stays vague, the animation will stay vague too.

What exactly changes between the first frame and the last frame?
Can a newcomer name that change in one sentence?
Which step in the middle carries the risk, cost, or delay?
What would make the after state feel unearned?
How will you show the change with pictures before you add words?
Who in the audience will not feel the problem in the before state?

If the last question has no clear answer, the before picture is probably too generic. Fix the before state first; the after state depends on it.

Answer them in plain words before you sketch. If an answer needs a diagram to make sense, the picture is not ready yet. The questions are a filter, not a script.

Frequently asked questions

Can a before and after replace the whole process?

It can replace the overview, not the training. Use it to make someone care about the change, then use a step-by-step format for the actions. If you try to teach every step inside the before and after, the middle will blur and the ending will feel unearned. The viewer remembers the feeling of the change, not the procedure.

A good handoff is to end with one clear next step and a place to find the full steps. That keeps the animation explainer focused on the change while still respecting the viewer who wants to act. The feeling comes first; the procedure follows.

What if the process has more than one good outcome?

Pick the outcome that removes the pain the viewer already knows. Showing two or three endings turns the piece into a comparison chart, which is a different job with different pacing. If the outcomes depend on context, say so in one line and keep the main change simple. You can always end with a short note that other paths exist.

When context matters, name the condition in the voiceover and keep the picture on the main case. The viewer can hold one exception in mind if it is stated plainly. Two exceptions usually need a different format.

How long should the middle part be?

Short enough that the viewer does not lose the thread. If you need to pause, rewind, or add a label to keep up, the middle is too long for this shape. Cut the middle to the moves that change the picture, and move the rest into a later section or a separate explainer video script. The middle is not the place to be complete; it is the place to be believable.

A believable middle has fewer moves than a complete one. When in doubt, cut the middle by half and see if the change still makes sense. Most middles survive the cut better than their authors expect.

Try sketching the before and after on paper before you write a script. If both pictures are clear and the middle fits in a few moves, you have a strong shape for an animation explainer. If not, switch to steps and save the before and after for the final frame.

Coder Legion - Recent posts tagged storytelling