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
"Legacy interconnected systems mean improving one area can create problems in another, and we don't always know those constraints upfront."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"Our offices have stand-up desks, nice collaboration areas, and comfy seating with a fresh, on-brand look."
Jen Crim Jess Quittner Saritha Kattekola Alex Karr Gurbani PahwaCulture, DIBS & Recruiting
June 11, 2021
"Critique sessions work best when the topic is shaped so answers are relevant and help the process, especially by including business goals."
Christian CrumlishAMA with Christian Crumlish, author of Product Management for UX People
March 24, 2022
"Maybe I too had joined another tech company that really wasn’t walking the walk when it came to diversity."
Libby MaurerTreating Diversity & Inclusion in Hiring as a Design Problem
December 5, 2019
"Sustainability is not just about the environment, it’s about community."
Ali Jeffery Sheri ChudowHow DesignOps Helped Enable Wall Street to Work Remotely
October 22, 2020
"You can’t know a human honestly from the outside alone; you have to let their reality work on you."
Daniel GloydDesigning From the Inside Out: How Method Acting Can Inspire Design Research
February 12, 2026
"Learning should be an experience tailored around the learner, not the curriculum."
Kristin SkinnerFive Years of DesignOps
September 29, 2021
"The most significant source of confusion is the difference between research questions and interview questions - Erica Hall."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"When you observe a quantum particle, its possible states collapse to one—just like user intent collapses to action."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
Latest Books All books
Dig deeper with the Rosenbot
How do I handle credibility challenges and emotional barriers when working with medical professionals?
What strategies help speed up the procurement and legal review of UX research platforms in organizations like LinkedIn?
Where can UX researchers find reliable, up-to-date information and recommendations on research tool options?