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
"Visual process maps embody cognition and allow people to step through design without becoming experts."
Surya VankaUnleashing Swarm Creativity to Solve Enterprise Challenges
June 10, 2021
"The economies of scale that benefited traditional media organizations have disappeared."
Patrick Boehler Madison KarasThe service shift: transforming media organizations to create real value through design
November 19, 2025
"The pandemic pushed us to be creative, and it’s been fun for users to participate remotely in the design process."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"We have a moral duty to bring global conversations back to local communities to increase diversity and richness."
Patrizia Bertini Alexandra Mengoni LeónPushing DesignOps’ Influence into New Global Markets
September 9, 2022
"Design thinking is the scientific method for the 21st century."
Phil GilbertA Consistent Culture of Design
May 14, 2015
"This is a hero moment because it accelerates and simplifies exploration of clustering options."
Yulya Besplemennova[Demo] Stress-testing GenAI in user research synthesis
June 4, 2024
"Remote is a design constraint, but what else can we do with it to improve practice?"
Sarah RinkRemote User Research: Dos and Don'ts from the Virtual Field
June 11, 2020
"We experimented with AI-powered sprints, but had lots of dead ends and false starts before finding what really works for us."
Mujtaba HameedThe new horizon of ethnography: using AI to unlock the full potential of in-person research
March 11, 2026
"Optimizing something for ease of use does not mean best for the user or humanity."
Sheryl CababaLiving in the Clouds: Adopting a Systems Thinking Mindset
June 6, 2023
