Compiled 5 August 2026. All time-sensitive claims are anchored to this date.
HOW TO USE THIS REPORT
Three reading paths
Use the Full report, Newcomer, Practitioner, or Executive toggle above to filter the contents. Out-of-path sections stay on the page — they dim, they are not deleted.
| You are | Read | Why |
|---|---|---|
| A newcomer | Chapters 1–17 | Foundations, diagnosis, and the first hard gate |
| A practitioner | Ch. 4, then Ch. 43–54 | Systems, tokenisation, migration, governance, and supply |
| A decision-maker or buyer | Ch. 4, 5, 10, 17, 52, and Part VI (Ch. 57–64) | The honest value case, measurement baselines, and gates |
Part I — What Motion Actually Is
1. Four lenses on motion, and the one this report commits to
Ask five people in a room what motion design is and you will get five answers that are not compatible. This is not semantic pedantry. The four definitions below imply different budgets, different hires, different deliverables and different measures of success. Choosing the wrong one is the most common upstream error in the discipline, and it is committed in the brief, before any designer touches a keyframe.
| Lens | The claim | ✔ Right about | ✘ Wrong about | Held by |
|---|---|---|---|---|
| 1. Craft output | Motion is the production of moving-image assets: idents, explainers, title sequences, social cutdowns | Honest about where the money goes — most motion spend is production spend | Defines the discipline by its artefacts. Motion becomes a per-asset purchase, so consistency is structurally impossible; every asset is a fresh negotiation | Procurement, most marketing departments, freelance production markets |
| 2. Brand asset | Motion is a distinctive property of the brand, in the class of colour, logo, mascot, sonic signature. Its job is to be recognised and attributed | Connects motion to the only branding literature with genuine empirical weight — the distinctiveness school (Ch. 4, Ch. 11). Makes motion measurable | Flatters motion by assuming any consistent movement becomes an asset. Assets require fame and uniqueness; most brand motion has neither | Brand strategists, effectiveness researchers, insight teams |
| 3. Interface behaviour | Motion is a functional layer of the UI: it explains state changes, maintains spatial continuity, provides feedback, reduces disorientation | The only lens with a real usability evidence base, and the only one under which motion is engineered rather than exported | Indifferent to brand. Optimised purely for function, every product converges on platform default — and the brand disappears at the touchpoint with the most exposure | Product designers, design system teams, front-end engineers, Nielsen Norman Group |
| 4. Brand behaviour | Static identity governs how a brand looks; motion governs how it behaves — pace, manners, temperament, restraint or exuberance | Explains why motion cannot be added at the end. Behaviour is a property, not a finish | Unfalsifiable and unbudgetable on its own. "The brand's body language" is a beautiful sentence that specifies nothing until compiled into parameters (Ch. 9) and tokens (Ch. 44–46) | Brand leadership, founders, creative directors |
The definition this report commits to
Motion design in branding is the specification and governance of how a brand's elements behave over time, across every touchpoint, expressed as a finite set of parameters that can be reproduced by people and machines who never spoke to the original designer.
Three load-bearing words.
Specification — not production. The deliverable of the discipline is a rule, not a film. Films are evidence that the rule works.
Governance — the rule must survive contact with an in-house team on a Friday deadline, three agencies in two hemispheres, and an engineer who has never opened the guidelines. If it does not, you have a showreel, not a system.
Reproducible by machines — this is the 2026 addition, and it is why tokenisation (Part V) is not a technical footnote. A motion rule that exists only as prose in a PDF cannot be enforced. A motion rule expressed as a token can be enforced automatically, in every build, forever.
This definition absorbs the useful content of all four lenses while remaining falsifiable. You can test whether a specification exists. You can test whether it is being followed. You can test whether audiences attribute the resulting behaviour to your brand. Lenses 1 and 4, taken alone, cannot be tested at all.
⚠ Diagnostic question, worth asking in the first meeting. "When this project is finished, what exactly do we own?" If the answer is a list of files, you have been briefed under Lens 1 and the work will not last eighteen months. If the answer is a set of rules plus the files that prove them, you are building a system.
2. Terminology disambiguation
Four terms are used interchangeably in briefs and mean four different things. Money is lost in the gap.
| Term | What it actually means | Typical deliverable | Owner | ⚠ Confused with |
|---|---|---|---|---|
| Animation | The technique of creating apparent movement. A skill, not a strategy | Rendered files | Animator / studio | Everything below. "We need animation" is a request for labour, not a decision |
| Motion graphics | Design applied to time-based media. Typically 2D graphic elements, type and image, in linear playback | Films, idents, social assets, broadcast packages | Motion designer / studio | Motion identity. Motion graphics are outputs; motion identity is the ruleset that constrains them |
| Motion identity (kinetic identity, brand-in-motion) | The defined, ownable behavioural signature of a brand: easing, timing, choreography, transitions, logo behaviour and sonic pairing, documented as rules | Motion principles, specs, reference films, asset library | Brand / design lead | Logo animation specifically. A logo sting is one application of a motion identity, not the thing itself |
| Interaction motion (UI motion, functional animation) | Motion inside a product that communicates system state, causality and spatial relationships to a user mid-task | Motion tokens, component specs, prototypes, shipped code | Product design + engineering | Motion identity. They share a root grammar but obey different constraints and are measured differently (Ch. 4) |
Three further terms, defined once here and used throughout.
💡 Easing — the rate of change of a movement over its duration. Not where something moves, but how it accelerates and decelerates. The single most expressive and most under-specified variable in the discipline (Ch. 8).
💡 Choreography — the relationship between multiple moving elements: what moves first, what follows, what stays still. Where individual easing conveys personality, choreography conveys hierarchy and intent.
💡 Motion token — a named, machine-readable value representing a single motion decision (a duration, an easing curve, a delay), stored in a shared file and consumed by design tools and production code alike. The mechanism that turns motion prose into motion enforcement (Ch. 44).
⚠ The most expensive terminological confusion in the field: a brief that says "motion identity" and a budget that pays for motion graphics. The client believes they are buying a system; the studio has priced a set of films. Both parties are correct about their own document. The system does not get built, and eighteen months later the brand's motion has fragmented across four agencies. This is not a rare edge case. It is close to the default outcome. Ch. 17 gives you the problem statement that prevents it.
3. Where motion sits, and what motion cannot fix
Motion is bordered by five adjacent disciplines. Practitioners who do not know the borders end up either being blamed for other people's failures or quietly solving other people's problems for free.
Text equivalent — motion map
Strategy feeds motion; motion pairs with sonic and visual; constrained by interaction and engineering.
⭐ Motion design and sonic branding are the same discipline practised in two media, and almost every organisation separates them. They share timing, rhythm, accent and duration. A 1.2-second logo reveal and a 1.2-second audio signature designed in different rooms will not land on the same frame, and the mismatch is perceptible even to audiences who cannot name it. Ch. 31 treats the pairing properly.
What motion can do: make a brand recognisable in the first second of a moving, muted, thumb-scrolled impression; convey temperament — pace, control, warmth, precision — faster than language can; explain what just happened in an interface, and where the user now is; create continuity across touchpoints that share no other visual element; direct attention, in a specific order, within a fixed window of time.
✘ What motion cannot fix
| The problem | Why motion won't fix it | What actually fixes it |
|---|---|---|
| A brand with no distinctive assets at all | Motion is a modifier of elements. With nothing recognisable to move, you are animating anonymity. Attribution fails | Establish at least one ownable visual or verbal asset first, then animate it |
| An incoherent product proposition | Motion communicates manner, not substance. A confident animation on a confused offer reads as evasion | Product and positioning work |
| A slow product | ⚠ Motion can mask small latency and improve perceived speed. It cannot mask real slowness, and above roughly 400ms of added animation it becomes the slowness | Engineering |
| A cluttered interface | Adding movement to clutter produces animated clutter. Motion raises the cost of every bad layout decision | Reduce elements first |
| Internal disagreement about the brand | Motion projects are frequently commissioned as a proxy for a strategy argument nobody wants to have. The argument then re-emerges in review, framed as feedback on easing | Resolve the positioning (Ch. 14) |
| Low brand awareness | Motion improves attribution of impressions you already have. It does not buy reach | Media |
⚠ The commonest structural error in the discipline: commissioning motion to solve a problem in an adjacent box. When a motion project is failing in review and the notes are unresolvable, check whether the actual problem is in strategy, product or engineering. Roughly speaking, if the third round of feedback contradicts the first, you are being asked to fix something motion cannot fix.
4. ⭐ THE GREAT DIVIDE: expression versus function
This is the most important chapter in the report. Almost every unresolvable argument about brand motion is this disagreement, unrecognised. Practitioners on each side believe the other is simply careless. Both are describing real evidence. They are optimising different variables, and neither side usually says which.
School A — The Distinctiveness School
Core claim: motion's job is to be recognised and attributed to your brand.
Intellectual lineage. Descends from the Ehrenberg-Bass tradition — Byron Sharp's How Brands Grow (2010) and, specifically for assets, Jenni Romaniuk's Building Distinctive Brand Assets (2018). The argument runs: buyers are not paying attention, they buy from a small mental repertoire, and brands grow by being easy to notice and easy to remember. Distinctive assets — 💡 sensory cues other than the brand name that trigger the brand in memory — are the mechanism, and they qualify as assets only if they score on fame and uniqueness.
Applied to motion, this yields hard prescriptions. Motion must be idiosyncratic, because generic movement cannot be owned. It must be repeated relentlessly and unchanged for years, because assets are built by repetition and destroyed by refreshes. It must arrive early, because in skippable and scrollable formats, brand behaviour that appears at the end appears to nobody. And consistency beats optimisation: a slightly worse animation used everywhere outperforms a better animation used once.
Its favourite evidence: the survival of kinetic and sonic signatures across decades — the MGM lion, the Intel five-note signature, the THX Deep Note, the Netflix "ta-dum," Channel 4's assembling blocks (Martin Lambie-Nairn, 1982). Vendor research claiming large effectiveness premiums for consistent distinctive assets and for early branding is quoted heavily — Ch. 5 explains why those specific numbers need care.
School B — The Functional School
Core claim: motion's job is to help the user understand what is happening, and then get out of the way.
Intellectual lineage. Descends from human-factors research and interface usability. Val Head's Designing Interface Animation (2016) argued the animation canon — Thomas and Johnston's twelve principles from The Illusion of Life (1981) — is only partially transferable: timing, easing and anticipation matter; solid drawing and staging largely do not. Issara Willenskomer went further, arguing in the UX in Motion Manifesto that borrowing from Disney was a category error, because interface motion serves usability rather than storytelling, and proposing twelve interface-native principles instead — easing, offset and delay, parenting, transformation, value change, masking, overlay, cloning, obscuration, parallax, dimensionality, dolly and zoom.
Nielsen Norman Group supplies the sharpest version of the case, based on repeated usability testing: animation above roughly 400–500ms stops reading as motion and starts reading as lag; scroll-triggered text animation measurably delays reading and comprehension, because users must wait for text to settle before they can read it; expert users pay a repetition penalty, where an animation that delights on first exposure obstructs on the hundredth ("this was nice the first time, but now it's getting annoying"); autoplaying and auto-advancing motion causes users to miss information entirely; and motion that hijacks attention or manufactures urgency is a dark pattern.
Applied to brand motion, this yields the opposite prescriptions. Motion should be nearly invisible — 100–300ms in frequent interactions. It should be conventional, because conventions are learned and idiosyncrasy costs comprehension. It should be skippable, interruptible and disableable. And repetition is not an asset-building mechanism; repetition is where animation becomes a tax.
Why this is a real contradiction, not a misunderstanding
Read the two positions side by side. Repetition is School A's core mechanism and School B's core risk. Idiosyncrasy is School A's requirement and School B's cost. Duration long enough to be noticed and attributed is School A's minimum and School B's failure threshold.
Text equivalent — expression function spectrum
Expression (remembered) to function (understood): cinema ident, brand film, marketing site, banking app.
⭐ When each school earns its keep
| Condition | Expression school wins | Function school wins |
|---|---|---|
| Exposure frequency | Low. Once a week or less | High. Daily or many times daily |
| User state | Passive, browsing, low intent | Active, mid-task, goal-directed |
| Consequence of the moment | Low. Nothing breaks | High. Money moves, data is deleted, a flight is booked |
| Attribution risk | High. Audience may not know whose message this is | Low. The user opened your app deliberately |
| Competing stimuli | Many. Feed, channel, shelf | Few. The user is inside your product |
| Skill of audience | Novice, or one-time | Expert, repeat |
| Dominant failure mode | Being ignored or misattributed | Wasting time, causing errors, causing nausea |
| Correct duration band | 800 ms – 8 s (Ch. 6) | 100–300 ms (Ch. 6) |
| ⚠ Its own characteristic overreach | Idiosyncrasy applied to high-frequency interactions. "Ownable" loading spinners. Branded easing on a keyboard input | Function applied to low-frequency brand moments, producing platform-default motion no one can attribute to anyone |
The synthesis: frequency governs, grammar unifies
The resolution is not compromise. It is partition by exposure frequency, unified by shared grammar.
Both schools are right within their frequency band and wrong outside it. The variable that decides which applies is not the medium, not the channel and not the department — it is how often the same person will see this same motion. A brand film seen once a quarter and a button state seen forty times a day are not the same design problem, and a motion identity that specifies one rule for both is guaranteed to fail one of them.
What holds the two dialects together is not shared duration but shared grammar — the same easing family, the same directional logic, the same choreographic order, scaled to fit.
Expressive
Functional
Expressive
Functional
Text equivalent — root grammar tree
One grammar; expressive dialect for low frequency; functional for high frequency with same curves and order.
◇ Allocation heuristic. In mature systems, expressive motion typically accounts for a small minority of instances and the large majority of production budget; functional motion is the reverse. If your motion budget is going 90% to expressive assets while 95% of your brand's motion impressions are functional interface behaviour, you are funding the wrong half of your own brand. This ratio is the single most useful thing to calculate in a first audit (Ch. 10).
Contrast pair: the same tactic, two outcomes, one company
Both cases are Apple. Both are system-wide expressive motion applied at the highest-frequency touchpoint that exists — the operating system.
| iOS 7, 2013 | The reduced-motion era, 2013 onward | |
|---|---|---|
| Tactic | Expressive motion made a defining property of the OS: zoom transitions on app launch, parallax on the home screen | Same expressive ambition, retained and extended across later systems |
| What happened | Widespread user reports of dizziness, nausea and disorientation. Apple shipped a Reduce Motion accessibility setting in a point release | Motion preference became a first-class, OS-level user setting, later mirrored on the web as the prefers-reduced-motion media query, and expressive motion continued to ship — with a governed escape hatch |
| Why the difference | Expression was shipped without an opt-out. The motion was not wrong; the absence of a control was | Expression is shipped with a specified degraded state. The brand keeps its behaviour; the vulnerable user keeps their balance |
Transferable lesson. Expressive motion is not risky because it is expressive. It is risky when no one has specified what happens for the user who cannot tolerate it. ⚠ The design of the reduced state is part of the motion identity, not a compliance afterthought (Ch. 16).
5. The case for taking motion seriously — and the numbers you should not repeat
There are two versions of this argument. One is statistical and popular. The other is structural and defensible. Learn both, and know which to use in front of a CFO who reads footnotes.
The statistical case, and its problems
These figures circulate constantly. Every one is indicative rather than settled — and in each case the publishing organisation sells either the measurement or the asset being validated. That does not make them false. It makes them unaudited.
| Claim | Source type | ⚠ Why it needs care |
|---|---|---|
| Sonic assets lift brand awareness by ~191% in the first two seconds of exposure, several times the effect of a visual logo | Ad-testing vendor | Effect size implausibly large relative to any published perception research; method and comparison baseline not independently reviewed |
| Ads with sonic branding are ~8.5× more effective than visual-only | Research agency | "Effective" undefined across a multiplier of that size; almost certainly a composite index, not a business outcome |
| Campaigns using recurring characters or devices overperform by ~32% on share and profit gain | Ad-testing vendor | Plausible direction, consistent with distinctiveness theory. Selection effects unaddressed: brands able to sustain a device for years differ systematically from those that cannot |
| Distinctive-asset-led integrated campaigns are 31% more effective, rising to 57% when customised per channel | Research agency | Directionally consistent with distinctiveness theory; the specific integers are not independently reproducible |
| Meaningful brand outcomes achievable from ~1.5 seconds of active attention | Attention-measurement vendor | The underlying attention research is serious work; the threshold is nonetheless a vendor-defined metric using vendor-defined instrumentation |
| A brand's own reported trust and assurance lift following a sonic and animated checkout confirmation | First-party brand claim | First-party, published for reputational purposes. Directionally interesting; not evidence of a general law |
✔ How to use these. Quote them once to establish that the field takes motion seriously. Never build a business case on them. If your case collapses when one figure is challenged, you did not have a case.
✘ How not to use them. Placing "8.5× more effective" on slide two of an investment deck. The first finance person to search the source will find a vendor, and your entire argument loses credibility for a number you did not need.
⭐ The structural case, which needs no contested statistics
The honest argument for motion does not rest on effect sizes. It rests on a change in the composition of brand impressions that is not seriously disputed by anyone.
1. The majority of brand impressions are now moving. Feeds, short-form video, streaming interfaces, in-app surfaces, connected TV, digital out-of-home, in-product notifications. The static poster is now the exception in most categories, not the norm.
2. Most of those impressions are muted, partial and brief. Sound-off autoplay, partially-scrolled viewports, skippable pre-roll. Motion is often the only variable the brand controls that survives all three conditions — colour survives, but colour alone is rarely unique; type survives, but rarely at that size; sound frequently does not arrive at all.
3. Static-only identity systems cannot govern moving impressions. This is the crux. A brand book that specifies logo, palette, type and grid says nothing about pace, easing, choreography, entrance, exit, or the relationship between a reveal and an audio accent. In the absence of a rule, every producer invents one. Within eighteen months a brand with thirty external content producers has thirty motion behaviours, and no one is accountable, because no rule was broken.
4. Motion has become the primary interface material. Both dominant platform design languages moved to physics-based motion in 2025 — Google's Material 3 Expressive introduced spring-based spatial and effects motion, and Apple's Liquid Glass made responsive, light-reactive material behaviour central across its platforms. The implication for brands is uncomfortable: the default motion of the platform is now strongly characterful. A brand that does not specify its own behaviour in-product does not get neutral behaviour. It gets Google's personality, or Apple's.
5. Motion is now the primary lever of legal exposure in identity. As of three days ago — 2 August 2026 — EU AI Act Article 50 transparency obligations became enforceable. Providers must ensure synthetic audio, image, video and text outputs are marked in a machine-readable, detectable format; deployers must visibly disclose deepfake content and AI-generated text published to inform the public on matters of public interest. Penalties reach €15m or 3% of worldwide annual turnover, whichever is higher. The July 2026 Digital Omnibus on AI (Regulation (EU) 2026/1744) left the enforcement date intact but granted a narrow transition to 2 December 2026 for machine-readable marking on generative systems already placed on the market before 2 August 2026 — ⚠ with no grace period for systems placed on the market on or after that date. In practice, marking is being implemented through provenance standards such as C2PA Content Credentials.
Add the European Accessibility Act, applicable since 28 June 2025 and referencing EN 301 549, which incorporates WCAG 2.1 Level AA; add Ofcom Rule 2.12 and mandatory photosensitive-epilepsy testing for UK broadcast advertising. Static identity carries almost no comparable exposure. Motion carries all of it (Ch. 68–70).
The one-sentence version for the boardroom: Most of what people now see of this brand is moving, and we currently have no rule governing how it moves — which means we are neither consistent nor compliant, and we cannot prove we are either.
⚠ Do not oversell. As of August 2026 there is no published controlled study demonstrating that adopting a motion identity caused a commercial outcome. The full inference chain, and what to do about it, is in Ch. 57.
6. Why motion works on the human perceptual system
Motion design is unusual among design disciplines in that its core effects rest on genuinely robust experimental psychology, most of it eighty years old, most of it unknown to practitioners. Knowing the mechanism converts taste arguments into technical arguments. It is the difference between "this feels wrong" and "this violates perceived causality, so users will read the second element as unrelated to the first."
1. Humans attribute personality and intention to moving abstract shapes. Heider and Simmel (1944). Participants watched a short animation of two triangles and a circle moving around a rectangle. Almost every viewer spontaneously described a social narrative: a bully, a victim, a chase, a hero. No faces. No bodies. Just geometry, moving. This is the empirical foundation of the entire "motion as brand behaviour" claim, and it is much stronger than most practitioners realise. You do not get to choose whether your brand's movement conveys character. Audiences will attribute character to it regardless. You only choose whether the character is the one you intended. ⚠ An unspecified motion system is not neutral. It is a personality assigned by whichever freelancer had the deadline.
2. Timing determines whether viewers perceive cause and effect. Michotte (1946). In experiments on the "launching effect," a moving object contacts a stationary one, which then moves. Viewers perceive direct physical causation — but only within tight timing tolerances. Introduce a small delay between contact and departure and the perception of causality collapses; the two events read as independent. When a user taps and a panel appears, whether they perceive "my tap caused this" or "something happened, separately" is a function of delay measured in tens of milliseconds. This is not a preference. It is perceptual physics.
3. Movement is read as biological before it is read as anything else. Johansson (1973). Point-light displays — a handful of dots attached to a walker's joints, everything else invisible — are recognised as human motion within a fraction of a second. Humans are extraordinarily tuned to the signature of living movement. This is why easing works and 💡 linear easing — constant velocity from start to finish — feels dead: it matches no biological or physical motion in the observer's experience.
4. Things that move together are perceived as belonging together. Gestalt common fate. Elements sharing a direction and rate of change are grouped perceptually, overriding proximity and similarity. This is the most under-used tool in brand motion. You can create perceptual grouping between elements that share no colour, no shape and no position, purely by moving them alike. For brands operating across wildly different touchpoints with little visual commonality — a broadcaster's on-air package and its app, say — common fate is often the only available unifier (Ch. 43).
5. Without motion, humans miss changes that are directly in front of them. Change blindness; Rensink, O'Regan and Clark (1997). Substantial changes to a scene go unnoticed when the transient visual signal that normally accompanies change is suppressed. An instantaneous state change is frequently not seen; motion supplies the transient that directs the eye. Removing animation entirely does not produce a neutral interface — it produces one where users miss things. ⚠ Note the tension with Mechanism 1 and with NN/g's findings: the same property that prevents change blindness enables dark patterns.
6. Response-time thresholds are stable and old. Human tolerance for system delay has been characterised consistently since the 1960s: around 0.1 second is perceived as instantaneous; around 1 second preserves uninterrupted flow of thought; around 10 seconds is the limit of attention on a task. The IBM "Doherty threshold" work (1982) established that system response under roughly 400ms produces disproportionate gains in productivity and engagement. Overlay NN/g's testing-based observation that interface animation beyond roughly 400–500ms begins to read as lag and you get a convergent, well-founded band.
Text equivalent — duration ladder
- 0–50 ms: Change blindness risk
- 50–100 ms: Micro-feedback
- 100–200 ms: Functional band — toggles, buttons
- 200–300 ms: Functional — panels, cards
- 300–400 ms: Approaching Doherty threshold
- 400–500 ms: Reads as lag if repeated
- 500 ms – 8 s: Expressive territory only
So what. Six mechanisms, six arguments you can now make without appealing to taste. And one synthesis: motion is powerful because it recruits perceptual machinery the audience cannot switch off. That is precisely why it must be governed rather than decorated.
7. The building blocks: what can actually move
Every motion decision in existence is a change to one of a small, finite set of properties over time. Practitioners who work from this list produce specifiable motion. Practitioners who work from references produce motion that cannot be written down.
| # | Property | 💡 What it means | Expressive range | Rendering cost | ⚠ Notes |
|---|---|---|---|---|---|
| 1 | Position (translate) | Movement through space | Very high — direction carries meaning | Cheap. Compositor-only via transform | ⚠ Animating top/left/margin instead forces layout recalculation and causes jank (Ch. 15, Ch. 46) |
| 2 | Scale | Growth or shrinkage | High — implies importance, arrival, emphasis | Cheap via transform | Scale plus position is the workhorse pair of interface motion |
| 3 | Rotation | Turning | Moderate — quickly reads as playful or mechanical | Cheap via transform | ⚠ Ages badly. Rotation-heavy systems date faster than any other choice |
| 4 | Opacity | Fade in or out | Low on its own — the safest and most anonymous property | Cheap | ✔ The correct default when reduced motion is requested (Ch. 16) |
| 5 | Colour | Hue, saturation, brightness over time | Moderate; strong when tied to state | Moderate — triggers paint | Underused in brand motion. Colour transitions can be as ownable as colour |
| 6 | Shape / path | Morphing outlines, drawing on, masking | Very high — the most ownable property there is | Expensive. Path interpolation is costly | ⚠ Where most logo animations live, and where most performance problems live |
| 7 | Blur / depth of field | Focus shifts | High — implies attention and hierarchy | Expensive on low-end devices | Central to contemporary "material" interface languages; budget for it |
| 8 | Sound | Audio accent, signature, texture | Very high — and processed fast | Negligible compute, high rights cost | ⚠ Absent in most impressions. Never load meaning solely onto audio |
| 9 | Easing (meta-property) | The velocity curve applied to any of 1–8 | Very high | Free | Ch. 8. The most expressive and most under-specified variable in the discipline |
| 10 | Choreography (meta-property) | Timing relationships between elements: order, stagger, overlap | Very high | Free | Conveys hierarchy and intent. Where a system stops looking like a collection of animations and starts looking like one brand |
8. Easing, and the grammar of curves
If motion identity has a single technical centre, it is here. Two brands can animate identical elements over identical durations in identical directions and feel completely different, entirely because of easing.
💡 Easing (also timing function) describes how a value changes across a duration. Plotted with time on the horizontal axis and progress on the vertical, the shape of the line is the character of the movement.
Linear
Robotic. Loops only.
Ease-out
Default entrances.
Ease-in
Exits and dismissals.
Ease-in-out
Smooth both ends.
Spring
Overshoot, gesture feel.
The two ways easing is specified, and why the difference is commercial
Cubic Bézier — the duration-based model. A curve defined by four numbers, e.g. cubic-bezier(0.2, 0, 0, 1), paired with a fixed duration. Deterministic, portable across platforms, trivially tokenisable. The W3C Design Tokens Community Group specification supports exactly this: first-class duration and cubicBezier types, plus a composite transition type combining duration, delay and timing function.
Spring physics — the model-based approach. Motion defined by mass, stiffness and damping rather than a duration. It has no fixed end time; it settles. Interruptible mid-flight and responsive to gesture velocity, which is why it dominates modern touch interfaces. Material 3 Expressive shipped spring-based spatial springs for layout movement and effects springs for non-spatial properties such as colour and opacity in 2025.
A third option now sits between them. 💡 linear() — a CSS easing function that accepts a list of sampled progress points, allowing an arbitrary curve, including a flattened approximation of a spring, to be expressed as a portable, deterministic value. It is how design tools currently export spring motion into environments that cannot compute physics. Ch. 45 explains why this matters for governance.
⚠ The specification model is a governance problem disguised as a technical one. As of mid-2026 the token standard has no first-class type for spring physics, keyframes or complex composite motion — teams needing them fall back on custom $extensions or work outside the standard. Read that in brand terms: the industry's motion tokenisation standard cannot yet natively express the motion model that both dominant platforms have adopted. That is not a reason to avoid springs. It is a reason to know exactly which parts of your system are governed and which are documentation. Ch. 45 gives you the workaround and the honest limitations.
Duration and easing heuristics ◇
| Heuristic | The rule | Why | Exception |
|---|---|---|---|
| Exits are faster than entrances | Exit at roughly 70–80% of entrance duration | Arriving content needs to be comprehended; departing content does not | Dismissals the user may want to reverse |
| Distance scales duration, sub-linearly | Doubling distance ≠ doubling time | Constant duration across distances makes long moves feel slow and short moves feel violent | Fixed-duration systems where consistency matters more |
| Larger objects move slower | Big surfaces need more time | Implied mass. Physics we all learned before we could speak | — |
| Ease-out for arrivals, ease-in for departures | Fast start, slow settle in; slow start, fast exit out | Matches the perceptual expectation of things coming to rest | Springs replace both |
| Never linear except for loops | Continuous rotation and progress indicators only | Linear reads as mechanical (Ch. 6, Mechanism 3) | Progress and loading indicators, where mechanical is honest |
| One easing family per brand | Pick a curve character and use it everywhere | ⭐ The entire distinctiveness mechanism available at zero rendering cost | — |
RENDERING
ACCESSIBILITY
ENFORCEMENT
PORTFOLIO
No other element of an identity system has four independent reasons to be the answer.
And it is competitively safe. Colour can be matched. Type can be licensed by competitors. Layout converges on platform convention. Easing is effectively unpoliced, unregistrable and almost never copied — because almost nobody looks at it.
A brand that commits to a single distinctive curve character and applies it to every property, at every duration, across every touchpoint, has built a distinctive asset that costs nothing to render, degrades gracefully, survives compression, works muted, works in a 100ms button state and works in an eight-second ident. It is the only element of a motion identity that scales across the entire frequency spectrum unchanged.
Text equivalent — why the brand belongs in the curve
- RENDERING: Easing and choreography are free; the most ownable properties are the most expensive (Ch. 7)
- ACCESSIBILITY: Curve and order survive Tier 2 reduced motion fully intact; distance travelled and parallax do not (Ch. 16)
- ENFORCEMENT: cubicBezier and duration are in the token spec; springs, keyframes and morphing are not (Ch. 45)
- PORTFOLIO: Sharing easing and stagger alone produces perceptible family resemblance at zero local-freedom cost (Ch. 43)
No other identity element has four independent reasons. Easing is unpoliced and rarely copied. A single distinctive curve scales across the frequency spectrum unchanged.
✔ The action. Before specifying a single animation, specify the curve. Two or three curves maximum — one for entrances, one for exits, optionally one for emphasis. Name them. Tokenise them (Ch. 44). Refuse all others.
✘ The failure. A "motion guidelines" PDF listing eleven easing curves "for different moods." Eleven curves is no curve. Nobody chooses correctly under deadline, and the brand has no behavioural signature at all.
9. From brand attributes to motion parameters: solving the adjective problem
Every motion brief in the world arrives containing the same four words: dynamic, premium, human, bold. Not one of them specifies anything. This chapter is the translation layer, and it is the difference between a motion project that converges and one that loops through six rounds of subjective feedback.
⚠ The adjective trap. Brand attributes are chosen to be aspirational and inclusive. Motion parameters must be exclusive and numerical. The two are structurally incompatible until someone does the translation, and the translation is normally attempted for the first time in a review meeting, verbally, by a committee. That is why it fails.
Brand layer
- “Confident”
- “Innovative”
- “Human”
- “Premium”
Motion layer
- duration: 240ms
- curve: cubic-bezier(...)
- stagger: 40ms
- overshoot: none
Text equivalent — translation gap
Bridged: opposed pairs mapped to parameters. Unbridged: six rounds of “more premium.”
The method: decompose attributes into opposed parameter pairs
Do not attempt to define "premium." Define what premium rules out. Motion character is far more reliably specified by exclusion than by aspiration.
| Opposed pair | Governed by | Low end | High end |
|---|---|---|---|
| Restrained ↔ Exuberant | Overshoot amount; number of simultaneous moving elements | No overshoot; 1–2 elements | Visible overshoot; 5+ elements |
| Deliberate ↔ Immediate | Duration; anticipation before the main move | 400ms+, visible wind-up | 120ms, no anticipation |
| Precise ↔ Organic | Easing symmetry; whether elements share timing exactly | Identical timing, symmetrical curves | Staggered, offset, slightly varied |
| Weightless ↔ Substantial | Implied mass: settle time, scale-to-duration ratio | Fast, no settle | Slow settle, longer decay |
| Ordered ↔ Emergent | Choreographic sequencing | Strict sequence, clear order | Overlapping, simultaneous |
| Continuous ↔ Punctuated | Whether motion flows or resolves in beats | Uninterrupted flow | Distinct stops, held frames |
Worked translation
Brand attributes: confident, precise, warm. Three words. Six rounds of feedback waiting to happen. Now translated:
| Attribute | Decomposed as | Parameter consequence | ✘ What it rules out |
|---|---|---|---|
| Confident | Immediate, not deliberate. Restrained, not exuberant | Short durations (160–240ms functional). No anticipation — the move begins on the input. No overshoot | Wind-up, bounce, hesitation, easing-in on user-triggered events |
| Precise | Ordered and Precise ends | Strict choreographic order. Identical stagger interval (e.g. exactly 40ms). Symmetrical, mathematically clean curve | Random offsets, organic variation, "hand-feel" timing, springs with visible wobble |
| Warm | Substantial, not weightless. Slight organic lean | Visible settle at the end of movement. Ease-out with a long tail rather than a hard stop | Linear motion, abrupt stops, mechanical constant velocity |
Resolved specification — a system, in four lines:
easing.entrance : cubic-bezier(0.16, 1, 0.3, 1) // long soft tail = warm settle
easing.exit : cubic-bezier(0.7, 0, 0.84, 0) // decisive = confident
duration.fn : 180 ms (±40 by element size)
stagger : 40 ms, fixed, never randomised
overshoot : 0 // non-negotiable
anticipation : none on user-triggered motion
⚠ Notice what happened. "Confident, precise, warm" now forbids overshoot, bounce, randomised timing and anticipation. A specification that forbids nothing specifies nothing. If your motion principles could describe your three closest competitors, you do not have motion principles; you have adjectives.
The review-language upgrade
The practical payoff arrives in review. Feedback stops being aesthetic and becomes parametric.
| ✘ Before | ✔ After |
|---|---|
| "It doesn't feel premium enough" | "Move it two steps toward Restrained: drop the overshoot and reduce to two simultaneous elements" |
| "Can it be more dynamic?" | "Shorten to the Immediate end: 140ms, remove the anticipation frame" |
| "It feels a bit cheap" | "The stagger is randomised — that reads Organic, and we specified Precise" |
| "Make it more us" | ⚠ Unanswerable. Send the reviewer back to the parameter table |
So what. This single table is the most reused artefact in most motion projects. It converts the discipline's dominant time-sink — subjective circular feedback — into a bounded technical conversation. Appendix A includes it as a template.
Part II — Diagnosis Before Prescription
⚠ Everything in Part II happens before anyone opens a design tool. The single strongest predictor of a failed motion project is that it began with a moodboard. Seven chapters of diagnosis, one gate.
10. The motion audit
You cannot specify a brand's behaviour without first establishing how it currently behaves. Almost no organisation knows. The audit is unglamorous, takes two to three weeks, and routinely produces the finding that changes the brief entirely.
| Dimension | The question | Typical finding |
|---|---|---|
| Inventory | Where does this brand currently move? | 3–10× more places than the client believes. Nobody has ever listed them |
| Ownership | Who produced each? Under what rule? | No rule. Multiple external producers, each with house habits |
| Variance | How different are the easing, durations and choreography? | ⚠ Extreme. Same logo revealed six ways in twelve months |
| Frequency | How often does a real person see each? | The Ch. 4 inversion: highest-frequency motion is almost always the least designed |
| Attribution | Could a category buyer identify the brand from the motion alone? | Usually no. Ch. 11 — test rather than assume |
| Compliance | Reduced-motion states? PSE clearance? AI disclosure? | Gaps, undocumented, unowned |
| Cost | What is being spent, on what, by whom? | Fragmented across marketing, product and regional budgets. Nobody has the total |
| Performance | What does the motion cost the product technically? | Unmeasured (Ch. 15) |
⚠ This is the chart that changes the budget conversation, and it is why the audit must precede the brief. A client who arrived asking for a new logo animation frequently leaves the audit asking for interface motion tokens instead. That reallocation is often worth more than everything else in the project combined.
Audit method — 12 steps
- Define the boundary. Which markets, which products, which sub-brands. Write it down; scope creep in audits is silent and fatal.
- Crawl, don't ask. Capture screen recordings from real devices on real networks. What the brand does differs from what the brand book says.
- Capture the product, not just the marketing. ⚠ The single most-skipped step. Record every transition, state change and loading state in the live product.
- Include third-party surfaces. Marketplace listings, connected-TV interfaces, partner apps, retail screens, hold animation on phone systems.
- Log the parameters, not the impressions. For each instance: duration, easing (measure it frame-by-frame if undocumented), properties animated, sound present, interruptible, reduced-motion behaviour.
- Trace provenance. Who made it, when, under what brief, using what tool, and is the source file retrievable? ⚠ Un-retrievable source files are a migration blocker (Ch. 50).
- Estimate frequency. Pull real analytics. Sessions × interactions per session. Order of magnitude is what matters.
- Estimate spend. Include internal time. Most organisations find 40–60% of motion cost is invisible internal labour.
- Test attribution (Ch. 11).
- Test performance (Ch. 15).
- Test compliance (Ch. 16, plus Ch. 68–70).
- Plot the two charts: frequency-weighted investment, and variance.
Same brand, same logo reveal, 12 months
| Instance | Duration | Easing | Sound | Direction |
|---|---|---|---|---|
| TV ident | 1400ms | ease-out | yes | scale up |
| Pre-roll | 800ms | linear | no | wipe L→R |
| Web hero | 600ms | ease-in-out | no | fade only |
| App splash | 350ms | spring, bouncy | yes | scale down |
| Event screen | 2200ms | ease-in-out | yes | rotate in |
| Email GIF | 500ms | linear | n/a | wipe R→L |
⚠ Six behaviours. Six producers. Zero broken rules, because no rule existed. Present this table and the mandate for a system arrives on its own.
Text equivalent — variance chart
- TV ident: 1400ms, ease-out, sound yes, scale up
- Pre-roll: 800ms, linear, sound no, wipe L→R
- Web hero: 600ms, ease-in-out, sound no, fade only
- App splash: 350ms, spring, bouncy, sound yes, scale down
- Event screen: 2200ms, ease-in-out, sound yes, rotate in
- Email GIF: 500ms, linear, sound n/a, wipe R→L
11. Distinctive asset testing, applied to movement
The distinctiveness school gives us the only rigorous method for answering the question every motion project should but rarely does ask: does this movement actually mean us to anybody?
💡 Distinctive asset — a sensory cue other than the brand name that triggers the brand in a buyer's memory.
Romaniuk's framework scores each candidate on two dimensions, tested by showing category buyers the asset with all brand names and logos removed and asking, unprompted, which brand it belongs to:
- 💡 Fame — the proportion of category buyers who link the asset to your brand.
- 💡 Uniqueness — how exclusively it links to you rather than also triggering competitors. Of the two, uniqueness is more critical; a famous asset that also cues three rivals is actively working for the category, not for you.
⭐ Adapting the test for motion — the four modifications
Static asset testing shows a still image. Motion cannot be tested that way, and the naive adaptation produces useless results.
1. Strip more aggressively than you think. For a static asset you remove the wordmark. For motion you must remove wordmark, palette, typeface and the shape being animated — otherwise you are testing the logo, not the motion. Test the behaviour on neutral grey geometry. ⚠ Practitioners resist this because the result is usually humbling. That humility is the finding.
2. Test at real duration and real conditions. Muted. At actual playback speed. On a phone. Testing an eight-second showreel edit of a 400ms transition measures nothing that exists in the wild.
3. Separate the two dialects. Expressive and functional motion must be tested separately. Different exposure, different recognition mechanism, different realistic ceilings. ⚠ Expect functional interface motion to score low on fame almost universally — that is not failure, it is the nature of the band. Judge functional motion on within-brand consistency and task metrics, and reserve fame testing for the expressive dialect.
4. Test the curve alone. The most revealing and least-performed test in the discipline: show the same neutral shape moving with your easing curve and with three competitors' curves. Ask which is yours. If nobody can tell, your easing is not yet an asset — and since easing is your cheapest distinctiveness lever (Ch. 8), that is the highest-value gap on your board.
Method: a workable motion distinctive-asset test
| Step | What you do | ⚠ Watch for |
|---|---|---|
| 1 | Identify 6–12 candidate motion assets from the audit | Don't only test what you like; test the highest-frequency instances |
| 2 | Rebuild each on neutral geometry, stripped of all other identity cues | Rebuild rather than crop; cropping leaks colour and type |
| 3 | Recruit category buyers, not designers and not only existing customers | ⚠ Designers over-perform wildly and will flatter you |
| 4 | Show unbranded, at real duration, muted, on mobile | Randomise order; avoid category priming in the intro |
| 5 | Ask unprompted: "Which brand, if any, does this belong to?" | Open text before any prompted list |
| 6 | Then prompted: "Which of these brands could this belong to?" — where uniqueness is measured | Include the real competitive set, not aspirational peers |
| 7 | Plot on the grid. Repeat annually, same method | Method drift destroys year-on-year comparability |
⚠ Sample and confidence. Robust fame and uniqueness estimates need several hundred category buyers per market to distinguish a 12% score from an 18% one. Below roughly n=200 you can identify catastrophe and obvious strength, and nothing in between. Budget accordingly, or state plainly that you are running a directional read rather than a measurement. Claiming precision you do not have is worse than admitting a directional test.
⚠ The dissent: where the distinctiveness school over-reaches on motion
The distinctiveness framework was developed and validated on static assets, packaging and characters. Applying it wholesale to motion imports two unexamined assumptions.
First, it assumes motion assets build fame at rates comparable to static ones. There is no published evidence establishing this. Motion is time-bound and often muted and partially viewed; recognition may build considerably more slowly. Treating a low fame score after twelve months as failure may simply be measuring impatience.
Second, "never refresh a distinctive asset" collides with technical reality. Static assets are stable because printing is stable. Motion assets sit on shifting platform substrates: aspect ratios change, autoplay policies change, platform motion languages change — both dominant systems moved to physics-based motion in 2025. A motion asset that never changes will eventually be technically wrong even while remaining strategically right. Ch. 50's migration craft exists precisely because "never change it" is not fully available to this discipline.
So what. Run the test anyway — it is the only honest answer to "is our motion working?" — but interpret it with these two caveats stated in the deck. And run the curve test. It costs almost nothing and it is the one result that reliably surprises everybody in the room.
12. Research and evidence methods, and each one's characteristic failure mode
Every method in this field has a specific, predictable way of misleading you. Knowing the failure mode is more valuable than knowing the method.
| Method | What it answers well | ⚠ Characteristic failure mode | Use when |
|---|---|---|---|
| Distinctive asset testing (Ch. 11) | Do people attribute this movement to us? | Low sensitivity below n≈200; requires a competitive set you may define wrongly | Annually, on expressive assets; as a pre/post around a system launch |
| Attention measurement (eye-tracking, webcam panels) | Was it seen at all, and for how long? | Vendor-defined metrics; lab conditions inflate attention versus real feeds; measures looking, not encoding | Comparing two edits of the same asset; validating early branding |
| Moment-by-moment emotional / facial coding | Where does an expressive asset lose people? | Measures expressed affect, not memory or behaviour; weak for subtle, restrained motion — precisely the motion premium brands want | Long-form expressive assets; diagnosing a drop-off point |
| Standard ad pre-testing (rated frameworks) | Will this asset clear a minimum bar? | ⚠ Systematically penalises restraint and rewards conventional emotional structure. Distinctive-but-quiet motion tests as "bland" and gets killed | As a floor check, never as a selection mechanism between good options |
| Moderated usability testing | Does functional motion help or hinder a real task? | Small n; participants are on first exposure, which is exactly the wrong exposure for judging repetition penalty | Before shipping any high-frequency motion |
| Longitudinal / diary study | The repetition penalty — does it annoy on day 30? | Expensive, slow, high attrition | ⭐ Before committing idiosyncratic motion to a daily-use surface. Almost nobody does this; the highest-value under-used method in the field |
| A/B or multivariate testing in production | Causal effect on a behavioural metric | Optimises short-term conversion, structurally blind to long-term brand effects. ⚠ Will reliably tell you to remove distinctive motion, because distinctiveness has no same-session payoff | Interface motion where the metric genuinely is task completion |
| Performance instrumentation (Ch. 15) | What does this motion cost in responsiveness and battery? | Measures the median device, not the tenth-percentile device where the damage is | Continuously, in CI, on every build |
| Accessibility user testing with motion-sensitive participants | Does this harm people? | ⚠ Almost never commissioned. Automated checks cannot detect vestibular discomfort | ⭐ Before any parallax, scroll-driven or large-surface motion ships |
| Expert / heuristic review | Fast identification of obvious errors | Reflects the reviewer's school (Ch. 4). Ask which school before accepting the verdict | Early, cheap, as a filter |
| Competitive motion teardown (Ch. 13) | What does the category already own? | Convergent thinking: benchmarking against the category is how you end up in the ⚠ AVOID quadrant | Once, at the start, to define what to refuse |
⭐ The methodological trap that kills more good motion than any other
A/B testing and distinctiveness are structurally opposed, and almost no organisation notices.
Distinctive assets work by accumulating memory over years. A/B tests measure behaviour within a session or a week. A distinctive motion asset therefore shows up in an A/B test as pure cost — added milliseconds, no lift — and is removed. The test was correctly executed and the conclusion is wrong.
⚠ Any organisation that governs motion decisions primarily through conversion testing will, over a few years, systematically strip out every distinctive behaviour it has and converge on platform defaults. It will do so while believing it is being rigorous. This is not hypothetical; it is the standard trajectory of motion in conversion-optimised product organisations.
✔ The fix, and it is a governance fix, not a research fix: classify motion by dialect before testing (Ch. 4). Functional motion is legitimately governed by A/B and task metrics. Expressive motion is governed by attribution and consistency metrics and is explicitly exempted from conversion testing, with that exemption written into the governance model (Ch. 51) and signed by whoever owns the brand. Without the written exemption, the exemption does not survive contact with a quarterly target.
13. Reading the category's motion landscape
The purpose of this analysis is not to find best practice. It is to find out what the category already owns, so you can refuse it.
- Define the real competitive set. Who a buyer might genuinely confuse you with, not who you admire. ⚠ Include the category leader even if you consider them irrelevant; their behaviour is the category's default and the strongest source of misattribution.
- Capture, don't remember. Record 10–20 motion instances per competitor, across both dialects.
- Measure their parameters. Duration, easing character, properties animated, choreographic order. Frame-by-frame where needed. This is tedious and it is the whole value.
- Plot the category on the parameter pairs from Ch. 9.
- Find the empty space. Not the best space — the empty space. Then check it is empty because nobody took it, not because it is unusable.
⚠ The convergence trap. Category analysis reliably produces convergence unless you explicitly invert it. Everyone benchmarks; everyone lands in the middle; the middle becomes the category cue; the category cue is the ⚠ AVOID quadrant. The correct output of this chapter is a list of behaviours you are forbidden from using, not a list of behaviours to emulate.
✔ Deliverable format that works: a one-page "Category Defaults — Do Not Use" list. Six to ten specific behaviours, each with the competitor who owns it. It is the most-referenced page of most motion projects because it makes rejection defensible in review: "we can't use the upward-drift reveal, that's theirs, here's the frame."
14. Reading the stakeholders and their real motives
Motion projects fail organisationally more often than creatively. Stated motives and actual motives diverge, and motion is unusually prone to becoming a proxy battleground because it is visible, expensive, subjective and sits across three departments that report to different people.
| Stakeholder | Stated motive | ⚠ Frequent actual motive | What they will block, and how to serve them honestly |
|---|---|---|---|
| CMO / brand director | Consistency and distinctiveness | Visible evidence of change under their tenure; something showable at the next all-hands | Blocks subtlety. ✔ Give them one high-visibility expressive artefact and the unglamorous token work; let the film buy the system |
| Head of product / design | Usability and system integrity | Protecting the design system from external interference and unfunded work | Blocks brand-driven motion arriving as a PDF. ✔ Deliver tokens and specs in their format, in their repo, or expect polite non-adoption |
| Engineering lead | Performance and maintainability | Not being handed unimplementable specifications with no time allocated | Blocks anything springs-shaped and unbudgeted. ✔ Bring them in at diagnosis, not handover (Ch. 15) |
| Regional / local marketing | Local relevance | Autonomy; not being governed from head office | Blocks by quiet non-compliance. ✔ Give them adaptable templates within fixed rules; specify what cannot change and let everything else flex |
| Legal / compliance | Risk | Not being the person who approved the seizure-inducing ad | Blocks late, hard, and at the worst moment. ✔ Involve at diagnosis (Ch. 68–70) |
| Accessibility lead (where one exists) | Compliance and inclusion | Being consulted before decisions rather than after | Blocks at launch when ignored. ✔ Ch. 16 makes them a diagnostic input |
| Agency / studio | Best work | A portfolio piece; ⚠ a scope defined as production, because production is billable and governance is not | Won't block; will quietly under-deliver on the systems layer. ✔ Put governance artefacts in the contract as named deliverables with acceptance criteria |
| The person who will actually make 200 assets next year | Usually not consulted | Wants the system to be fast and unambiguous under deadline | ⭐ The most predictive stakeholder for whether the system survives. ✔ Interview them in week one. Every time |
⭐ The single question that surfaces the real project
Ask each senior stakeholder, separately, in writing:
"Eighteen months after this launches, what will be true that isn't true today?"
Then compare the answers. Convergent answers mean a real, shared brief; proceed. ⚠ Divergent answers mean you are being asked to resolve a strategy disagreement using easing curves. Stop and escalate. No amount of craft resolves this, and the disagreement will resurface as unresolvable third-round feedback (Ch. 3).
Case card — Jaguar, November 2024
The most instructive recent case, and the most misread.
- What happened: a radical repositioning toward ultra-luxury EV. Retirement of long-standing brand devices. A launch film built on abstract expressive motion, colour and typography, with no vehicle shown, carrying lines including "Copy Nothing" and "Delete Ordinary".
- What followed: immediate, large-scale public and press backlash. European registrations collapsed to a reported 49 units in April 2025, down from close to 2,000 a year earlier — ⚠ but attributing that collapse to the motion identity is wrong. The company had deliberately ceased legacy internal-combustion production ahead of an all-electric relaunch, so dealers had almost nothing to sell. The commercial number is a production decision, not an advertising effect.
- The genuinely motion-relevant detail: a leaked letter from Jaguar's own design team to their chief creative officer reportedly expressed frustration that the identity — developed with an external partner — felt disconnected from the actual vehicles, and that its character read as "too rounded and playful" against the intended exuberance.
Transferable lesson, and it is a Ch. 14 lesson, not a Ch. 4 one: the internal disagreement about what the brand was had not been resolved before the motion work went public. Motion did not cause the disagreement; motion made it undeniable, at maximum volume, to a global audience. ⚠ Expressive motion is a very efficient amplifier of whatever strategic clarity exists — including its absence. Do not use the audit and stakeholder work to skip the strategy argument. Use it to force the argument early, cheaply, in a room.
15. Constraint mapping: channels, platforms and pipelines
Motion is the only element of an identity system whose technical constraints routinely override its creative intent. Constraints must be mapped at diagnosis, because discovering them at production is how systems get quietly abandoned.
1. Rendering constraints — the cheap/expensive divide, enforced. The browser and OS rendering pipeline runs roughly JavaScript → style → layout → paint → composite. Animating properties that force layout recalculation — width, height, margin, top, left — repeatedly blocks the main thread, produces 💡 jank (dropped frames, visible stutter) and degrades responsiveness. Animating 💡 compositor-only properties — transform and opacity — skips layout and paint, is handed to the GPU compositor thread, and stays smooth even when the main thread is busy. ⚠ This has a direct brand consequence: the properties cheapest to render are the least ownable, and the most ownable are the most expensive (Ch. 7). Constraint mapping is where you decide, deliberately, which expensive properties you will pay for and where.
2. Responsiveness constraints — motion competes with interaction. Interaction responsiveness is now a measured, published web metric, and heavy main-thread animation degrades it directly: if the main thread is occupied animating, it cannot process the user's tap. Motion is therefore not free even when it looks smooth.
✔ Practical measures to specify at diagnosis:
- Compositor-only properties for anything high-frequency.
- Pause off-screen animation via intersection observation rather than letting it run unseen.
- Native CSS scroll-driven animation and view transitions where available, because these run on the compositor and free the main thread. As of mid-2026, scroll-driven animations have reached roughly 84–85% global browser support — stable in Chromium since v115 and in Safari since v26, but still behind a flag in stable Firefox — and cross-document view transitions sit at roughly 81%, stable in Chromium and Safari with partial support in Firefox from v144. ⚠ Treat both as progressive enhancement: gate them behind a feature query and specify the static fallback, or Firefox users get an unspecified experience.
- File-size discipline on vector animation formats: unused layers, embedded raster images and dense Bézier paths bloat JSON payloads; binary-packaged formats parse faster and ship smaller.
3. Device and physical constraints. Low-end and older devices are where motion damage concentrates, and they are invisible in median-device testing. Complex vector animation and non-composited CSS animation consume CPU and GPU, cause thermal throttling and drain battery. Reducing frame rate on mobile and simplifying paths are standard mitigations. ⚠ Specify your tenth-percentile device at diagnosis and test on it. Not the team's phones.
4. Pipeline and channel constraints.
| Channel | Hard constraints | ⚠ Kills motion systems by |
|---|---|---|
| Social feed | Muted autoplay; aspect-ratio variance; aggressive compression; partial viewport | Killing sound-dependent meaning; destroying fine detail and subtle gradients in compression |
| Broadcast / connected TV | Fixed frame rates; ⚠ mandatory PSE testing in the UK (Ch. 69); interlacing legacy; strict duration clocks | Late-stage PSE failure forcing re-edit and re-clearance |
| Product / app | Platform motion language; OS reduced-motion setting; performance budgets; engineering release cycles | Specs arriving in a format engineering cannot consume |
| Minimal animation support; GIF only, effectively | Producing an unavoidable static-fallback problem nobody specified | |
| Digital out-of-home | No sound; extreme viewing distance; brief dwell; sometimes non-standard ratios | Making detail and duration assumptions from desktop |
| Retail / physical screens | Long loops; ⚠ burn-in on some display types; unattended playback | Loops that fatigue viewers or damage hardware |
| Presentations / documents | Whatever the software supports; produced by non-designers | Being the largest volume producer of off-brand motion in the organisation, unmeasured |
Rendered-file model
- Motion lives in assets
- Governed by asset review
- Updates = re-render everything
- ✔ Broadcast, film, social
- ✘ Cannot respond to input at scale
Parameter model
- Motion lives in rules
- Governed by build pipeline
- Updates = change a value once
- ✔ Product, web, high-frequency
- ✘ Constrained by device
Text equivalent — architecture models
Choose rendered files, runtime parameters, or both — define the seam at diagnosis.
So what. Every hour of constraint mapping at diagnosis saves several at production. More importantly, it is the only point at which engineering can shape the system rather than veto it. ⚠ An engineering lead who first sees the motion system at handover will implement approximately the parts that are convenient.
16. Accessibility and reduced motion as a design input, not a retrofit
⚠ Read this before designing, not before launching. The reduced-motion state is part of the motion identity. Treated as compliance, it produces a broken brand and an exposed one.
Motion on screen can trigger dizziness, vertigo, nausea, headache and disorientation in people with vestibular disorders and motion sensitivities, and can seriously impede users with attention and cognitive differences. Parallax, scroll-jacking, large-surface movement and auto-advancing content are the highest-risk patterns. Separately, flashing content carries seizure risk for photosensitive users — a distinct hazard with distinct rules (Ch. 69).
The technical and legal baseline, as of 5 August 2026
| Instrument | Requirement | Status |
|---|---|---|
💡 prefers-reduced-motion — a CSS media query exposing the user's OS-level motion preference | Detect and honour: remove, simplify or slow non-essential motion | Widely supported; ✔ the primary implementation mechanism |
| WCAG 2.2.2 Pause, Stop, Hide (Level A) | Motion starting automatically, lasting over 5 seconds, presented alongside other content must be pausable, stoppable or hideable | Level A — the lowest bar, and legally in scope |
| WCAG 2.3.1 Three Flashes or Below (Level A) | No content flashing more than three times per second, or flashing below the general and red flash thresholds | Level A |
| WCAG 2.3.3 Animation from Interactions (Level AAA) | Motion animation triggered by interaction must be disableable unless essential | ⚠ Level AAA — not the legal floor |
| European Accessibility Act (Directive (EU) 2019/882) | Enforceable across all 27 member states since 28 June 2025 for a broad range of consumer-facing digital products and services; compliance route is EN 301 549, which incorporates WCAG 2.1 Level AA for web, mobile and software | In force |
| Ofcom Rule 2.12 (UK Broadcasting Code) | Broadcasters must minimise the risk to viewers with photosensitive epilepsy; flashing images and regular patterns exceeding specified luminance and frequency thresholds are prohibited | In force. UK broadcast advertising is cleared through Clearcast, which requires certification from approved 💡 Harding Test equipment — the standard automated PSE analysis — before transmission |
⚠ The gap that catches people out. The success criterion most directly about interaction-triggered motion — 2.3.3 — is Level AAA, so honouring prefers-reduced-motion is not strictly the minimum legal requirement under an AA-referenced regime. Many practitioners assume otherwise. Two reasons to implement it regardless: institutional procurement and enterprise agreements increasingly expect it; and the implementation cost is trivial relative to the harm and reputational exposure of ignoring it.
Tier 1 — Full
Tier 2 — Reduced
Tier 3 — Static
Text equivalent — three tiers
- Tier 1 — Full: Complete intended motion. Default when no preference is expressed.
- Tier 2 — Reduced: Keep opacity, colour, sequence and order. Remove parallax, large translation, overshoot.
- Tier 3 — Static: Single frame carries meaning when motion is unavailable.
⚠ The double-bind, named here and returned to in Ch. 70. There is no risk-free position. Ship expressive motion without a specified reduced state and you risk harming users, breaching accessibility expectations and generating complaints. Strip motion to a minimum and you lose distinctiveness, attribution and — in product contexts — the transient signal that prevents change blindness (Ch. 6), degrading usability for everyone. Both action and inaction carry penalties. The only defensible position is the specified-tiers approach above, documented, with the reduced state designed to the same standard as the full state.
✔ Also provide an in-product motion toggle. OS-level settings are under-discovered, and users who need reduced motion on your site may not have set a system preference.
17. ⭐ HARD GATE 1 — The motion problem statement
Everything upstream converges here. Nothing downstream should start without it. This is the first formal gate in the report, the cheapest to pass and the most expensive to skip.
| # | Component | ⚠ If omitted |
|---|---|---|
| 1 | The behavioural problem, in one sentence, evidenced from the audit | The project becomes a taste exercise with no falsifiable endpoint |
| 2 | Frequency split — the proportion of brand motion impressions that are expressive versus functional, with numbers from Ch. 10 | Budget goes to the wrong dialect; the brand's actual behaviour remains undesigned |
| 3 | Architecture decision — rendered-file, parameter, or both, with the seam defined (Ch. 15) | Two unreconciled systems; handover fails; engineering implements the convenient parts |
| 4 | The refusal list — category defaults you will not use (Ch. 13) | Convergence; you build an ⚠ AVOID-quadrant asset that cues a competitor |
| 5 | Constraint envelope — tenth-percentile device, performance budget, PSE requirement, disclosure requirement, three-tier accessibility commitment | Late-stage veto by engineering, legal or accessibility |
| 6 | Governance answer — who owns the rule after launch, who enforces it, through what mechanism, with what authority to refuse work | ⭐ The single largest cause of system decay (Ch. 51) |
| 7 | Success definition — the metric, the baseline measured now, and the review date | No baseline means no possible proof of value, which means no renewal of funding |
Template
The problem. [Brand] currently has no governed rule for how it behaves over time. Our audit of [n] motion instances across [n] touchpoints found [n] distinct easing behaviours and [n] distinct durations applied to the same core element, produced by [n] parties, none of whom broke a rule, because no rule existed.
The distribution. Approximately [x]% of brand motion impressions per person per year occur in functional interface contexts; [y]% in expressive brand contexts. Current design investment is approximately the inverse.
What we will build. A single root motion grammar — easing family, directional logic, choreographic order, sonic accent point — expressed in two dialects: expressive (>800ms, ≤[n] instances) and functional (100–300ms, tokenised, in [repository]). Delivered as [rendered assets] plus [motion tokens in DTCG-compatible format], with the seam at [defined boundary].
What we will not do. We will not use [refusal list]. We will not exceed [duration] on any interaction occurring more than [n] times per session. We will not ship any motion without a specified Tier 2 reduced state and Tier 3 static state.
Constraints. Tenth-percentile device: [device]. Compositor-only properties for all functional motion. Scroll-driven and view-transition techniques gated behind feature queries with specified fallbacks. UK broadcast assets require Harding Test PSE clearance before final delivery. AI-generated content requires visible disclosure and machine-readable marking per EU AI Act Article 50, enforceable since 2 August 2026.
Governance. [Named role] owns the grammar and holds authority to refuse non-compliant work. Enforcement mechanism: [token pipeline / review gate / template lockdown]. Review cadence: [frequency].
Success. By [date]: (a) unprompted attribution of the unbranded expressive asset among category buyers rises from [baseline, measured] to [target]; (b) easing variance across audited touchpoints falls from [n] behaviours to ≤3; (c) no regression in interaction responsiveness on the tenth-percentile device; (d) Tier 2 and Tier 3 states specified for 100% of shipped motion.
- [ ]Audit complete; frequency-weighted chart produced
- [ ]Variance chart produced
- [ ]Distinctive asset test run or gap acknowledged
- [ ]Category refusal list written
- [ ]Stakeholder 18-month question compared
- [ ]Constraint envelope agreed with engineering
- [ ]Accessibility three-tier commitment agreed
- [ ]Architecture decision made, seam defined
- [ ]Governance owner named, refusal authority granted
- [ ]Success metrics defined AND baselined
- [ ]Problem statement signed by brand, product, and engineering
Text equivalent — Gate 1 checklist — Ch. 17
- Audit complete; frequency-weighted chart produced
- Variance chart produced
- Distinctive asset test run or gap acknowledged
- Category refusal list written
- Stakeholder 18-month question compared
- Constraint envelope agreed with engineering
- Accessibility three-tier commitment agreed
- Architecture decision made, seam defined
- Governance owner named, refusal authority granted
- Success metrics defined AND baselined
- Problem statement signed by brand, product, and engineering
Part V — Scale, Tokenisation and Migration
Chapters 43–56. Everything in Parts III and IV assumed one brand, one grammar, one team. Part V is what happens when that assumption breaks — and how to move from one state to another without destroying what you built.
Case card — Kestrel Rail
Context
Facts
- • 900 platform screens running motion inherited from a 2011 hardware vendor: owned by nobody, never assessed for photosensitivity, seen ~420 times/year by every regular passenger
- • 340 regional marketing assets/year; 62% required central rework before the project
- • An ident seen ~6 times/year per person had absorbed €140k over two years; transitions seen ~1,100 times/year had absorbed nothing
- • 44 motion proposals reviewed against the purpose test (Ch. 23); 31 cut
- • Curve-based tokens throughout, with ONE documented spring exception (ticket-wallet swipe), registered with a rationale and a sunset date
Text equivalent — Kestrel Rail case card
Regional rail operator. Multi-market, multi-substrate. Fictional recap of Ch. 35.
- 900 platform screens; ~420 views/year per regular passenger
- 340 regional assets/year; 62% required central rework
- Ident ~6 views/year absorbed €140k; transitions ~1,100/year absorbed nothing
- 44 proposals reviewed; 31 cut on purpose test
- Curve-based tokens; one registered spring exception
43. When there is more than one: brands, platforms and markets
Multiplicity arrives in four forms, and each has a different correct answer. Organisations routinely apply the answer for one form to a different form and produce a system nobody can use.
| Form of multiplicity | The question | ⚠ The wrong instinct |
|---|---|---|
| Multiple brands (house of brands, portfolio) | How much motion do the brands share? | Sharing everything, which erases the portfolio's reason to exist |
| Multiple platforms (iOS, Android, web, broadcast, physical) | How much does the grammar bend to platform convention? | Refusing to bend, producing motion that feels wrong on every platform equally |
| Multiple markets (regional, cultural, regulatory) | What can regions change? | Either total lockdown, which produces quiet non-compliance, or total freedom, which produces nothing |
| Multiple products (a suite under one brand) | Where does the shared system end and product-specific motion begin? | Building one system for the flagship and letting the rest default |
For every form, the same structural question: which layers of the grammar are shared, and which are local?
L1 Easing family
L2 Choreographic order & stagger
L3 Duration scale
L4 Directional logic
L5 Accent point & sonic
L6 Transition patterns
L7 Subject matter, imagery, tone
Text equivalent — shared layers
- L1 Easing family — share almost always
- L2 Choreographic order & stagger — share usually
- L3 Duration scale — share often
- L4 Directional logic — share sometimes
- L5 Accent point & sonic — share for sub-brands
- L6 Transition patterns — rarely shared
- L7 Subject matter, imagery, tone — never shared
⭐ The insight that resolves most multi-brand arguments: sharing L1 and L2 alone produces a perceptible family resemblance (Gestalt common fate, Ch. 6) at zero rendering cost, zero local-freedom cost, and full survival under reduced motion. Two brands in a portfolio that share nothing but an easing curve and a stagger interval will read as related. Two brands that share transition patterns and imagery but use different curves will not.
This is close to a free lunch and it is almost never exploited, because portfolio motion decisions are usually made at L6 and L7 — the layers where sharing is both hardest and least effective. (Fourth of the four convergent arguments in Ch. 8.)
The platform-bend rule
⚠ A grammar that refuses to bend to platform convention produces motion that is equally wrong everywhere. A grammar that bends completely produces no brand at all.
✔ The workable rule: bend on mechanism, hold on character.
| Bend (platform-specific) | Hold (invariant) |
|---|---|
| Which transition pattern is used for navigation | The easing curve applied to it |
| Whether motion is spring-driven or duration-driven | Whether overshoot is permitted |
| Gesture velocity inheritance (Ch. 26) | The choreographic order |
| Platform-native back/dismiss behaviour | The accent point |
| Frame rate and rendering approach | The stagger interval |
Worked example. A brand's grammar specifies vertical-axis arrivals. On iOS, sheet presentation is natively vertical — no conflict. On a broadcast on-screen package, "vertical arrival" is meaningless in a lower-third that slides horizontally by convention. The bend: the lower third may enter laterally. The hold: it uses the entrance curve, the 50ms stagger, and lands its accent on settle. ⚠ Documented as a platform exception in the non-compliance register (Ch. 42), dated, with a stated rationale — not silently permitted.
44. Motion tokens: the mechanism that makes motion enforceable
This is the chapter that converts everything upstream from documentation into governance.
💡 Design token — a named value stored in a shared, machine-readable file, referenced by name rather than repeated as a literal value, and consumed by both design tools and production code.
The point is not the file. The point is that the value exists in exactly one place. Change it once, and every consumer changes. A duration written as 240ms in forty places is forty decisions. A duration written as duration.functional.medium in forty places is one decision, referenced forty times.
Prose guideline
“Use 240ms for medium transitions” → human remembers approximately, types 250 or 300.
Token
duration.functional.medium = 240ms → build consumes it; non-reference is CI failure.
Text equivalent — prose vs token
Tokens make compliance structural; prose decays monotonically.
What the standard covers, as of August 2026
The W3C Design Tokens Community Group published its first stable specification, version 2025.10, on 28 October 2025. It establishes a vendor-neutral JSON format and is supported by major design tooling and token pipelines.
⚠ Adoption figures circulating in 2026 — including a widely-repeated claim of roughly 84% of design teams — are, single-sourced and not independently verified. The specification's existence and stability are; its penetration is not.
Motion types with first-class support:
| Type | What it holds | Example |
|---|---|---|
duration | A length of time | {"$type": "duration", "$value": {"value": 240, "unit": "ms"}} |
cubicBezier | An easing curve as four control values | {"$type": "cubicBezier", "$value": [0.15, 0.85, 0.25, 1]} |
transition | ⭐ A composite type combining duration, delay and timing function into one reusable token | Bundles the three decisions that always travel together |
⭐ The composite transition type is the most under-used feature in the specification. Most teams tokenise durations and curves separately, then re-pair them by hand at every use site — which reintroduces exactly the judgement the token system was meant to remove. A transition token encodes the pairing, which is where the grammar actually lives.
A worked token file
{
"duration": {
"functional": {
"short": { "$type": "duration", "$value": { "value": 160, "unit": "ms" } },
"medium": { "$type": "duration", "$value": { "value": 220, "unit": "ms" } },
"long": { "$type": "duration", "$value": { "value": 300, "unit": "ms" } }
},
"expressive": {
"short": { "$type": "duration", "$value": { "value": 900, "unit": "ms" } }
},
"instant": { "$type": "duration", "$value": { "value": 0, "unit": "ms" } }
},
"easing": {
"entrance": { "$type": "cubicBezier", "$value": [0.15, 0.85, 0.25, 1] },
"exit": { "$type": "cubicBezier", "$value": [0.60, 0.00, 0.90, 0] }
},
"motion": {
"enter": {
"$type": "transition",
"$value": {
"duration": "{duration.functional.medium}",
"delay": "{duration.instant}",
"timingFunction": "{easing.entrance}"
}
},
"leave": {
"$type": "transition",
"$value": {
"duration": "{duration.functional.short}",
"delay": "{duration.instant}",
"timingFunction": "{easing.exit}"
}
}
},
"stagger": {
"default": { "$type": "duration", "$value": { "value": 50, "unit": "ms" } }
}
}
⚠ Note the exit duration. leave references functional.short while enter references functional.medium — the Ch. 8 heuristic that exits are faster than entrances, encoded structurally rather than remembered. This is what it means for a grammar to be enforceable: the rule is in the file, not in someone's head.
The two tokens nobody creates
✔ duration.instant (0ms). Sounds absurd; it is essential. It gives the reduced-motion tier and the interrupt case a named reference rather than a hard-coded zero. Tier 2 becomes a token override rather than a code branch.
✔ stagger.default. Choreography is half the brand signature (Ch. 30) and is almost never tokenised, which means it is almost never enforced. A stagger interval that lives only in prose reverts to whatever feels right.
45. ⭐ Where tokenisation breaks: the spring problem
The most consequential technical-governance gap in the discipline as of August 2026, and one that most motion practitioners have not yet had to confront.
What platforms do
- Spring physics
- Shape morphing
- Gesture velocity
What standard governs
- duration ✔
- cubicBezier ✔
- transition ✔
- springs ✘
Text equivalent — governance gap
Gap between platform motion models and token specification — hybrid curve + spring exceptions recommended.
⚠ Two things have moved in 2026, and both matter for how you architect.
First, the gap is under active work rather than dormant: community discussion on choreography-level motion token types has produced a proposed spring type carrying bounce, duration and a physics block of stiffness, damping and mass, alongside proposals for a keyframes or timeline node that would map cleanly onto CSS @keyframes and vector-animation exports. Nothing is ratified.
Second, and more immediately useful: tooling has settled on a workaround. Design tools now export spring motion by baking it down — sampling the physics into a linear() easing function with many stops, producing a portable, deterministic approximation for environments that cannot compute springs. ⚠ A baked spring is not a spring. It reproduces the shape of the motion but loses the two properties springs exist for: mid-flight interruptibility and gesture-velocity inheritance. It is a governance instrument, not a motion model.
Four responses, honestly compared
| Response | What you do | ✔ Gains | ⚠ Costs |
|---|---|---|---|
| 1. Curve-only grammar | Refuse springs. Specify everything as duration + cubicBezier | Fully enforceable. Portable across platforms. Reviewable as numbers | ✘ No gesture-velocity inheritance, a genuine usability deficit on gesture surfaces (Ch. 26). Feels dated against platform-native motion |
2. Springs via $extensions | Tokenise spring parameters as custom extensions in the token file | Values live in one place; partially traceable | ⚠ Non-standard, so tooling support is inconsistent. Springs behave differently across runtimes, so the same values produce different motion on different platforms. Not truly enforceable |
| 3. Hybrid by dialect ⭐ | Curve-and-duration tokens for the functional dialect; springs permitted only on documented gesture surfaces, each an explicit registered exception. Bake springs to linear() for any non-gesture surface that needs the same character | Enforceable where enforcement matters most, at high frequency. Velocity inheritance retained where it is genuinely required. The baked curve carries the character into environments that cannot run physics | Two specification models to maintain. ⚠ Requires discipline to stop the exception list growing |
| 4. Springs throughout, prose governance | Full physics model, governed by documentation and review | Contemporary. Best gesture feel | ⚠ Unenforceable. Reverts to Ch. 19's judgement model. Variance grows with headcount. Not recommended above one team |
⭐ Recommendation: response 3. Kestrel took it — curve-based tokens throughout, with one documented spring exception for the ticket-wallet swipe. The exception was written into the non-compliance register with a rationale and a sunset date, so it is a decision rather than a precedent.
⚠ What to watch. If the specification gains a first-class spring type, response 1 becomes unnecessarily restrictive and response 3's exception list can be regularised. Do not architect on the assumption that this gap is permanent — but do not architect on the assumption it will close either. Review annually.
The deeper point
This gap is a specific instance of a general pattern worth naming: the enforceable subset of a motion language is always smaller than the expressible subset. Everything outside the enforceable subset is governed by prose, and prose decays.
When you design a grammar, know which of its four components (Ch. 30) sit inside the enforceable subset. Easing curves and durations do. Choreographic stagger does, if you tokenise it. Directional logic and accent point do not — they are governed by specification and review, permanently.
✔ Practical consequence: load as much of your brand's distinctiveness as possible into the enforceable subset. Third of the four convergent arguments in Ch. 8.
46. Decision trees for structural choices
Four decisions that recur, resolved as trees rather than debated as opinions.
Tree 1 — Should this exist?
No
Yes
Yes
No
Yes
No
No
Yes
Yes
No
Yes
No
Tree 2 — Which dialect?
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Tree 3 — Rendered file or runtime?
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Tree 4 — Can a region change this?
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Yes
No
Text equivalent — decision trees
Four trees: existence/restraint gate, dialect by frequency, rendered vs runtime, regional change with fixed-layer refusal.
⚠ Tree 4's asymmetry is deliberate and it is the whole governance strategy. Refusing a fixed-layer change is defensible precisely because the variable layer is genuinely generous. A governance model that refuses everything gets circumvented. A governance model that refuses a short, principled, published list and approves freely outside it gets complied with.
47. Roles, prioritisation and resource allocation
| Role | Does what | ⚠ Where it usually sits, wrongly |
|---|---|---|
| Motion owner | Holds the grammar. Refuses non-compliant work. Arbitrates exceptions | ⚠ Usually nobody. The single most consequential vacancy in the discipline |
| Motion designer | Produces expressive work; writes specifications | Studio or in-house creative. Usually present |
| Motion engineer (or a product engineer with the remit) | Implements the functional dialect; maintains the token pipeline; instruments performance | ⚠ Usually nobody, so tokens go unconsumed (Ch. 41) |
| Producer / operator | Makes the volume: 200+ assets a year from templates | ⚠ Usually present, never consulted during design (Ch. 14) |
⭐ Of the four, the two most commonly missing — owner and engineer — are the two that determine whether the system survives. A project that funds two designers and no owner and no engineer has funded artefacts, not a system.
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Text equivalent — prioritisation
- Highest-frequency functional instances with zero specification
- Safety- or compliance-exposed instances
- The endframe
- Templates for highest-volume producers
- Remaining functional instances by frequency
- Expressive hero work (usually fifth or sixth, not first)
⚠ This sequence is politically difficult and it is correct. The hero film is what the CMO wants and what wins the pitch. Delivering it last is rarely possible. The workable compromise: deliver it in parallel, not first, and let it fund the rest — Ch. 14's honest advice about serving each stakeholder's real motive.
Allocation heuristics ◇
| Heuristic | The rule |
|---|---|
| Pre-production share | Scripting, storyboarding and specification typically consume 20–30% of a motion project's cost; locking them early prevents far more expensive mid-production change |
| Revision reality | Most studio quotes include two revision rounds; open-ended feedback loops are the largest single source of budget overrun |
| Shot count over duration | Ten one-second cuts cost considerably more than one ten-second shot. ⚠ Cut count, not runtime, is the cost driver |
| The invisible internal half | Audits routinely find 40–60% of true motion cost is internal labour that no budget line records |
| The system/production split | A brand at Level 1–2 maturity (Ch. 20) should expect to spend materially more on specification and tokenisation than on rendered assets in year one. ⚠ This inverts the normal ratio and must be argued for explicitly |
Indicative market rates, August 2026 ◇
⚠ Compiled from market surveys and rate guides. Wide variance by region and specialism, and unverified. Order-of-magnitude planning only, and the fastest-dating table in this report.
| Item | Indicative range |
|---|---|
| Senior freelance motion designer, day rate (US market) | $650–$1,200 |
| Broadcast / title design specialist, day rate | $800–$1,500 |
| Real-time engine specialist (Unreal and similar), day rate | $1,000–$2,000+ |
| Motion graphics, per finished minute | $1,000–$15,000 |
| 3D animation, per finished minute | $5,000–$50,000+ |
| Motion guidelines as an add-on to an existing identity | $500–$2,000 |
| Mid-range brand identity including basic motion guidelines | $5,000–$15,000 |
| Comprehensive motion system with tokens and developer handoff specs | $15,000–$50,000+ |
⚠ Note the striking implication of the last three rows: the market prices a full motion system at roughly the cost of one minute of premium 3D animation. That is either the best-value item in the identity budget or evidence that the market has not yet learned to price systems. Probably both.
48. The pathologies of scale
Six failure modes that emerge only at scale. Each has a diagnostic tell and a specific fix, and each is invisible while a system is small.
| Pathology | What it is | Diagnostic tell | ✔ Fix |
|---|---|---|---|
| Drift | Slow, unintentional divergence from the grammar. No single violation is significant | Year-on-year variance chart (Ch. 10) shows growth. Nobody can name a moment it changed | Pipeline enforcement (Ch. 44). ⚠ Social enforcement cannot stop drift; it only slows it |
| Bloat | Token and spec counts grow monotonically. Eleven curves where three were specified | Token file has more easing values than the grammar permits | Ch. 49. ⚠ Requires deletion authority, which is a governance property, not a design one |
| Duplication | Two teams independently specify the same behaviour under different names | Two tokens with identical values and different names | Single source of truth; automated duplicate detection in the pipeline |
| Self-competition | Sub-brands or products develop distinctive motion that competes with the parent for attribution | Distinctive-asset testing attributes the motion to the sub-brand and not the parent | Ch. 43's shared-layer decision, made deliberately rather than by default |
| Ossification | ⚠ The opposite pathology, and the one mature systems die of. The system becomes unchangeable; innovation happens outside it | Teams shipping motion that bypasses the system entirely, and being right to | Ch. 50. Scheduled review, funded change budget, a legitimate exception path |
| Orphaning | Instances whose owner left, whose source files are unretrievable, whose rationale is lost | Matrix rows with no owner (Ch. 38). Assets nobody can edit | ⚠ Ownership column enforced as a release condition; source-file retrievability audited |
DRIFT ◄──────── HEALTHY BAND ────────► OSSIFICATION
Variance grows vs variance = 0 and circumvention
Text equivalent — drift and ossification
Organisations oscillate between drift crackdowns and ossification unless governance dampens the cycle.
⚠ Orphaning is the pathology with the longest tail. Kestrel's departure-board animation was orphaned for over a decade: inherited from a 2011 hardware vendor, owned by nobody, unassessed for safety, seen 420 times a year by every regular passenger. Orphaned motion is not merely off-brand. It is unassessed risk with a brand's name on it.
49. ⭐ SUBTRACTION: pruning a motion system
Every motion system grows. Almost none are pruned. Subtraction is the least-practised discipline in the field and the one that most reliably improves a mature system.
| Growth pressure | Why nothing counteracts it |
|---|---|
| Every new component needs motion | Adding is a design task; removing requires authority |
| Every exception becomes a precedent | Precedents have no expiry unless one is written (Ch. 42) |
| New platforms add patterns | Old platform patterns are never retired |
| Personnel change adds preferences | Departing staff's decisions outlive their rationale |
| ⚠ Deletion has no advocate | Nobody is promoted for removing a token |
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Text equivalent — subtraction
- Unreferenced tokens — start here, zero risk
- Duplicate values — consolidate
- Curves beyond grammar — count extras
- Motion failing purpose test — run restraint gate
- Motion over duration band — reduce not delete
- Expired exceptions — register with dates
- Redundant expressive assets — last and hardest
⚠ What must never be subtracted
The fixed layer (Ch. 34): easing family, accent point, choreographic order, stagger interval, sonic signature, endframe lock-up.
Subtraction pressure falls disproportionately on the fixed layer, because the fixed layer is the boring part — and it is boring by design, because distinctive assets accumulate through unchanged repetition. A rationalisation exercise led by someone who has not read Ch. 34 will helpfully remove the brand.
✔ Governance device: mark the fixed layer as protected in the token file and in the matrix, with a named approver required for any change. It takes ten minutes and prevents a category of well-intentioned destruction.
The subtraction audit, run annually
| Metric | How to compute | Target direction |
|---|---|---|
| Unreferenced token count | Automated scan of consumers against the token file | → 0 |
| Distinct easing curves in production | Count in code, not in the document | → the grammar's number |
| Instances with no stated purpose | Matrix query | → 0 |
| Instances above their purpose's duration band | Matrix query | → 0 |
| Open exceptions past their sunset date | Register query | → 0 |
| ⭐ Impression coverage (Ch. 38) | Σ frequency of specified / Σ frequency of all | → 100% |
⚠ Note that subtraction and coverage move in opposite directions and both must improve. Cutting instances raises the risk of coverage falling. The goal is a smaller system covering a larger share of impressions. That combination is the signature of a maturing system, and it is measurable.
50. ⭐ TRANSITION AND MIGRATION CRAFT
The most under-documented chapter in this field, and the most valuable. Almost everything published about brand motion describes arriving at a new system. Almost nothing describes leaving an old one — and the leaving is where systems break, budgets die and brands spend eighteen months looking like two brands.
⚠ Sourcing note, stated plainly. Generic rebrand-rollout phasing is well documented. Motion-specific migration is not: there is no published, evidenced methodology for retiring an easing family, dual-running two motion grammars, or sunsetting an ident across broadcast and product simultaneously. What follows is synthesis and reasoning from first principles, plus transferable structure from general rebrand practice. It is the most useful chapter in this report and the least externally validated. Treat it as a strong starting framework to adapt, not as citable evidence.
Why motion migration is harder than static migration
| Static asset migration | ⚠ Motion migration |
|---|---|
| A logo is replaced. The old one is gone | Motion lives in code, in rendered files, in templates, and in hardware. Four substrates, four different replacement mechanisms |
| Replacement is binary and visible | ⚠ Partial replacement is invisible. A product can have new tokens and old hard-coded values simultaneously, and look almost right |
| Old assets can be recalled | ⚠ Rendered motion assets persist indefinitely in third-party ad systems, partner platforms, archived campaigns and hardware that cannot be updated |
| Cost is reprinting | Cost is engineering time, re-rendering, re-clearance (⚠ broadcast assets need fresh Harding Test PSE clearance, Ch. 69), and re-recording sonic accents |
| No performance implication | ⚠ The new system may perform differently on the tenth-percentile device, so migration can regress the product |
| Nobody can partially comply | ⚠ Partial compliance is the normal state for months, and it must be designed |
⭐ The core migration insight: motion migration is not a replacement, it is a period of deliberate coexistence. Plan the coexistence. The alternative is not a fast switch — it is an accidental, undocumented, indefinite coexistence, which is what most brands actually experience.
Inventory & retrievability
Dual-run preparation
Migrate by frequency
Sunset old system
Delete & document
Text equivalent — migration phases
- Inventory & retrievability: Behaviour matrix; substrate classification
- Dual-run preparation: New tokens alongside old; coexistence rules
- Migrate by frequency: Highest impressions first; tenth-percentile test per batch
- Sunset old system: Deprecated tokens with dated sunsets per substrate
- Delete & document: Subtraction audit clean; permanent exceptions registered
Substrate classification: the step that determines everything
⚠ Migration sequencing must be by substrate, not by touchpoint or by team. Each substrate has a different replacement mechanism, a different cost and a different achievable timeline. Mixing them into one plan produces a plan that is wrong for every substrate.
| Substrate | Replacement mechanism | Realistic timeline | ⚠ Migration risk |
|---|---|---|---|
| Tokenised runtime motion | Change a value | Days per release | ⭐ Lowest. This is why tokenisation is a migration investment, not only a governance one |
| Hard-coded runtime motion | Engineering refactor | Quarters | Requires engineering capacity that competes with features. ⚠ The commonest migration blocker |
| Templates | Rebuild and redistribute | Weeks | ⚠ Old template copies persist on local machines indefinitely |
| Rendered assets in owned channels | Re-render and replace | Weeks–months | Cost scales with volume |
| Rendered assets in third-party systems | Request replacement | ⚠ Months, sometimes never | Ad servers, partner platforms, aggregators, archived campaigns |
| Broadcast masters | Re-render, re-clear | Months | ⚠ Requires fresh PSE clearance (Ch. 69) and re-versioning to duration clocks |
| Sonic assets | Re-record or re-edit | Months | ⚠ If the accent point moves, the sound must move; if the sound is licensed, rights renegotiation |
| Hardware-embedded motion | Firmware, or hardware replacement | Years, or never | ⚠ Kestrel's 2011 platform screens. Often the highest-impression substrate and the least migratable |
⭐ The uncomfortable structural finding this produces: the highest-impression substrates are frequently the least migratable. Which means impression coverage of the new system may lag the launch by years, while the brand publicly claims a completed rebrand. Plan for it and say so internally, or be surprised by it and deny it externally.
Rule 1
Rule 2
Rule 3
Rule 4
Rule 5
Rule 6
Text equivalent — coexistence rules
- New work uses the new system — no exceptions
- Existing work untouched unless already changing
- Never mix systems within one screen or asset
- Endframe migrates first, everywhere
- If in doubt, use new system and log the gap
- One named person arbitrates within 24 hours
Sequencing: three strategies compared
| Strategy | How | ✔ When it's right | ⚠ Failure mode |
|---|---|---|---|
| Big bang | Everything switches on one date | Small estate; single substrate; strong external launch requirement | ⚠ Almost never achievable in motion, because hardware and third-party substrates cannot comply. Produces a public claim of completion that is false, and a long undocumented tail |
| Frequency-first ⭐ | Highest-impression instances first, regardless of visibility | Most brands. Maximises perceived change per unit of effort | Leadership sees little for months, because high-frequency instances are unglamorous. ⚠ Requires the Ch. 10 chart to defend the sequence |
| Substrate-first | Complete each substrate before starting the next | Estates dominated by one difficult substrate | Slow to show cross-channel coherence; a fully-migrated product alongside a fully-old broadcast package reads as inconsistent |
✔ Recommended hybrid, and it is what mature teams converge on: endframe everywhere first (rule 4), then frequency-first within the tokenised and template substrates, then substrate-first for the hard cases, with dated sunsets per substrate and a permanent exception register for the unmigratable.
Migration KPIs
| KPI | Definition | ⚠ Note |
|---|---|---|
| Impression coverage of the new system | Σ frequency of migrated instances / Σ frequency of all | ⭐ The only KPI that reflects what audiences experience. Report this one to leadership |
| Row coverage | Migrated rows / total rows | Flatters. Use internally only |
| Deprecated-token reference count | Automated scan | → 0. Must hit zero for one full release cycle before deletion |
| New references to deprecated tokens | Automated scan, per release | ⚠ Any non-zero value means the coexistence rules are not being followed. Investigate the cause, not the instance |
| Substrates past sunset date | Register query | → 0, or moved to permanent exception with rationale |
| Responsiveness on tenth-percentile device | Instrumented | ⚠ Must not regress. A migration that degrades the product will be reverted, correctly |
| Producer rework rate | Assets needing central correction | ⭐ Should rise early in dual-run then fall below pre-migration baseline. A rise that never falls means the new system is harder to comply with than the old one |
⚠ The three migration failures to expect
1. The stalled dual-run. Phase 1 completes, Phase 2 begins, and then feature work reclaims engineering capacity. The brand runs two motion systems indefinitely. Prevention: coexistence rule 2 — migration rides on planned work — plus dated substrate sunsets with a named owner. Standalone migration backlogs do not survive two quarters.
2. The declared-complete migration. Launch happens, press coverage is positive, leadership declares completion, and 60% of impressions are still on the old system because they live in hardware and third-party substrates. Prevention: report impression coverage, not row coverage, from day one. ⚠ This failure is near-universal and mostly a measurement artefact.
3. The migration that regressed the product. New grammar is more expensive to render; responsiveness drops on low-end devices; engineering removes the motion wholesale rather than tuning it. Prevention: Ch. 33's device test per migration batch, not once at design time.
⭐ What makes motion migration succeed, in one sentence: migrate the enforceable subset first, ride planned work, sunset by substrate with dates, and measure by impressions. Every failure above is a violation of one of those four clauses.
51. Governance models
Four models. The choice should match organisational reality, not aspiration.
| Model | Structure | ✔ Right when | ⚠ Fails by |
|---|---|---|---|
| Central authority | One owner approves all motion | Small estate; strong central brand function | Becoming a bottleneck; regions circumvent; ossification (Ch. 48) |
| Federated with a locked core ⭐ | Centre owns the fixed layer and the token pipeline; regions and products own the variable layer freely | Most multi-market, multi-product brands | Requiring the fixed/variable line to be genuinely published and genuinely short (Ch. 34) |
| Pipeline-enforced | Compliance is automated; humans review only exceptions | Product-dominant organisations with engineering maturity | Governing only the enforceable subset (Ch. 45); expressive work drifts unnoticed |
| Community of practice | No authority; shared norms, regular forums | Small organisations; genuinely collaborative cultures | ⚠ Cannot stop drift. Degrades as headcount grows (Ch. 19) |
Pipeline
Template lock
Review
Text equivalent — enforcement ladder
- Pipeline: Non-compliance fails a build. Most durable.
- Template lock: Non-compliance not producible. Bypassable by new files.
- Review: Human notices and refuses. Decays under deadline pressure.
⚠ The governance rule that follows: for anything that matters, move enforcement up this ladder. Anything governed only by review will drift — not because reviewers are weak, but because review is a human process competing with deadlines, and deadlines win at a predictable rate.
The exception path is a governance feature, not a failure
⚠ A governance model with no legitimate exception path does not produce compliance. It produces undocumented non-compliance, which is strictly worse: the same divergence, minus the visibility.
| Requirement | Why |
|---|---|
| Written request, one paragraph | Forces articulation; filters casual requests |
| Decision within a stated window (48 hours to 1 week) | ⚠ Slow decisions get answered by invention |
| Decided by the named owner, not a committee | Committees refuse by default and slowly |
| ⭐ Every approval carries a sunset date | Without a date, every exception is permanent |
| Logged in a public register | Makes the register the honest picture of the estate |
| Fixed-layer requests are refused, always | The one absolute. Predictability makes refusal defensible |
⭐ The register is the single most useful governance artefact in this report, and it is the one almost nobody keeps. It is simultaneously the compliance picture, the migration backlog, the technical-debt list and the evidence for next year's funding request.
52. ⭐ HARD GATE 3 — Governance in force
Passed when governance is operating, not when it is designed.
- [ ]Named owner in post with written refusal authority
- [ ]Fixed/variable card published
- [ ]Pipeline enforcement live for enforceable subset
- [ ]Templates locked; non-designer test passed
- [ ]Lookup test passing across estate
- [ ]Exception path published with decision window
- [ ]Exception register open with dated sunsets
- [ ]Subtraction audit scheduled and funded
- [ ]Impression coverage reported to leadership
Text equivalent — Gate 3 checklist — Ch. 52
- Named owner in post with written refusal authority
- Fixed/variable card published
- Pipeline enforcement live for enforceable subset
- Templates locked; non-designer test passed
- Lookup test passing across estate
- Exception path published with decision window
- Exception register open with dated sunsets
- Subtraction audit scheduled and funded
- Impression coverage reported to leadership
⚠ The gate's sharpest test: ask when the owner last refused a piece of work, and ask what happened next. If the refusal was overturned by someone more senior without going through the exception path, governance does not exist — the org chart governs motion, and it will produce exactly the drift the system was built to prevent.
53. In-house or outsourced: scaling motion capability
⚠ Sourcing note. The three-model structure below adapts team topologies documented in design-system practice, where the distinction between solitary, centralised and federated models is well established. The dialect-based insourcing rule, the hiring sequence and the failure modes are this report's synthesis.
Most organisations treat "should motion be in-house?" as a cost question, answer it with a rate comparison, and get it wrong. It is a frequency question, governed by the same variable as everything else in this report.
⭐ The rule: insource by dialect, not by discipline
| Functional dialect | Expressive dialect | |
|---|---|---|
| Cadence | Continuous. Every release, every new component | Episodic. Campaigns, launches, refreshes |
| Coupled to | Product release cycles | Marketing calendar |
| Needs | Engineering integration, token pipeline access, CI presence | Craft ceiling, outside perspective, surge capacity |
| Dominant mode (Ch. 19) | Lookup | Judgement |
| Verdict | ✔ In-house, almost always | ✔ Outsourceable, often correctly |
⭐ The last row is the argument. In-house structures are lookup machines: they accumulate precedent, maintain repositories, and get better at not re-deciding. Studios are judgement machines: they are hired for the decision, not the retrieval. Matching the work to the mode is the whole of this chapter.
⚠ The common failure is the inverse arrangement — an external studio maintaining interface motion it cannot instrument, and an internal team producing expressive work at a craft ceiling the brand has outgrown.
The four models
| Model | Structure | ✔ Right when | ⚠ Fails by |
|---|---|---|---|
| No studio | All motion commissioned externally | Small estate; low volume; no product surface | Governance exists only by contract (Ch. 54). Highest-drift arrangement available |
| Embedded | Motion capability sits inside product teams | Product-dominant organisations; strong token pipeline | Consistency across teams, unless the grammar is genuinely enforced. Each team drifts locally |
| Central studio | All motion requests route through one team | Mid-size estate; strong central brand function | Becoming a bottleneck. ⚠ Then teams route around it, which reads as drift |
| Hybrid ⭐ | Centre owns grammar, tokens and enforcement; practitioners embedded in product teams; external studio for expressive peaks | Most organisations past a single product | Requires the fixed/variable line to be published and short (Ch. 34). Maps directly onto Ch. 51's federated model |
The hiring sequence, and why it surprises people
MOTION OWNER
MOTION ENGINEER
PRODUCER / OPERATOR
MOTION DESIGNER
⚠ NOTE THE ORDER. Most organisations hire a motion designer first, because that is the visible craft role, and then have nobody to govern, implement or operate what the designer produces. The designer is the only one of the four the market will sell you without being asked.
Text equivalent — trigger-based hiring order
- MOTION OWNER: trigger: a grammar exists. Fractional is fine. Without it, nothing below matters — the grammar decays faster than it is applied (Ch. 51).
- MOTION ENGINEER: trigger: tokens exist but are not consumed. ⭐ The most commonly skipped hire and the one that decides whether Gate 2 can pass at all (Ch. 42).
- PRODUCER / OPERATOR: trigger: template volume exceeds ad-hoc. Cheapest variance reduction available (Ch. 47).
- MOTION DESIGNER: trigger: expressive volume exceeds studio economics.
Most organisations hire the motion designer first and have nobody to govern, implement or operate.
⚠ The craft-ceiling problem, and why full insourcing is rarely correct
An in-house studio's craft ceiling is set by its most senior practitioner, and in-house practice develops more slowly than studio practice because the variety of work is narrower. Over a few years, fully-insourced expressive work tends to regress toward competence: reliably on-brand, reliably unremarkable.
✔ The defensible position at most scales is to insource the functional dialect completely and retain a studio relationship for expressive peaks — not because internal people are less able, but because the two dialects reward different working conditions.
Three failure modes
| Failure | The tell | ✔ Fix |
|---|---|---|
| The service desk | The team measures itself on throughput and ticket closure. Nobody has refused anything | ⚠ Governance has collapsed into production. Separate the owner role from the delivery function (Ch. 52) |
| The bottleneck | Lead times lengthen; teams begin producing motion outside the system and are right to | Move enforcement up Ch. 51's ladder so that compliance stops requiring the central team's attention |
| Ceiling regression | Expressive work is compliant and forgettable; the annual attribution test flatlines (Ch. 59) | Reintroduce external craft on expressive peaks. ⚠ This is a capability decision, not a performance-management one |
54. ⭐ Onboarding third-party producers
⚠ Sourcing note, stated plainly. As with Ch. 50, there is no published methodology for this. What follows is synthesis from practice and from the governance logic established in Ch. 51. Treat it as a working framework to adapt.
⭐ The structural problem, stated once
External suppliers can only be governed by contract and review. That is mechanism 3 on Ch. 51's durability ladder — the weakest one, the one that decays with deadline pressure. Pipeline enforcement is unavailable, because the supplier does not build in your repository. Template lock is partially available at best.
Now note what external suppliers usually produce: the expressive dialect, at volume, on the highest-visibility surfaces.
⚠ External supply is therefore structurally the highest-drift channel in the estate, and it is producing the assets the brand is judged on. No amount of relationship management changes the mechanism. What changes it is converting governance from something exercised at delivery into something agreed at contracting.
| Internal production | External production | |
|---|---|---|
| Pipeline enforcement | ✔ Available | ✘ Unavailable |
| Template lock | ✔ Available | ◐ Partial |
| Review | ✔ Available | ✔ Available, and ⚠ commercially constrained |
| Consequence | Compliance can be structural | Compliance must be contractual |
The onboarding pack: send refusals first
⚠ The instinct is to send the grammar card and the brand guidelines. Both are necessary and neither is what a supplier most needs. A supplier's operative question is not what does this brand do? but what will get this work rejected?
| Order | What you send | Why this order |
|---|---|---|
| 1 | Category refusal list (Ch. 13) | Prevents the most expensive class of error — a beautifully executed asset that cues a competitor |
| 2 | Fixed/variable card (Ch. 34) | One page. Tells them where they are free, which is most places, and where they are not |
| 3 | Grammar card (Ch. 30) | The four components, with values |
| 4 | Acceptance criteria (below) | The contract's teeth, in plain language |
| 5 | Token file or specification extract | Whatever the enforceable subset can be handed over as (Ch. 45) |
| 6 | Reference assets | ⚠ Last, deliberately. Sent first, references become the spec and the written rules go unread |
Contracting for governance
Ch. 14 advises putting governance artefacts in the contract as named deliverables with acceptance criteria. This is what that means in practice.
| Criterion | Verifiability | ⚠ Note |
|---|---|---|
| Easing values match the specified curves | Machine-checkable | Measurable frame-by-frame. Non-negotiable |
| Durations sit within the purpose's band | Machine-checkable | Ch. 23 |
| Tier 2 and Tier 3 states delivered | Checkable | ⚠ Specify that Tier 2 is not "no animation" |
| Stagger interval as specified, not randomised | Checkable | Ch. 30 |
| Source files delivered in editable format, with fonts and assets | Checkable | ⭐ See below |
| Purpose named for each motion instance | Checkable | Feeds the matrix (Ch. 38) |
| Flash-safety clearance where the channel requires it | Checkable | Ch. 16 |
| "On brand" / "feels right" | ✘ Unverifiable | ⚠ Where every dispute originates. Remove it from the contract and replace it with Ch. 9's parameter table |
✔ The paid pilot. Commission one asset, run it through the full acceptance criteria, and resolve the disagreements before the main body of work is scheduled. It costs one asset and it surfaces every misreading of the pack while there is still time and goodwill to fix them.
⚠ Refusal authority when there is a commercial relationship
Refusing an internal team's work is uncomfortable. Refusing a supplier's work three days before a campaign launch, having already been invoiced, is frequently impossible — and everyone in the room knows it.
⭐ So refusal cannot be a judgement exercised at delivery. It has to be an acceptance criterion agreed at contracting. The distinction is the whole chapter: "this doesn't feel right" is a conversation the deadline wins, whereas "clause 4.2 specifies the entrance curve and this is not it" is a conversation the deadline does not enter.
⚠ If a supplier's non-compliant work ships because there was no time to fix it, log it in the exception register with a sunset date (Ch. 51). An undocumented pass becomes a precedent, and the next brief will be quoted against it.
Offboarding, which decides your migration cost
The most consequential clause in a motion supply contract is the one nobody negotiates.
⚠ Source-file delivery must be a contractual deliverable at commissioning, not a request at the end of the relationship. Requested afterwards, you are asking a supplier with no obligation, possibly no remaining licence to the assets, and possibly no copy of the file.
Ch. 48's orphaning pathology and Ch. 50's Phase 0 retrievability audit both terminate here. Every un-retrievable source file in an estate was once a commission where this clause was absent.
✔ Specify at contracting: editable source files with all layers intact; a manifest of fonts, licensed audio and third-party assets with their licence terms and expiry; and the parameter values as written specification, not only as rendered output. ⭐ That last item is what lets a future team migrate the asset instead of re-inventing it (Ch. 50).
Part VI — The Value Layer
Chapters 57–64. How value in motion is quantified, what the honest numbers are, and how to build a case that survives a finance review.
57. How motion value is actually quantified
⚠ Start with the uncomfortable truth, because the rest of this part depends on it being said. As of 5 August 2026, there is no published controlled study demonstrating that adopting a brand motion identity caused a commercial outcome. Studios publish process. Vendors publish effect sizes for adjacent things they sell. Nobody publishes counterfactuals.
Text equivalent — inference chain
- Distinctive assets aid mental availability
- Motion can function as distinctive asset (by analogy)
- Therefore motion aids mental availability (inference — not measured)
- Therefore motion produces commercial return (inference on inference)
✔ What to do with this. Do not pretend the gap is closed. Say it out loud, early, and then do the thing that actually solves it: measure your own brand. A measured baseline plus an annual re-test converts an industry-wide inference into a company-specific fact within eighteen months. That is available to any brand willing to spend a modest research budget, and it is worth more than every statistic in the field combined.
The four currencies motion is measured in
Motion has no single natural unit. Four are defensible, and most brands should use two or three.
| Currency | Measured as | ✔ Best for | ⚠ Limitation |
|---|---|---|---|
| Attribution | Unprompted correct brand identification from unbranded motion (Ch. 11) | ⭐ The expressive dialect. The closest thing to a true measure of motion's brand value | Needs n≈200+ per market; slow to move; annual cadence at best |
| Efficiency | Cost per compliant asset; producer rework rate; time-to-produce | The system layer. ⭐ The easiest genuine ROI to demonstrate | Measures the system, not the motion. A cheap system producing bad motion scores well |
| Task performance | Time on task, error rate, completion rate, interaction responsiveness | The functional dialect | ⚠ Structurally blind to brand value (Ch. 12). Will recommend removing distinctiveness |
| Risk reduction | Compliance coverage: Tier 2/3 completeness, PSE clearance, disclosure compliance | ⭐ The most under-claimed value in the discipline | Not a growth argument; a loss-avoidance argument. Finance understands it well |
⭐ The under-used one is risk reduction, and it is the strongest with a sceptical CFO. Motion is now the primary locus of legal exposure in an identity system (Ch. 5, point 5). A motion system that brings compliance coverage from unknown to 100% has produced quantifiable value: it has removed an unquantified liability. ⚠ Kestrel's platform-screen finding was worth more to its board than any attribution number.
58. ⭐ FULLY WORKED NUMERICAL EXAMPLE
⚠ Fictional. Kestrel Rail, 18 months post-launch. All figures invented to be internally consistent and realistically ordered. The purpose is to show the method and to expose which assumptions dominate the answer.
The investment
| Item | Cost (€) |
|---|---|
| Audit and diagnosis (4 weeks) | 34,000 |
| Grammar and framework development (3 weeks) | 28,000 |
| Component specification, 26 components | 46,000 |
| Token development and pipeline integration | 31,000 |
| Logo behaviour, endframe, ident set (3 idents) | 88,000 |
| Sonic signature | 24,000 |
| Templates, 9 formats | 19,000 |
| Tier 2 / Tier 3 specification across all instances | 17,000 |
| Validation (5 tests, Ch. 33) | 22,000 |
| Photosensitivity assessment, platform screens | 11,000 |
| Internal labour (estimated, 0.6 FTE × 8 months) | 41,000 |
| Total investment | 361,000 |
| Ongoing annual: 0.3 FTE owner + annual attribution test | 58,000 / yr |
1. Efficiency — the hard, defensible number
| Metric | Before | After 18 months | Basis |
|---|---|---|---|
| Assets produced by regional teams per year | 340 | 340 | Unchanged volume |
| Proportion requiring central rework | 62% | 14% | Measured |
| Assets reworked per year | 211 | 48 | Calculated |
| Average rework cost per asset | €420 | €420 | Internal day-rate estimate |
| Annual rework cost | €88,620 | €20,160 | |
| Annual saving | €68,460 |
Additional efficiency: average production time per social asset fell from 6.5 to 4.1 hours (templates). 340 assets × 2.4 hours × €55/hr = €44,880/yr.
Total measured efficiency return: €113,340 / yr.
2. Risk reduction — quantified as coverage, not cash
| Item | Treatment |
|---|---|
| Platform-screen photosensitivity risk, 900 screens, previously unassessed | ⚠ Not monetised. Recorded as: an unquantified liability affecting ~420 impressions/passenger/year, now assessed and remediated |
| Accessibility coverage: Tier 2/3 from 0% to 100% | Recorded against EAA applicability (Ch. 16) |
| Broadcast PSE clearance now systematic | Avoided re-edit and re-clearance cost, estimated €8,000–15,000 per failed asset [I, internal estimate] |
⚠ Deliberately not monetised. Assigning a euro value to avoided harm requires assumptions about incident probability that nobody can defend. ✔ Present risk reduction as a coverage change, not a cash figure. Boards accept this; they reject invented probabilities, and rightly.
3. Attribution — measured, and modest
| Metric | Baseline | 18 months |
|---|---|---|
| Unprompted attribution, unbranded expressive asset | 11% | 19% |
| Curve-only recognition, category buyers | 41% | 52% |
| Distinct easing behaviours on the mark | 5 | 1 |
⚠ The +8 percentage points of attribution is not converted to revenue, and this is the honest core of the example. Doing so would require a link between attribution and purchase that the field has not established (Ch. 57). It is reported as what it is: evidence the asset is accumulating, on the mechanism theory says drives growth, with the commercial link explicitly unproven.
4. Task performance — one clear result, one null result
| Metric | Before | After |
|---|---|---|
| Interaction responsiveness, tenth-percentile device | Baseline | No regression ✔ |
| Time to comprehend a disruption alert (moderated testing, n=24) | 2.9s | 2.1s |
| Ticket purchase completion rate | 94.1% | 94.3% |
⚠ The completion-rate change is within noise. Report it as null. Reporting a 0.2pp movement as a win is how motion practitioners lose credibility with analytics teams permanently.
The financial summary
| Year 1 | Year 2 | Year 3 | |
|---|---|---|---|
| Investment | (361,000) | (58,000) | (58,000) |
| Efficiency return | 56,670 (half-year) | 113,340 | 113,340 |
| Net cash | (304,330) | 55,340 | 55,340 |
| Cumulative | (304,330) | (248,990) | (193,650) |
Payback on efficiency alone: does not occur within five years.
⭐ This is the honest answer, and it is the most important number in this chapter. A motion system does not pay back on efficiency at Kestrel's scale. Anyone presenting a motion business case as an efficiency play at this scale is either working at much larger volume or is inventing numbers.
Volume dominates efficiency payback — judgement→lookup only pays at scale.
Attribution may dwarf efficiency if commercially linked — but link is unproven.
Justify on volume and risk. Present attribution as measured accumulation, not revenue.
Text equivalent — sensitivity
Efficiency case is volume-dependent; do not monetise attribution without established purchase link.
59. The purest single test
If you could measure only one thing, measure this:
Show category buyers your motion, stripped of logo, colour, typeface and the shape being animated — leaving only the curve, the order and the timing. Ask them, unprompted, whose it is.
Why this test and not another:
- It isolates the only thing a motion identity uniquely owns. Everything else in the asset is doing work that colour, type or logo could also do.
- It tests the layer that is free to render, survives reduced motion, and cannot be optimised away (Ch. 8).
- It is unfoolable. You cannot pass it by spending more.
- ⚠ It is humbling, which is why it is rarely run.
✔ Interpretation ◇. At four options, chance is 25%. Meaningfully above chance means the asset is forming. Near chance after two years of consistent deployment means the grammar is not distinctive, and the correct response is to change the grammar rather than to spend more on assets. ⚠ Requires n≈200+ per market to distinguish these cases (Ch. 11).
60. ⭐ The tiered measurement stack
Three tiers, three audiences. ⚠ Reporting Tier 3 metrics to decision-makers is how motion loses its budget: they cannot act on frame rates, so they conclude motion is not strategic.
Tier 1 — Decision-makers (5 metrics)
Quarterly / annual
- • Unprompted attribution, unbranded expressive asset
- • Impression coverage of governed system
- • Compliance coverage: Tier 2/3, PSE, disclosure
- • Producer rework rate
- • Interaction responsiveness on tenth-percentile device
Tier 2 — Diagnostic
For motion owner
- • Distinct easing curves in production vs grammar
- • Row coverage vs impression coverage
- • Open exceptions past sunset
- • Deprecated-token references (if migrating)
Tier 3 — Operational
Designers and engineers
- • Frame rate per instance per device class
- • Compositor-only compliance
- • Template usage rate
- • Source-file retrievability
Text equivalent — measurement tiers
- Tier 1 — Decision-makers (5 metrics): Unprompted attribution, unbranded expressive asset; Impression coverage of governed system; Compliance coverage: Tier 2/3, PSE, disclosure; Producer rework rate; Interaction responsiveness on tenth-percentile device
- Tier 2 — Diagnostic: Distinct easing curves in production vs grammar; Row coverage vs impression coverage; Open exceptions past sunset; Deprecated-token references (if migrating)
- Tier 3 — Operational: Frame rate per instance per device class; Compositor-only compliance; Template usage rate; Source-file retrievability
⚠ Most motion reporting is entirely lagging, which is why motion appears unmanageable.
| Leading — moves first, predicts the rest | Lagging — confirms, too late to steer |
|---|---|
| Distinct easing curves in production | Unprompted attribution |
| Matrix rows with no owner | Curve-only recognition |
| Unreferenced and duplicate token count | Brand-health tracker movement |
| Open exceptions past sunset | Producer rework rate |
| Deprecated-token references per release | Task-performance metrics |
| Time-to-decision on exceptions | Compliance incident count |
| Template usage rate | Impression coverage |
⭐ The single best leading indicator in the discipline: the count of distinct easing curves in production, measured in code rather than in the document. It requires no research budget, can be automated, moves within weeks of governance weakening, and predicts every lagging metric in the right-hand column. If that number is creeping up, attribution will fall in eighteen months. ⚠ Almost no organisation tracks it.
61. Resource and budget allocation rules ◇
| Rule | The heuristic | Basis |
|---|---|---|
| Frequency-weighted allocation | Motion budget should be distributed closer to the distribution of impressions than to the distribution of visibility to leadership | Ch. 10. ⚠ The most consequential and most resisted allocation rule in the report |
| System-before-assets in year one | At Level 1–2 maturity, expect specification and tokenisation to exceed rendered-asset spend | Ch. 20. Inverts the normal ratio; must be argued explicitly |
| The 20–30% pre-production share | Scripting, storyboarding and specification consume 20–30% of project cost | Industry rate guidance |
| Two revision rounds, then repriced | Open-ended feedback is the largest overrun source | Industry practice. ⚠ Ch. 9's parameter table is the actual fix |
| Cut count over runtime | Cost scales with shot count more than duration | Industry rate guidance |
| The ongoing 0.3 FTE minimum | A governed system needs roughly a third of a person permanently, plus an annual research line | ⚠ Synthesis, not measured. Below this, governance is review-only and drifts (Ch. 51) |
| The measurement line | Budget the annual attribution test at the outset, in the same approval | ⭐ Retro-funding research is nearly impossible (Ch. 64) |
⭐ The allocation argument that works with finance: do not ask for a motion budget. Ask for a reallocation within existing motion spend, evidenced by the frequency-weighted chart. Most organisations are already spending enough on motion; they are spending it on 3% of their impressions. Kestrel spent €140k over two years on an ident seen six times a year per person, while spending nothing on transitions seen 1,100 times.
62. The one-page case for investment
Motion system — investment case
The situation
[n]% of this brand's motion impressions occur in instances with zero design specification. We have [n] distinct behaviours on the same core element, produced by [n] parties. No rule was broken, because no rule exists.
The exposure
[n] instances have no reduced-motion state. [n] have never been assessed for photosensitivity risk. [n] carry AI-disclosure obligations that became enforceable on 2 August 2026. Current compliance coverage: [n]%.
The ask
€[n] one-off. €[n]/yr ongoing (0.3 FTE + annual research). Sourced [x]% from reallocation of existing motion spend.
What we will deliver
One governed grammar, two dialects, tokens consumed by the product build, specifications for [n] instances covering [n]% of impressions, Tier 2 and Tier 3 states at 100%.
How you will know it worked
Distinct easing behaviours [n] → 1; impression coverage [n]% → [n]%; compliance coverage [n]% → 100%; producer rework rate [n]% → [n]%; responsiveness on [device]: no regression. Baselines measured [date]. Re-test [date].
The honest caveat
Efficiency returns are ~€[n]/yr and do not pay back within [n] years at our current asset volume. The case rests on risk reduction and on building a distinctive asset. ⚠ We will measure attribution and report it, and we will not convert it to a revenue figure, because that link is not established in this field.
What we are not claiming
We are not claiming a sales effect. No published controlled study demonstrates one.
Text equivalent — investment case
- The situation: [n]% of this brand's motion impressions occur in instances with zero design specification. We have [n] distinct behaviours on the same core element, produced by [n] parties. No rule was broken, because no rule exists.
- The exposure: [n] instances have no reduced-motion state. [n] have never been assessed for photosensitivity risk. [n] carry AI-disclosure obligations that became enforceable on 2 August 2026. Current compliance coverage: [n]%.
- The ask: €[n] one-off. €[n]/yr ongoing (0.3 FTE + annual research). Sourced [x]% from reallocation of existing motion spend.
- What we will deliver: One governed grammar, two dialects, tokens consumed by the product build, specifications for [n] instances covering [n]% of impressions, Tier 2 and Tier 3 states at 100%.
- How you will know it worked: Distinct easing behaviours [n] → 1; impression coverage [n]% → [n]%; compliance coverage [n]% → 100%; producer rework rate [n]% → [n]%; responsiveness on [device]: no regression. Baselines measured [date]. Re-test [date].
- The honest caveat: Efficiency returns are ~€[n]/yr and do not pay back within [n] years at our current asset volume. The case rests on risk reduction and on building a distinctive asset. ⚠ We will measure attribution and report it, and we will not convert it to a revenue figure, because that link is not established in this field.
- What we are not claiming: We are not claiming a sales effect. No published controlled study demonstrates one.
⭐ The two most persuasive elements are the last two boxes. A case that names its own limits is trusted on everything else it claims. A case built on "8.5× more effective" collapses the moment someone finds the source (Ch. 5).
63. What to measure when there is no financial dimension
Not every motion system sits in a commercial brand. The structure holds; substitute the domain's real currency.
| Domain | Substitute currency | Tier 1 metric equivalents |
|---|---|---|
| Public sector / civic | Comprehension and access | Time to comprehend a critical notice; Tier 2/3 coverage; proportion of population served on low-end devices |
| Healthcare | Safety and error reduction | Error rate on critical confirmations; time to comprehend an alert; ⚠ zero tolerance on overshoot and flash thresholds |
| Education | Learning gain | Comprehension of an explanatory sequence; ⚠ measured against a static-diagram control, which frequently wins |
| Transport / safety-critical | Risk reduction | Photosensitivity assessment coverage; comprehension under time pressure; failure-state legibility |
| Charity / advocacy | Attention and recall per unit spend | Unprompted attribution; message recall; cost per attributed impression |
⚠ In every one of these, the restraint gate (Ch. 27) carries more weight than the distinctiveness argument. In a safety-critical or clinical context, an unnecessary 400ms animation is not a brand risk, it is an operational one. The dialect split still applies — but the functional dialect's authority over the expressive one is close to absolute.
64. ⭐ HARD GATE 4 — Measurement in place
This gate sits before launch, not at the end, because ⭐ a baseline you did not measure before launch cannot be measured retrospectively, ever. This is the gate whose failure is permanent.
- [ ]Distinct easing behaviours counted in code with today's date
- [ ]Impression coverage calculated from frequency-weighted audit
- [ ]Compliance coverage: Tier 2/3, PSE, disclosure counted
- [ ]Producer rework rate measured over a real period
- [ ]Responsiveness on tenth-percentile device instrumented
- [ ]Unprompted attribution tested and recorded (n, market, method)
- [ ]Curve-only recognition tested and recorded
- [ ]Annual re-test scheduled and funded with build approval
- [ ]Conversion-testing exemption for expressive dialect signed
- [ ]Tier 1 reporting line agreed: five metrics, recipient, cadence
- [ ]Method documented to reproduce exactly in 12 months
Text equivalent — Gate 4 checklist — Ch. 64
- Distinct easing behaviours counted in code with today's date
- Impression coverage calculated from frequency-weighted audit
- Compliance coverage: Tier 2/3, PSE, disclosure counted
- Producer rework rate measured over a real period
- Responsiveness on tenth-percentile device instrumented
- Unprompted attribution tested and recorded (n, market, method)
- Curve-only recognition tested and recorded
- Annual re-test scheduled and funded with build approval
- Conversion-testing exemption for expressive dialect signed
- Tier 1 reporting line agreed: five metrics, recipient, cadence
- Method documented to reproduce exactly in 12 months
⚠ The commonest failure at this gate is a schedule failure, not a will failure. Attribution testing takes four to six weeks and needs a sample. Launch dates slip toward it and someone proposes measuring the baseline "just after launch." Refuse. A post-launch baseline is not a baseline; it is a first reading with the intervention already applied, and it forfeits the only mechanism by which this discipline can prove its own value. </user_query>