Motion mistakes designers make
The most common ways motion goes wrong in product UI, and how to fix each one.

Zander Whitehurst
7 min read
Motion is one of the quickest ways to make an interface feel polished. It is also one of the quickest ways to make it feel cheap, slow or even unusable. The difference rarely comes down to talent. It usually comes down to a handful of habits that are easy to slip into and just as easy to fix once you can spot them.
Most of the mistakes below are ones I see every week when reviewing student work. Plenty of them are ones I made myself for years. None of them are fatal, and every one has a simple fix.
Animating everything
The most common mistake is treating motion as decoration. Every card fades in, every icon spins, every heading slides up from below. Each animation might look fine on its own, but together they create noise. Nothing stands out because everything moves.
Motion is a signal. It tells people what changed, where to look and what is connected to what. When everything moves, the signal disappears.
The fix: before adding an animation, ask what it communicates. If the answer is "it looks nice", leave it out. Reserve motion for state changes, spatial relationships and feedback. A good test is to remove all motion from a screen and add it back one piece at a time, only where something feels missing.
Making it too slow
Designers often set durations by watching an animation on its own, over and over, in a prototype. In that context 600 milliseconds feels smooth and considered. In a real product, used fifty times a day, it feels like wading through treacle.
People notice slowness far more than they notice speed. An interface that responds instantly feels capable. One that makes you wait for a flourish feels like it is showing off at your expense.
The fix: start shorter than feels comfortable and only lengthen if something feels abrupt. Use the interaction twenty times in a row before you decide. If you find yourself waiting for it, it is too slow.
Using linear easing
Linear easing moves an element at a constant speed from start to finish. Nothing in the physical world moves like that, so it reads as mechanical and slightly wrong, even when people cannot say why.
The fix: use an ease out curve for elements entering or responding to input, so they start quickly and settle gently. Keep linear for things that genuinely should be constant, like a progress bar filling or a loading spinner rotating.
Inconsistent timings
One modal opens in 200 milliseconds, another in 350. One dropdown eases out, another eases in and out. Individually none of these are wrong, but together they make a product feel like it was assembled by different people. Usually it was.
The fix: agree a small set of named durations and easing curves and use only those. Three or four durations and two or three curves cover almost everything. Once they live as tokens in your design system and your codebase, consistency becomes the default rather than something you police.
Animating properties that cause jank
Some CSS properties are cheap to animate and some are expensive. Animating width, height, top, left or margin forces the browser to recalculate layout on every frame. On a fast laptop you might not notice. On a mid range phone the animation stutters.
Designers rarely think about this because design tools do not care which property moves. The browser cares a great deal.
The fix: animate transform and opacity wherever you can. They can be handled by the GPU and skip layout entirely. Instead of animating height to reveal a panel, scale or translate it. Instead of moving an element with left, use translate.
/* Janky: triggers layout on every frame */
.panel { transition: height 200ms ease-out; }
/* Smooth: compositor only */
.panel { transition: transform 200ms ease-out, opacity 200ms ease-out; }
When you genuinely need layout to animate, libraries like Motion handle it with layout animations that use transforms under the hood.
Ignoring reduced motion
Some people experience dizziness, nausea or headaches from on screen movement. Operating systems let them ask for less of it, and browsers expose that preference through prefers-reduced-motion. Many products ignore it entirely.
The fix: respect the setting in every animation, not just the big ones. Reduced motion does not mean no feedback. Swap large movements for simple fades or instant state changes so the interface still communicates clearly. Treat it as a design requirement from the start rather than a fix after launch.
Motion that blocks the user
A surprising amount of motion gets in the way. A page transition that must finish before you can click. A menu that ignores taps while it slides open. An onboarding sequence that plays in full whether you want it or not.
When motion blocks input, people feel the product is slow even if every animation is short. They tapped, and nothing happened.
The fix: make animations interruptible. People should be able to click, scroll or close at any point, and the interface should respond immediately, reversing or skipping the animation if needed. Never disable interaction just to let an animation finish.
Bounce everywhere
Spring physics and overshoot can make an interface feel lively. Used everywhere, they make it feel like a toy. A settings menu that wobbles, a modal that bounces in, a table row that springs into place. Playfulness turns into wobble.
Bounce also carries meaning. It suggests something physical and energetic, which suits a celebration or a playful brand moment. It does not suit a destructive confirmation dialog.
The fix: use overshoot sparingly and on purpose. Keep most transitions critically damped so they settle without bouncing. Save bounce for moments of delight or for products where playfulness is genuinely part of the brand.
Not testing on real devices
Motion that looks perfect in a desktop browser can fall apart on a phone. Frame rates drop, touch interactions feel different and a 200 millisecond transition that felt snappy on a big screen feels sluggish in the hand. High refresh rate displays expose stutter that a 60Hz monitor hides.
A few years ago I shipped a page transition I was genuinely proud of. It was smooth, layered and beautifully timed on my laptop. The first time I opened it on an older Android phone, it dropped so many frames it looked like a slideshow. I had tested it a hundred times, just never anywhere that mattered. I rebuilt it with transforms only that afternoon and it was half the complexity and twice as smooth.
The fix: test motion on the devices your users actually have, including at least one older phone. Use browser developer tools to throttle the CPU and watch the performance panel for dropped frames. If it only works on your machine, it does not work.
A quick checklist
Before you ship any motion, run through these questions:
- Does it communicate something? If not, remove it.
- Is it fast enough to repeat? Use it twenty times and see.
- Is the easing intentional? No accidental linear.
- Does it use your tokens? Same durations and curves as everything else.
- Is it animating transform and opacity? Avoid layout properties.
- Does it respect reduced motion? Check with the setting turned on.
- Can people interrupt it? Input should never wait.
- Is the bounce earned? Only where playfulness fits.
- Have you tried it on a real phone? Ideally an older one.
Good motion is mostly restraint
The designers whose motion work I admire most are not the ones who animate the most. They are the ones who know exactly when to stop. Their interfaces feel quick and calm, and the few moments that do move feel deliberate.
If you want structured practice spotting and fixing these mistakes, and building motion that holds up in real products, the AI Motion Design bootcamp covers it hands on. Otherwise, pick one screen in your product this week and run it through the checklist above. You will almost certainly find something to remove, and the screen will be better for it.
Memorisely