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
"Have you just asked what scares us or keeps us up at night? Those repeated fears highlight the risks we need to avoid."
Christian Crumlish Wendy Johansson Rich Mironov Aditi Ruiz Adam ThomasAfternoon Insights Panel
December 6, 2022
"Government is seven plus years behind industry – not bleeding edge, more like the dull butter knife edge."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"Slack is the heart and soul of this conference, where the most intimate interactions happen."
Bria Alexander Louis RosenfeldWelcome
September 8, 2022
"Embedding process knowledge directly into work surfaces helps teams unpack and collaborate effectively."
Surya VankaUnleashing Swarm Creativity to Solve Enterprise Challenges
June 10, 2021
"Share early, share ugly—that’s our mantra for this entire process."
Cassandra PiesterDeveloping and Deploying Your Design Operations Strategy
September 24, 2024
"Yesterday we saw themes emerge on striving for inclusion, applying equity and sustaining the work over time."
Ariel KennanTheme 2 Intro
December 9, 2021
"If a security camera were recording, what would they see? Focus on facts, not stories."
Joshua GravesWe Need To Talk: Navigating Conversations with Your Boss (Part 1 of 3)
April 14, 2025
"An agent is a model using tools in a loop, making plans, reasoning, and calling tools until it’s done."
Peter Van DijckBuilding impactful AI products for design and product leaders, Part 3: Understand AI architectures: RAG, Agents, Oh My!
July 30, 2025
"Sponsor sessions are completely free and offer content just as valuable as the main program sessions."
Bria AlexanderOpening Remarks
November 17, 2022