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
"Daniel Day-Lewis went so far as to suffer three broken ribs immersing in his role for My Left Foot."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Without good relationships, you won’t get good data. And without good data, you won’t have good project outcomes."
Deirdre Hirschtritt Cesar Paredes Marie PerrotResearch is Only as Good as the Relationships You Build
November 17, 2022
"We finally instead of using the compass and the map we finally were able to build a GPS."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"You can look at a company’s impact reports and funding sources to sniff out if something feels too good to be true."
Max Gadney Andrea Petrucci Joshua Stehr Hannah WickesAssessing UX jobs for impact in climate
August 14, 2024
"Rob Meetzel knows Ford as the back of his hand after nearly 30 years."
Lada GorlenkoTheme 1: Intro
January 8, 2024
"I asked myself, will I take the leap or will I take permission? And this gamble paid off."
Feyikemi AkinwolemiwaPlay to innovate: How curiosity and experimentation transform UX
March 11, 2026
"If you have a question at the end of a presentation, please put that question in the thread associated with the talk."
Bria AlexanderOpening Remarks
March 29, 2023
"Synthetic duplicates living on after data deletion raise ethical questions about users’ right to be forgotten."
Llewyn Paine[Demo] Deploying AI doppelgangers to de-identify user research recordings
June 5, 2024
"OKRs are not one-size-fits-all; you have to shape them based on your organizational context and culture."
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
