You've shipped a new motion system. How do you best judge whether it actually succeeded?
- A. Count how many animations you added
- B. Combine task-success and speed metrics, accessibility compliance, and user feedback against the goals the motion was meant to serve ✓
- C. Ask the design team if they're proud of it
- D. Check whether it won a design award
Correct answer: B. Success is measured against the motion's intended job, using behavioural, accessibility and qualitative evidence, not output volume or internal pride.
Leadership wants a bold, animation-heavy redesign; your instinct says it will slow core workflows. How do you proceed?
- A. Comply fully to stay aligned with leadership
- B. Prototype both, test against key task metrics, and present evidence to find the right restraint ✓
- C. Quietly build the restrained version you prefer
- D. Refuse the project citing usability principles
Correct answer: B. Senior judgement resolves the tension with evidence: prototype, measure impact on real tasks, and let data reconcile ambition with usability.
Across a large product, motion has drifted into dozens of inconsistent one-offs. What's the most durable fix?
- A. Personally re-animate every screen to your taste
- B. Define a motion language (principles, tokens, choreography rules) and governance so teams stay consistent as they scale ✓
- C. Ban animation except where you approve it
- D. Document the current state and leave it alone
Correct answer: B. At system scale, consistency is sustained by shared principles, tokens and governance that many teams can apply, not by heroic one-person cleanup.
A signature transition you fought for tests as slightly slower on task completion but users rate the app as more polished. How do you decide?
- A. Keep it; perceived polish always wins
- B. Weigh the friction against the brand value, considering task frequency and context, and choose or tune deliberately ✓
- C. Remove it; any task slowdown is unacceptable
- D. Let the PM decide alone
Correct answer: B. Mature trade-off analysis weighs measurable friction against brand value in context and frequency, rather than treating either metric as automatically decisive.
You must defend keeping a subtle, expensive-to-build easing detail that most users won't consciously notice. What's the strongest case?
- A. It's my signature and shows craft
- B. Subconscious cues like this shape overall feel and trust, and it's consistent with our motion system's principles ✓
- C. Competitors have it, so we need it
- D. It was hard to build, so it should stay
Correct answer: B. The defensible argument ties the detail to how it shapes users' subconscious perception and to system consistency, not to ego or effort spent.
A new platform (e.g., a watch or TV) needs motion. How should you adapt your existing language?
- A. Reuse the phone animations unchanged for consistency
- B. Re-derive the motion from the same principles but retune timing, distance and input for the new context and hardware ✓
- C. Design entirely unrelated motion to feel fresh
- D. Turn off motion since the platform is different
Correct answer: B. Scaling a motion language means carrying the principles across platforms while retuning the specifics to each context's input, viewing distance and performance.
Your motion increases delight metrics but support tickets about 'the app feeling laggy' rise on older devices. How do you respond?
- A. Prioritise the delight metric since it's higher-value
- B. Segment performance data, set a frame-rate budget, and provide a lighter motion tier for constrained devices ✓
- C. Tell support to advise users to upgrade
- D. Remove all motion to be safe
Correct answer: B. Senior practice sets performance budgets and adaptive tiers so delight for some users never comes at the cost of a broken experience for others.
A designer argues every screen should have a unique 'hero' animation to feel crafted. As lead, how do you respond?
- A. Approve it to encourage creative ownership
- B. Explain that a consistent, learnable language usually serves users better than novelty per screen, reserving hero moments intentionally ✓
- C. Reject creativity outright
- D. Let each designer do whatever they want
Correct answer: B. System-level thinking values learnability and coherence over per-screen novelty, spending distinctive hero moments deliberately rather than everywhere.
You're setting motion principles for a design system many teams will use. What makes them most effective?
- A. Highly prescriptive rules for every possible animation
- B. Clear principles plus tokens and examples that explain the 'why,' so teams can make good decisions in new cases ✓
- C. A gallery of finished animations to copy exactly
- D. Leaving it open so teams interpret freely
Correct answer: B. Durable systems teach the reasoning and provide reusable tokens, empowering teams to make consistent decisions in situations the docs never anticipated.
Analytics can't isolate your motion's impact from other simultaneous changes. How do you still evaluate it responsibly?
- A. Claim credit for any positive movement in the metrics
- B. Use targeted usability sessions, isolated prototype tests, and qualitative signals to assess the motion specifically ✓
- C. Assume it had no effect and move on
- D. Wait until you can run a perfect isolated experiment someday
Correct answer: B. When clean quantitative isolation isn't possible, rigorous evaluation leans on controlled prototype tests and qualitative research targeted at the motion itself.
A high-profile stakeholder loves an animation that you believe harms comprehension of a critical safety-related flow. What do you do?
- A. Defer to their seniority and ship it
- B. Bring evidence from testing on the safety-critical flow and advocate firmly for the user, proposing an alternative that satisfies intent ✓
- C. Ship it but add a disclaimer
- D. Escalate to their boss without discussion
Correct answer: B. Where comprehension is safety-critical, the designer's duty is to advocate with evidence and offer an alternative, not to defer purely to rank.
Your motion system needs to support both a playful consumer app and a serious enterprise product under one brand. How do you structure it?
- A. Use identical motion everywhere for brand unity
- B. Define shared principles and tokens with tunable parameters (energy, duration ranges) that each product expresses differently ✓
- C. Build two completely unrelated systems
- D. Let the consumer style dominate both
Correct answer: B. A scalable brand motion system shares a principled core while exposing tunable ranges so distinct products can express appropriate character.
You notice engineers routinely simplify your handed-off motion because specs are ambiguous. What's the root-cause fix?
- A. Sit with each engineer to police every implementation
- B. Improve the handoff: precise tokens, edge-case states, reference prototypes, and early collaboration on feasibility ✓
- C. Design simpler motion so nothing gets lost
- D. Blame engineering for cutting corners
Correct answer: B. Reliable implementation comes from unambiguous specs, buildability discussed early, and reference artifacts, addressing the cause rather than policing symptoms.
A motion pattern that worked at 10 screens is creating inconsistency and maintenance pain at 200 screens. What's the mature response?
- A. Keep patching individual screens as issues arise
- B. Step back, codify the pattern into reusable components/tokens, and refactor so it scales predictably ✓
- C. Freeze the design system to stop the growth
- D. Accept inconsistency as inevitable at scale
Correct answer: B. Scaling problems call for abstracting the pattern into reusable, governed components so consistency holds as the surface area grows.
You must decide whether a delightful but non-essential loading animation is worth its engineering and performance cost. How do you frame the decision?
- A. Keep it because delight is inherently valuable
- B. Assess how often it's seen, its effect on perceived wait and brand, and its cost, then decide against clear criteria ✓
- C. Cut it because it's non-essential by definition
- D. Let engineering decide based on effort alone
Correct answer: B. Senior prioritisation evaluates value (frequency, perceived-wait, brand) against cost with explicit criteria rather than defaulting to either delight or thrift.
Users with vestibular sensitivities report discomfort from your large parallax and zoom transitions. How should the system respond long-term?
- A. Add a one-off toggle just for those screens
- B. Bake reduced-motion alternatives and safe defaults into the motion system so accessibility is structural, not patched ✓
- C. Tell affected users to disable animation at the OS level
- D. Reduce the parallax slightly and hope it's enough
Correct answer: B. Accessible motion at scale is designed into the system with built-in reduced-motion alternatives, not bolted on per screen after complaints.
Two respected team members disagree: one wants springy, physical motion, the other crisp and minimal. As lead, how do you resolve it?
- A. Pick the style you personally prefer
- B. Decide based on brand strategy, user context and testing, then codify it so the debate doesn't recur per feature ✓
- C. Alternate between both to keep everyone happy
- D. Let each ship their own style
Correct answer: B. Leadership resolves style debates against strategy and evidence and then codifies the decision, preventing the same argument from replaying on every feature.
A quarter after launch, how do you know your motion language is still serving users rather than just existing?
- A. It's still there and nobody complained
- B. Revisit it against current task metrics, accessibility, device performance and feedback, and prune or retune what no longer earns its place ✓
- C. Assume it's fine unless leadership asks
- D. Add new animations to keep it feeling current
Correct answer: B. Motion, like any design, needs periodic review against real outcomes so elements that no longer earn their keep get retuned or removed.
You're asked to justify motion investment to a skeptical executive focused on ROI. What's the strongest framing?
- A. Show a reel of the prettiest animations
- B. Tie motion to measurable outcomes: comprehension, perceived performance, error reduction, and brand perception, with evidence ✓
- C. Argue that all modern apps have animation
- D. Emphasise how much effort the team put in
Correct answer: B. The persuasive case connects motion to business-relevant outcomes with evidence, rather than relying on aesthetics or industry conformity.
Your team wants to adopt an off-the-shelf animation library to move faster. What's the key senior consideration?
- A. Adopt it immediately to save time
- B. Check that its motion aligns with your principles, performs on target devices, and can be tokenised into your system, not just that it's convenient ✓
- C. Reject it to keep everything custom
- D. Use it only for the parts engineers find hard
Correct answer: B. Tooling decisions must be judged against system fit, performance and consistency, so a library serves the motion language rather than fragmenting it.