How to Turn a Motion Reference into Clear Creative Direction

How to Turn a Motion Reference into Clear Creative Direction, with a cropped IBM · Motion vocabulary screenshot on an oil-painted background

“Make it feel like this” is an understandable way to start a motion project. A reference communicates more quickly than a long list of adjectives. But it can also conceal disagreement: one person likes the generous typography, another likes the camera movement, and a third expects the same playful transitions. They have approved the same link while imagining different videos.

A useful motion design reference analysis makes those preferences explicit. It identifies what happens, what that behavior contributes, and which parts belong in your project. The output is not a catalog of everything visible in the reference. It is a direction another person can use without copying the source’s identity or guessing what you meant.

Published IBM and Dropbox guidance supplies a useful vocabulary for deciding what a movement should contribute to your own scene.

Choose an animation reference for a specific problem

Before taking screenshots, write a sentence about the reference’s purpose. Perhaps it shows how to keep a product legible during a transition. Perhaps its typography feels assured without overwhelming the screen. Perhaps it demonstrates how an expressive opening can lead into a practical explanation. That purpose should connect to a real need in your video.

If you cannot name the connection, keep the reference as inspiration rather than direction. It may still be useful to explore a mood, but it should not silently determine the production. A beautifully animated fashion film might have little to teach a software onboarding video about showing a precise sequence of interface states.

Ask the person who supplied the link what they want to borrow and what they do not. This is not an invitation to collect more adjectives. Point to a moment or property: the title stays in one place while the background changes; the camera stops before the important interface detail appears; the closing frame leaves enough room for the message.

A reference can also be useful because it demonstrates something to avoid. If a transition looks impressive but makes the product hard to follow, record that limitation. Record why the technique would help or obstruct this viewing task.

Separate observation, interpretation, and proposal

Keep three kinds of note distinct. An observation records what you can see or hear. An interpretation explains why you think it works. A proposal describes what you would do in your own project. Mixing them makes personal preference sound like an objective property of the source.

For example, “the title remains in the same position across the cut” is an observation you can verify by comparing frames. “That stable position helps maintain orientation” is an interpretation. “Keep our feature title fixed while the product state changes” is a proposal. The proposal can be useful even if your explanation of the original designer’s intent is uncertain.

Do not assign precise timing from a still image. A screenshot can show placement, contrast, type scale, and the visible state of an object. It cannot establish acceleration, a pause, a transition path, or synchronization with sound. Those require watching the actual sequence, ideally with controls that let you replay the relevant interval.

The same boundary applies to audio. A visible waveform or a muted player does not tell you how the soundtrack feels. If your analysis is visual only, say so in the working notes and leave sound decisions open. You can still produce useful visual direction without pretending to have reviewed an element you did not experience.

Note type Hypothetical example How it becomes useful
Observation The panel finishes moving before the label appears Establishes a visible sequence
Interpretation The pause may help the viewer locate the panel Suggests a reason to test
Proposal Use that sequence for our feature explanation Becomes a concrete direction
Open question Does the hold remain readable on a phone? Identifies a review task

Map events before describing the overall style

Watch the reference once at normal speed to understand the communication. Then revisit the section you intend to borrow from. Identify the meaningful events: an object enters, a state changes, a title becomes readable, a transition starts, or the scene resolves. You do not need to document every frame to understand the sequence.

Use timestamps from the actual file or player when you record them. Avoid transferring timings from a different edit of the same campaign. If the reference is a looping embed with no reliable time display, identify the events in order and describe the limits of your observation. A rough but honest event map is more useful than fabricated precision.

Notice which events overlap and which wait for one another. A title may enter while a panel is still moving, or it may wait until the panel settles. Those two sequences can create different reading experiences even when the final still frame is identical. This is why a mood board alone cannot carry a complete motion direction.

Then identify the hierarchy within each event. What moves first? What stays quiet? Where does the viewer’s attention go next? A sequence that feels calm may contain substantial movement, but arrange it so that one change leads at a time. Describe that relationship before deciding that the reference simply needs to be “slower.”

Use IBM’s distinction to discuss purpose, not just speed

IBM’s animation overview distinguishes productive motion, associated with efficiency and responsiveness, from expressive motion, associated with energy and personality. It describes these as complementary approaches whose application depends on the reason for the movement, rather than a single formula. This gives a team a more useful vocabulary than treating all motion as either fast or slow.

Actual IBM Design Language page describing productive and expressive animation

For your own reference analysis, ask which role a particular moment serves. Does it explain a state change, preserve orientation, or confirm an action? Does it introduce the brand, celebrate an outcome, or create anticipation? A video may need both types of moment, but they should not compete indiscriminately.

A fictional product launch might use a more expressive opening to establish character, then a restrained demonstration so viewers can inspect the interface. The closing message could return to the opening’s visual language. Assign each expressive moment a role before choosing its treatment.

This distinction can resolve a common disagreement. One reviewer wants more personality; another wants less distraction. They may both be right about different parts of the sequence. Instead of averaging the whole film into a vaguely moderate style, assign expression to particular moments and protect the moments that carry detailed information.

The IBM reference image supplies a concrete composition note: curved black paths and circular nodes share the frame with an angular white structure. That observation is already more useful than “organic but technical.” It identifies a contrast you can translate into your own scene. Decide which object should carry the more fluid behavior and which should provide a stable reference. Then test whether the contrast helps the viewer follow the intended relationship. Keeping one structure quiet may make the other movement easier to inspect. Copying both path shapes without assigning those roles would preserve the surface while losing the reason for the contrast.

IBM’s published animation reference image showing curved black paths and an angular white structure

Examine the composition that makes the movement work

A transition does not operate independently of the frame around it. The available space, type size, object position, and background contrast determine what the viewer can follow. When you borrow a movement without its supporting composition, it can feel wrong even if the path and duration are similar.

Compare the start, the most active moment, and the settled state. Check whether the main subject changes size or position, whether text remains readable, and whether objects cross or cover one another. A movement that looks simple at the endpoints may pass through a crowded intermediate frame that matters for your version.

Measure relationships before absolute values. A title occupying roughly half the available width tells you something about hierarchy; copying its pixel size into a different frame does not. A product screen positioned near the title may create a coherent reading group. Moving that screen to the far edge in your version can break the relationship even if all the individual assets look polished.

Pay attention to empty space as working room. It may provide a path for an object, protect a headline from a moving background, or allow a viewer to distinguish successive states. Filling every quiet area with another asset can remove the condition that made the reference feel composed in the first place.

Translate brand character without importing brand identity

References often feel distinctive because their typography, color, imagery, and motion work together. You cannot assume that swapping in your logo will produce an equally coherent result. Start with your own approved brand assets and use the reference to guide relationships or behavior, rather than replacing your identity with the source’s surface treatment.

Dropbox’s motion guidelines connect simplicity, understanding, responsive feedback, and restrained playfulness to its brand expression. The useful lesson is that personality is described alongside function. Read each principle as a choice about how the brand behaves.

Dropbox’s actual motion principles page

You might borrow the idea of a small expressive response while keeping your own typeface, colors, shapes, and tone. Describe what the expression should achieve: acknowledge completion without overwhelming the result, or make a closing moment feel warm without turning the whole sequence into a celebration. That gives the maker room to produce an original treatment.

Be explicit about exclusions. If you like a reference’s pacing but not its elastic movement, say so. If the composition is useful but the color system belongs to another brand, identify your own palette as fixed. A concise exclusion list prevents a reference link from becoming accidental authorization to imitate everything it contains.

Dropbox’s example also turns a vague preference into a bounded direction. If the product result must remain the focal point, give the small expressive response to a secondary object after the result is visible. Keep the status label and task identity steady. In a closing beat, that balance can change: the logo may carry the expression once the explanation is complete. Write those roles into the direction rather than requesting playfulness everywhere. This helps two reviewers who seem to disagree: one can get a warmer finish while the other keeps the detailed demonstration calm. The reference contributes a behavior at a chosen moment, not a treatment imposed uniformly across the film.

Close crop of Dropbox’s Subtle Playfulness example and its published preference for a restrained expressive response

Resolve conflicting references before production

Two good references can point in incompatible directions. One may use dense information and rapid cuts; another may rely on a single object and long holds. Asking for both without assigning their roles forces the maker to invent a compromise. The result may satisfy neither reason you selected them.

Give each reference a specific contribution. Reference A can inform title placement. Reference B can inform the transition between product states. Your own brand rules determine type and color. This is more actionable than listing several links under “visual style” and expecting the common thread to be obvious.

If the contributions still conflict, choose based on the video’s job. A detailed product explanation needs sufficient time and scale for inspection. A short atmospheric opener may tolerate ambiguity that would be frustrating in a tutorial. The question is not which reference is objectively better; it is which behavior supports the intended viewing task.

Write down the rejected option briefly when it prevents a recurring debate. For example, the rotating-screen treatment was considered but set aside because the essential label becomes too small. That note is useful project context. It should not become a long defense of every design decision or a permanent constraint on unrelated videos.

Turn analysis into a direction someone can execute

A useful direction describes the scene’s purpose, the behavior to borrow, the assets that remain fixed, and the result to inspect. It should be short enough that the maker can locate the actual instruction without reading an essay about the reference. Keep detailed observations available as supporting material.

For a hypothetical feature demonstration, the direction might be: show the task changing to its completed state; keep the product screen stable while that happens; reveal the benefit after the state settles; preserve our approved typography and screenshot; borrow the reference’s sequence of attention, not its colors or logo movement.

That instruction does not specify every implementation detail. It leaves room for the maker to choose a suitable transition while protecting the communication. If a particular curve, path, or duration is essential and has been observed reliably, include it. Otherwise, avoid false precision that makes a preference look like a measured requirement.

Attach the smallest useful set of reference frames with clear labels. A start state and a settled state may explain composition, while a link to the relevant moving sequence explains behavior. Attach the moving interval when path, acceleration, or sound is part of the direction.

Test the interpretation with your own content

Before producing a whole film, build one representative sequence using your real assets and approved copy. The reference may have a three-word title while your message needs a longer explanation. It may feature an abstract shape while your scene contains a detailed interface. Those differences can change whether the borrowed behavior works.

Compare the test with the purpose you wrote at the start. If the goal was to keep the product legible during a transition, inspect legibility during that transition. If the goal was a calmer reading experience, watch the complete scene at normal speed. A general resemblance to the reference is not the same as solving the intended problem.

Invite feedback in terms of the effect, not fidelity to the inspiration. Ask whether the viewer knows where to look and whether the important state change is understandable. If the treatment works only when placed beside the original reference, the direction has not become a self-sufficient design yet.

Keep the approved direction with the editable OpenDesign source and use the Motion project workflow to preview and export the representative sequence. Recheck the particular relationship you borrowed when later copy or capture changes.

Finish with a decision, not a larger reference folder

Stop collecting when the team can explain what it is borrowing, why that helps, and how it will judge the result. More links can be useful when a real question remains unresolved. They are less useful when they postpone choosing among already understood alternatives.

Keep the final reference note current. Remove directions that have been superseded, preserve the approved assets, and record the specific behavior the test established. A future collaborator should not have to reconstruct which of six mood boards represents the decision that produced the current video.

The strongest reference analysis leaves you less dependent on the reference. You understand the relationship between movement, composition, and purpose well enough to make a new piece with its own identity. That is the difference between a link that expresses taste and a direction that helps someone make the right next version.