How Storytelling Actually Works in Motion Design (And Why Most Videos Get It Wrong)

The Word Everyone Uses and Almost Nobody Understands

Every motion design studio says they do storytelling. Most of them don't.

What they do is sequencing, moving from one piece of information to the next in a logical order. That's not storytelling. Storytelling requires tension. It requires a reason for the viewer to need to know what happens next. Without that, you have a well-organised presentation, not a story.

I've been in briefs where the client has said "we want something that tells our story" and what they meant was "we want to explain our feature set in a compelling way." Those aren't the same thing. Features don't have stories. Problems do. Users do. The gap between where someone is and where they need to be, that's where the story lives.

The motion design that works, the stuff people actually watch, share, and remember, creates that gap in the first ten seconds and resolves it in the last ten. Everything in between builds the bridge. That's the structure. The art is in making the bridge feel inevitable rather than constructed.

Storytelling, the real kind, has specific mechanics. It creates tension. It follows a character. It makes deliberate choices about what to include and what to leave out. And in motion design, it's the difference between a video that people watch once and forget and one that changes how they think about your product.

Stories Have Tension

The most important element of any story is tension: the gap between how things are and how they could be. Without tension, there's no reason to keep watching.

In a SaaS explainer video, tension looks like this: "Your team spends four hours every week manually reconciling data across three platforms. By Thursday, someone's working from an outdated version. By Friday, the report is wrong."

That's not a product description. That's a scenario your viewer lives in. They feel the frustration. They recognise the cost. Now they're invested in the resolution.

Most explainer videos skip this entirely. They open with "Introducing [product name], the all-in-one platform for..." and the viewer's brain checks out immediately. There's no tension, no reason to care, no emotional investment in what comes next.

Stories Follow a Character

Every story needs a character, someone the viewer can project themselves onto. In motion design, this doesn't mean you need elaborate character animation. It means the narrative needs a perspective.

The character is usually the customer:

• "Meet Sarah, a marketing manager juggling three tools and zero visibility..."
• "You're an ops lead responsible for data accuracy across four departments..."
• "Your team has fifteen minutes before the board meeting and the numbers don't match..."

The character gives the viewer a way in. Instead of processing abstract information about your product, they're watching someone like them navigate a problem they recognise. That's the difference between information and story.

Stories Require Choices About What to Leave Out

This is the hardest part. Every client wants to include everything: every feature, every use case, every differentiator. The impulse is understandable. They've built something complex and they're proud of all of it.

But stories work through compression, not completeness. You choose the one scenario that best represents your product's value. You choose the three features that matter most to your primary audience. You cut everything else.

I had a client whose product had twelve major features. They wanted all twelve in a 90-second video. That's seven seconds per feature, barely enough time to name them, let alone explain them. We chose three features, showed them in depth, and the video converted better than anything they'd produced before.

The principle: A story that goes deep on three things is more compelling than a story that skims twelve.

The Process That Produces Good Storytelling

Good storytelling doesn't happen in the animation phase. It happens in the first two weeks of a project, during the work that most people skip:

1. Problem immersion. Before I write a word, I need to understand the problem the product solves, not from the founder's perspective, but from the customer's. What does their day look like? Where does it break down? What's the cost of doing nothing?

2. One thing identification. What's the single most important thing the viewer needs to understand? Not the most impressive feature. The thing that makes them think "I need this."

3. Story arc development. Structure the narrative: world as it is (tension), introduction of the solution (turn), world as it could be (resolution). This arc works at any length, from 30 seconds to three minutes.

4. Script writing. Words first, visuals second. The script is the backbone. If the story doesn't work as a script read aloud in a room, it won't work as a video.

5. Visual storytelling. Now, and only now, does design enter the picture. The motion graphics serve the story. Every visual choice should amplify the narrative, not decorate it.

Why Most Videos Get It Wrong

Most videos get storytelling wrong because they start at step five. They open After Effects before they've figured out the story. They choose a visual style before they've written the script. They animate features before they've identified the tension.

The result is a video that looks professional but feels empty. All craft, no substance. The viewer watches it, acknowledges that it's well-made, and promptly forgets everything about it.

The videos that work, the ones that drive conversions, get shared internally, and change how people think about a product. are the ones where the story came first.

If you want a video that tells a real story about your product or mission, take a look at my process or get in touch.

Frequently Asked Questions

How do you find the right story for a product you've never used? I interview the team (founders, product managers, customer success leads) and I read customer reviews and support tickets. The best stories come from real customer experiences, not marketing copy. The patterns in how customers describe their problem before finding the product are usually where the story lives.

Can storytelling work for highly technical products? Absolutely. In fact, technical products need storytelling more than simple ones. The more complex the product, the more important it is to anchor the explanation in a human scenario. Nobody connects with a technical architecture diagram. Everyone connects with "your engineering team shipped a bug to production and spent three hours rolling it back."

What's the difference between storytelling and a product tour? A product tour shows features in sequence. A story creates tension, follows a character through that tension, and resolves it. A product tour says "here's what our product does." A story says "here's what your life looks like before and after." The product tour informs. The story persuades.

---

Dan Neale is a motion designer and creative director based in Byron Bay, Australia. He specialises in motion design for SaaS companies, tech founders, agencies, and nonprofits. 15 years. 500+ projects. motionstory.com.au