Design System Migration: A Campaign, Not a Mandate
Migrating to a new design system is a campaign to win over teams, not just a technical refactor. Use strategies like piggybacking on features (Trojan Horse) or starting with willing teams to build momentum and avoid getting stalled by resistance.
Why it exists
A new design system, no matter how well-built, is a disruption. Legacy systems are deeply embedded in products and workflows, and teams are busy with their own priorities. Migration projects often fail because they are treated as a purely technical task, ignoring the human factors of resistance, unclear benefits, and conflicting schedules.
The mental model
Think of design system migration not as a technical refactor, but as an internal sales and marketing campaign. Your 'customers' are other product teams. Your goal is to persuade them to 'buy' the new system by demonstrating its value, making adoption easy, and aligning with their existing priorities. Success is measured by voluntary adoption, not just technical completion.
How it works
Migration is rarely a single, big-bang event. It's a series of strategic choices, often mixed and matched. Five common strategies exist. First, the Trojan Horse, where you sneak in new components during regular feature work. Second, Strategic Team Selection, where you partner with enthusiastic teams first to create success stories. Third, Incremental Micro-Adoption, where teams adopt the system in layers, like using design tokens first, then basic components. Fourth, Value-First Communication, which focuses on demonstrating benefits instead of demanding compliance. Fifth, the Start Small strategy, which builds out foundational elements first and then scales.
When to use it
A deliberate migration strategy is critical when replacing a legacy system with high inertia. This is especially true in organizations with autonomous teams, tight budgets, or mixed levels of design system maturity. The Trojan Horse approach works well with no dedicated migration budget. Strategic Selection is ideal for building momentum and creating internal champions. Micro-Adoption is suited for complex applications where a full rewrite is too risky.
When not to use it
A formal strategy is overkill for a brand-new, small-scale project (a 'greenfield' app) where the design system can be adopted from day one. It's also less critical in a small, single-team organization where communication is simple and everyone is already aligned on the new system's value. In these cases, direct adoption is often sufficient.
One canonical example
A common hybrid approach combines the Trojan Horse and Micro-Adoption strategies. A team wants to migrate but has no dedicated time. The design system team first releases only the design tokens (colors, spacing). During their next feature sprint, the product team refactors their CSS to use the new color tokens instead of old hex codes. This is a small, low-risk change piggybacked onto existing work. Later, they can replace a legacy button with the new system's button component in another feature ticket, gradually migrating the app without a dedicated 'migration sprint.'
Interview question
Why is design system migration best approached as an internal 'campaign' rather than a technical mandate?
- a.To primarily reduce the development and maintenance costs of product features.
- b.To enforce strict technical compliance and new coding standards across all teams.
- c.To overcome human resistance and achieve voluntary adoption by demonstrating value.Correct
- d.To ensure a swift, organization-wide, big-bang replacement of all legacy components.
Why? this is the answer
The card states that migration is an 'internal sales and marketing campaign' to 'persuade' product teams to 'buy' the new system by 'demonstrating its value' and achieving 'voluntary adoption.' Option B describes a mandate, which the card advises against, as it ignores human factors.
Just read this? Test yourself on what you have been reading.
Read the original → hdennison.com
- #design systems
- #ui engineering
- #refactoring
- #product management
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on design systems — each one lists the topics its interview covers.
See open roles