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
"Participants are paid based on purchasing power parity — $400 USD equivalent spread over six months for active participation."
Wyatt HaymanGlobal Research Panels
August 8, 2020
"Nearly 30 years into my career, I’m doing the most rewarding work of my life helping modernize military space systems."
Michal Anne RogondinoSaving Outer Space: The First UX Design System for Our Nation’s Satellites
January 8, 2024
"We want to be an inspiring friend you go to for advice, not just someone who tells you what to buy."
Sara Asche Anderson Jamie KaspszakNot Your Ordinary Re-Brand: Design's Path to Driving Customer Obsession at Best Buy
January 8, 2024
"Without data, we are just a person with an opinion — you can’t measure performance or impact without data."
Patrizia BertiniDesignOps + KPIs = Measure your Impact!
January 8, 2024
"All organizing is science fiction; it’s about the imaginations we choose to design from."
Amahra SpenceDesigning for Liberation, Rehearsing Freedom
November 18, 2022
"A typical enterprise customer has like five analysts who need a login, not millions of users."
Dan WillisEnterprise Storytelling Sessions
May 13, 2015
"Focus on the destination, not the vehicle, because AI tools will change every single day."
Erika FlowersAI-Readiness: Preparing NASA for a Data-Driven, Agile Future
June 10, 2025
"Telling the right story means creating a memorable shorthand that leaders can reference when they're at other tables."
Dalia El-ShimySo You've Got a Seat at the Table. Now What?
March 31, 2020
"Tagging content as evergreen or setting validity periods helps automate cleaning and maintaining the repository over time."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
