Meet Spectrum, Adobe’s Design System
Summary
We built Adobe’s design language, Spectrum, to work on a huge and varied product ecosystem. Adobe’s offering includes dozens of connected desktop, web, and mobile experiences with millions of worldwide users. Some of our products are brand new and some have been in the market for decades. Hear from two of Spectrum’s designers as they give an overview of the design system and answer your questions about building and scaling a design system!
Key Insights
-
•
Spectrum supports over 130 Adobe products across three business units and multiple platforms, requiring a highly scalable and flexible design system.
-
•
The design team does not implement components directly; implementation is handled by separate engineering teams, necessitating strong cross-team collaboration.
-
•
Spectrum evolved from occasional quarterly versions to individual component versioning, improving change tracking and prioritization by implementation teams.
-
•
A transparent design checklist tracks component quality and health with open issues linked to Jira tickets to prioritize fixes and improvements.
-
•
Spectrum Contributions is a sister site hosting 110+ work-in-progress components, increasing visibility and community feedback outside the core team.
-
•
A design token repository serves as a single source of truth for all component attributes like color and sizing, ensuring consistency and ease of updates.
-
•
Nate Baldwin highlights naming as the hardest ongoing challenge due to multiple platforms and diverse teams; content strategist Jess Satel assists in establishing a clear terminology.
-
•
Spectrum balances consistency and respect for platform-specific UI conventions by either skinning native components or documenting deviations explicitly.
-
•
Accessibility and color theming are managed by defining target contrast ratios first, then generating compliant colors via the custom tool Leonardo.
-
•
The Spectrum team fosters community via multiple engagement channels including Spectrum Guild quarterly meetings, town halls, office hours, and Slack, improving documentation and prioritization.
Notable Quotes
"Our team does not actually build the components consumed by product teams. Implementation teams report to their respective engineering and product orgs."
"We moved from versioning the entire system quarterly to individually versioning components, so changes are easier to track and prioritize."
"Naming things — components, properties, parts — is the hardest thing and it never stops. Thankfully, we have Jess Satel, our amazing content strategist."
"We try to keep things as consistent as possible in terms of the API but document where platforms need to deviate to be good citizens of their environment."
"Instead of choosing colors then checking contrast, we flipped the process and started by defining contrast ratio targets and then generating colors to meet them."
"We capture component design decisions and health transparently with checklists; unchecked items correspond to open tickets for prioritization."
"We have weekly meetings with implementation teams to design APIs, discuss progress, and address issues to ensure alignment."
"Spectrum Contributions site gives visibility to work-in-progress components, making users more vocal with feedback that we can capture and raise."
"Our UI kits are generated through JavaScript based on tokens, meaning less manual work, fewer errors, and consistent updates across themes and platforms."
"Spectrum is about empowering collaboration across products, disciplines, and clouds — not just providing tools but supporting people using the system."
Or choose a question:
More Videos
"Setting up a repository as a team of one or two is actually the prime time to establish processes like that."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"We have a role to play in democratizing the future and amplifying more visions of what that future can hold."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"Innovation is not a spice that you sprinkle on and suddenly magical new things come out."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"If you don't have dedicated accessibility people, start grassroots by building empathy and rallying teams around user stories."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"You can’t make your team happy, no one can ever make anyone else happy ever, ever."
Tess DixonC'mon Get Happy
September 29, 2021
"Our skills matrix became the center of gravity for our practice—it started writing job descriptions and guiding recruitment."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"It’s huge to have a framework so managers and employees speak the same language around skills and growth."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"If you make rules, put numbers in them, and say them confidently, sometimes people actually do them."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"Getting to know someone as a person first—the vibe check—is the first step to successful UX research collaboration."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
