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
"I’ve nearly bought products in my sleep because I memorized the key presses from consistent checkout flows."
Sam ProulxOnline Shopping: Designing an Accessible Experience
June 7, 2023
"We’ve had to retire the studio development category because it wasn’t prioritized due to project work demands."
Ignacio MartinezFair and Effective Designer Evaluation
September 25, 2024
"Stakeholders saw design as a slow-moving black box — exactly what we were trying to move away from."
Sarah Kinkade Mariana Ortiz-ReyesDesign Management Models in the Face of Transformation
June 8, 2022
"The Shakers’ principled approach to design was a precursor to Bauhaus’s form follows function and today’s user-centered values."
Daniel GloydWarming the User Experience: Lessons from America's first and most radical human-centered designers
May 9, 2024
"Structure beats free form interaction—systematic query frameworks are essential to avoid pitfalls."
Patrick BoehlerFishing for Real Needs: Reimagining Journalism Needs with AI
June 10, 2025
"Providing stakeholders with real user voices alongside insights is key to internalizing and acting on research."
Andy Barraclough Betsy NelsonFrom Costly Complexity to Efficient Insights: Why UX Teams Are Switching To Voxpopme
September 23, 2024
"Technology moves faster than policymaking — that’s the pacing problem we need to address."
Alexandra SchmidtWhy Ethics Can't Save Tech
November 18, 2022
"Strategic friction is about where you apply friction deliberately to create insight and transformation."
Louis RosenfeldDiscussion: What Operations can teach DesignOps
November 6, 2017
"Sketch made it possible to build a scalable library that millions of customers rely on with just a couple clicks."
Mitchell BernsteinOrganizing Chaos: How IBM is Defining Design Systems with Sketch for an Ever-Changing AI Landscape
September 29, 2021
