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 spanning multiple platforms and business units with diverse technologies.
-
•
The design system evolved from a few Adobe designers managing Illustrator files to a dedicated cross-functional team since around 2015.
-
•
Spectrum’s team focuses on design, documentation, and defining tokens but relies on product engineering teams for component implementation.
-
•
Component health is tracked transparently using a design checklist linked to open tickets to prioritize fixes.
-
•
Spectrum shifted from quarterly global versions to individual component versioning for more granular updates and smoother communication.
-
•
Spectrum Contributions is a sister site showcasing design work-in-progress components to gather community feedback early and increase visibility.
-
•
Design tokens serve as a single source of truth for attributes like color and sizing, enabling theme flexibility and consistent UI kit generation.
-
•
Leonardo, a tool developed by Nate Baldwin’s team, automates generating accessible color palettes by targeting specific contrast ratios across themes.
-
•
Naming components and their properties precisely is the toughest challenge, addressed by working closely with a content strategist, Jess Satel.
-
•
Spectrum maintains strong collaboration with multiple engineering teams through weekly meetings, office hours, and Slack channels to synchronize design decisions and implementation feedback.
Notable Quotes
"Our team does not actually build the components consumed by product teams due to how Adobe's teams are structured."
"We use a design checklist to show the health of each component, leaving items unchecked if they don't meet standards."
"Naming things is the hardest thing; it’s an ongoing process involving components, their parts, and properties."
"We investigate whether we can skin native components to respect platform conventions while identifying commonalities and differences."
"Instead of choosing colors and then checking contrast, we define target contrast ratios first and generate colors accordingly."
"Leonardo helps generate color palettes that meet contrast requirements, ensuring accessible themes."
"Our UI kits are generated through JavaScript from design tokens, reducing manual errors and keeping everything up to date."
"We have a Spectrum Guild that includes product designers and managers from every business unit to surface major changes and requests."
"We hold quarterly town halls and office hours to keep the community informed and supported."
"We’re far from done; evolving foundational elements, accessibility, and customization tools will drive Spectrum’s future."
Or choose a question:
More Videos
"Many designers feel overwhelmed by hundreds of expected skills, which creates paralysis about where to focus."
Shaping design, designers and teams
November 8, 2018
"Selling the design system’s value continuously, especially as new teams and components are added, is essential."
Sabrina Mach Nina WainwrightHow to Design Your Design Operating Model
September 29, 2021
"People are disabled by environments, processes, or systems, not by their own bodies or minds."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"Starting with a small project builds momentum and shows results that help get funding and organizational buy-in."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility (Videoconference)
May 26, 2022
"Product design and development can often mirror what happens in a chef’s kitchen: lots of coordination and spinning plates behind the scenes."
Briana ThomasThe Quiet Force: Uncovering Hidden Leadership in High-Impact Design Teams
September 24, 2024
"I wish I could tell my 22-year-old self what to stop doing and what to embrace to be a better designer."
Adam Cutler Karen Pascoe Ian Swinson Susan WorthmanDiscussion
June 8, 2016
"We had to partner closely with information security to ensure every piece of data in research files was tracked and compliant."
Operationalizing DesignOps
November 7, 2018
"Executives see research value when they’ve lost money on bad bets and want to mitigate risk for future decisions."
Leah Buley Joe NatoliAsk Me Anything with Leah Buley and Joe Natoli, co-authors of The User Experience Team of One (2nd edition)
October 8, 2024
"Strategy should be continuous, circular, and evolve with every action the organization takes."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020