Building the Motion Product Practice
Overview
When I joined monday.com, motion design had no role, no precedent, and no expectation within the product. I built the practice from scratch: researching what motion should mean for a complex work platform, defining its strategic purpose across the R&D org, and growing the team that brought it to life.
Role
Motion Design Team Lead
Concept, Strategy & Delivery
Part 1
Establishing Motion’s Purpose
The first question wasn’t how to animate. It was why. I formalized a framework that gave the entire R&D org a shared language for motion’s role in the product. Every animation we ship belongs to one of four pillars:
Orientation & Guidance
Attention & Education
Feedback
Brand Recognition
Part 2
From Decoration to Communication
The framework changed how we responded to motion requests. Where teams once asked for “a delightful animation,” we now had a language to push back with the right question: which pillar does this serve?
The Dashboard Refresh is the clearest example. Before the framework, a data refresh happened silently. The UI updated with no signal to the user. Motion’s job here wasn’t decoration. It was communication.
The Shift: If a state change occurs, it must be visible and clear. No user action goes unacknowledged.
Ex. 01: Dashboard Refresh Button
Before
- The data refreshed silently. Users had no way to know the update had occurred.
After
- A deliberate pause before the refresh draws the eye to the change, making the system response impossible to miss.
Guidance through Behavior
Feedback with Location
Brand Recognition
Guidance through Behavior
Feedback with Location
Brand Recognition
Guidance through Behavior
Feedback with Location
Brand Recognition
Part 3
From Framework to Delivery
I integrated motion into the Design System via two layers:
Motion Tokens: Standardized values that create a consistent physical “weight.”
- Duration: Mapped to user goals, from Micro-interactions (70ms) to Attention (500ms).
- Easing: Purpose-built Cubic-Bezier curves for Enter, Exit, and Transition states.
Motion Patterns: A curated library of reusable behaviors that prevent visual fatigue and ensure platform-wide consistency.
Tokens
Duration
Cut0msInstant state change, no transitionExtreme Short70msMinor changes: color change, fadesShort100msMicro interactions: toggle, button press/releaseMedium150msComponent appears, dialog box, buttonLong250msInteraction with emphasis: chips, tabs, fabSoft350msTransition of big element or distance: cardsAttention500msSystem alerts, notifications, errorsEasing
Entercubic-bezier(0, 0, .2, 1)Use for object appearanceExitcubic-bezier(.6, 0, 1, 1)Use for object disappearanceTransitioncubic-bezier(.4, 0, .2, 1)Use for changes between states of the same objectKeyframecubic-bezier(0.33, 0, .67, 1)Use to build keyframesLinearlinearUse for opacity: fade or color changePatterns
Pop Directional
Highlights the spatial relationship between parent and child components.
Pop Enter
Standardizes the entrance of new UI elements
Pop Emphasize
A non-intrusive method to grasp attention without breaking the user's flow.
The impact
Patterns Create Flow
By combining Tokens (the rules) with Patterns (the behavior), we gave every team in R&D the tools to ship consistent, high-quality motion without needing a motion designer in the room.
Consistency
Designers and engineers can now implement high-quality motion independently.
Efficiency
Reduced the need for custom motion specs by ~50% through reusable system components.
Usability
By highlighting relationships and state changes consistently, we significantly reduced the cognitive load required to navigate complex boards.