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."
Dig deeper—ask the Rosenbot:
More Videos
"Research is about being ready for anything, even what you didn’t imagine."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"Keep your LinkedIn profile updated and compelling so you’re findable for passive job opportunities."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Driver modeling tells you which research initiatives matter most based on their impact on key outcome metrics."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Surprisingly, when nudging vaccines, consumers preferred seeing every eligible vaccine listed, even controversial ones like COVID-19."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Human behavior is anything but linear, rational, or predictable."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"Not everything that is faced can be changed, but nothing can be changed until it is faced."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Hiring for lived experience, not just academic credentials, changes the game."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Around 14 to 20 designers is usually the tipping point where having a dedicated design ops person starts to make sense."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"In large complex systems, the dots are scattered across silos and time zones, making progress feel elusive."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
