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
"There is no such thing as a single issue struggle because we do not live single issue lives — bell hooks."
Angelos ArnisNavigating the Rapid Shifts in Tech's Turbulent Terrain
October 2, 2023
"We are writing the definitive guide because there is no single book dedicated entirely to design ops."
John Calhoun Rachel PosmanBring your DesignOps Story to Life! The Definitive DesignOps Book Jam
October 3, 2023
"Usability testing is the gateway drug for research; similarly, small measurements are the gateway for strategic design impact."
Alfred KahnA Seat at the Table: Making Your Team a Strategic Partner
November 29, 2023
"Queerness taught me that if I didn’t like the rules, I could change the game."
Dan WillisEnterprise Storytelling Sessions
June 3, 2019
"Design ops professionals need to embrace their role as agents of change, supporting others but often facing resistance."
John Maeda Alison RandAbout Design Organizations (Videoconference)
May 13, 2019
"Empathy for us needed to be redefined from problem-based to solution-based to avoid an us versus them mindset."
Anat Fintzi Rachel MinnicksDelivering at Scale: Making Traction with Resistant Partners
June 9, 2022
"Creating tangible artifacts forces reaction and debate, helping break enterprise paralysis and drive decisions."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"2020 was focused on resilience, collaboration challenges, burnout, and attrition during the pandemic."
Kristin SkinnerTheme 1 Intro
September 29, 2021
"The Colab team members didn’t just interview cleaners—they became cleaners for weeks to truly understand issues and design better policies."
Maish NichaniSparking a Service Excellence Mindset at a Government Agency
December 9, 2021
