Meet Spectrum, Adobe’s Design System
Summary
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
"In India, a cow crossing the road can disrupt Uber pickups, showing the need to design with local realities in mind."
Nancy DouyonWe'll Figure That Out in the Next Launch: Enterprise Tech's Nobility Complex
June 15, 2018
"Using Merge we’re closing the loop of documentation and empowering stakeholders to communicate via common jargon and components."
Jack BeharHow to Build Prototypes that Behave like an End-Product
December 6, 2022
"Confusing product portfolios often arise when two successful teams’ products overlap, complement, or have vague distinctions."
Jorge ArangoMeeting of the Waters: Designing for Successful Inorganic Growth
August 12, 2021
"If you’re in a big company, think smaller to work bigger — narrow your focus rather than get distracted by every shiny tool."
Jon White Erin MayUnsticking Research for Better Information Flow
March 11, 2026
"Give a why of why you’ve made this design decision. It helps your team understand and reduces defensiveness."
Jessamyn EdwardsSurviving Your UX Career in Enterprise Design
December 2, 2021
"Designers embedded alongside technical teams can spot unseen issues in the spaces between operational silos."
Stefanie OwensOptimizing for Outcomes: Transformation Design in Systems at Scale
December 4, 2024
"Attention theft is when experiences are designed to siphon away your focus aggressively."
Ron BronsonDesign, Consequences & Everyday Life
November 18, 2022
"Slack is growing steadily for us, but it’s hard to moderate and expensive at scale."
Louis RosenfeldThe Rosenbot and the Rosenverse: An AMA with Lou Rosenfeld
June 5, 2024
"Collaboration is not just beneficial, it's essential for effective climate action."
Ash BrownSilver Linings: What DesignOps Learned in the Shift to WFH
October 23, 2020
Latest Books All books
Dig deeper with the Rosenbot
How do product risk categories like feasibility, viability, desirability, and usability relate to research method choice?
How might activism in the tech industry evolve given today's power imbalances among AI corporations?
What is the Neural Transmission System project and how does it invert typical human-AI art interaction?