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
"Resiliency for me is not really a professional thing. It’s a lot more personal."
Jennifer KanyamibwaCreating the Blueprint: Growing and Building Design Teams
November 8, 2018
"Maintaining a repo often requires 100% manual participation from researchers and that can be hard to enforce and monitor."
Brigette Metzler Dana ChrisfieldResearch Repositories: A global project by the ResearchOps Community (Videoconference)
August 27, 2020
"Taking meeting minutes and assigning action items with director names reduced arguing and helped move things forward."
Carl TurnerYou Can Do This: Understand and Solve Organizational Problems to Jumpstart a Dead Project
March 28, 2023
"Trust, facilitation, change, and complexity—if you wrap your mind around those, you’ll get reasonably far."
John Mortimer Milan Guenther Lucy Ellis Patrick QuattlebaumPanel Discussion
December 3, 2024
"Information overload with checklists on top of checklists does not create a great onboarding experience."
Dante GuintuHow to Crush the Talent Crunch
September 8, 2022
"Principle is an idea or value that gives unity and organization to a product, system, service, and human experience."
Richard BuchananCreativity and Principles in the Flourishing Enterprise
June 15, 2018
"Melinda Belcher has had great success first as an outside consultant and then as an inside enterprise manager."
Dan WillisTheme 3: Intro
January 8, 2024
"We study failure without blame; this is the path to progress."
Dan WardFailure Friday #1 with Dan Ward
February 7, 2025
"Researchers are positioned at the nexus of insight and action."
Chris GeisonTheme Two Intro
March 28, 2023