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
"Either you need accessibility now or you will need accessibility in the future."
Sheri Byrne-HaberAccessibility at Scale
June 9, 2021
"Data tells you what happens; qualitative research tells you why it happens."
Prayag Narula Hannah HudsonEmpowering Designers to do Good Research
March 11, 2022
"The hardest skill to recruit for is someone who can consult and ask the right questions to uncover what the request really is."
Janelle EstesUX Research Trends
January 28, 2021
"User research is a validation function is a common pitfall, but its real power is uncovering meaningful insights early."
Craig Brookes Andreas Huebner Morgan Quinn"Just Make it Look Good" and Other Ways We're Misunderstood
June 11, 2021
"We encourage one-to-one video calls to build rapport and feel comfortable reaching out for advice."
Marc Fonteijn Ru ButlerIncrease your confidence, influence, and impact (through a Professional Community)
December 3, 2024
"Managing vendors is a full-time job, and research ops teams often coordinate numerous vendors for tools and recruitment."
Kate TowseyThe State of ResearchOps: More Than Just Theory
June 20, 2019
"Our nervous system is ancient; it can’t tell the difference between an angry email and a tiger lurking."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 9, 2022
"The collaboration cycle requires following standards for accessibility, content, design system usage, and IA or you don’t launch your product."
Shawna Hein Kevin HoffmanCreate a Cohesive Civic Design Practice Across Agency, Vendors, and Contracts
November 17, 2022
"Positive mutual regard helps uncover root causes behind people’s behaviors to build collaboration rather than combat."
Tricia WangSCALE: Discussion
June 15, 2018
Latest Books All books
Dig deeper with the Rosenbot
How can research repositories score or show the impact of research recommendations to enhance organizational learning?
How can research enablement free up time for researchers to focus on high-level strategic questions?
How can lifelong learning be incorporated as a core principle of design education and beyond?