Rosenverse

This video is only accessible to Gold members. Log in or register for a free Gold Trial Account to watch.

Log in Register

Most conference talks are accessible to Gold members, while community videos are generally available to all logged-in members.

Meet Spectrum, Adobe’s Design System

Gold
Wednesday, June 9, 2021 • Design at Scale 2021
Share the love for this talk
Meet Spectrum, Adobe’s Design System
Speakers: PJ Buddhari and Nate Baldwin
Link:

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."

Ask the Rosenbot
Amy Gawronski Zuccaro
Advice for DesignOps Employee #1
2021 • DesignOps Summit 2021
Gold
Kate Towsey
ResearchOps AMA with Kate Towsey & Jake Burghardt
2025 • Advancing Research Community
Sarah Williams
A Framework for CX Transformation
2021 • Design at Scale 2021
Gold
Saara Kamppari-Miller
Theme Three Intro
2023 • DesignOps Summit 2023
Gold
Kate Towsey
Participant Recruitment and Management Tools
2026 • Advancing Research 2026
Gold
Andrew Custage
The Digital Journey: Research on Consumer Frustration and Loyalty
2023 • Advancing Research 2023
Gold
Caroline Vize
The State of UX: Five Lessons from 2021 to Accelerate Digital Experience in 2022
2022 • Advancing Research 2022
Gold
James Rampton
The Basics of Automotive UX & Why Phones Are a Part of That Future
2024 • Rosenfeld Community
Lavrans Løvlie
Ask me anything – Authors of Service Design: From Insight to Implementation
2025 • Advancing Service Design 2025
Gold
Michael Land
Establishing Design Operations in Government
2021 • DesignOps Community
Shivanjali M.
From Fragmented to Fluent: The Linguistic Approach to Research Knowledge
2026 • Rosenfeld Community
Sohit Karol
Designing Delightful Listening Experiences: Mixed Methods Research in the Age of Machine Learning
2020 • Advancing Research 2020
Gold
Amy Marquez
INVEST: Discussion
2018 • Enterprise Experience 2018
Gold
Bria Alexander
Day 1 Panel: Up to the Minute: The latest in AI’s impact on UX
2025 • Designing with AI 2025
Gold
Barb Spanton
Doing Work That Matters: A Look Beyond The Idealistic Notion of 'Doing Meaningful Work'
2022 • Design at Scale 2022
Gold
Sarah Auslander
Incremental Steps to Drive Radical Innovation in Policy Design
2022 • Civic Design 2022
Gold

More Videos

Taylor Jennings

"Setting up a repository as a team of one or two is actually the prime time to establish processes like that."

Taylor Jennings Joe Nelson Alex Knoll

Repository Retrospective: Learnings from Introducing a Central Place for UX Research

March 9, 2022

Nicole Aleong

"We have a role to play in democratizing the future and amplifying more visions of what that future can hold."

Nicole Aleong

Future Orientations to Everyday Life: Futures Anthropology as a Methodology

March 26, 2024

Jeff Gothelf

"Innovation is not a spice that you sprinkle on and suddenly magical new things come out."

Jeff Gothelf

Innovation Studios: the Engines of Enterprise Experimentation

May 14, 2015

Saara Kamppari-Miller

"If you don't have dedicated accessibility people, start grassroots by building empathy and rallying teams around user stories."

Saara Kamppari-Miller

DesignOps for Inclusive Design and Accessibility

May 26, 2022

Tess Dixon

"You can’t make your team happy, no one can ever make anyone else happy ever, ever."

Tess Dixon

C'mon Get Happy

September 29, 2021

Liam Thurston

"Our skills matrix became the center of gravity for our practice—it started writing job descriptions and guiding recruitment."

Liam Thurston

Why Your Design Team Is Quitting, And How To Fix It

June 10, 2022

Ian Swinson

"It’s huge to have a framework so managers and employees speak the same language around skills and growth."

Ian Swinson

Designing and Driving UX Careers

June 8, 2016

Leisa Reichelt

"If you make rules, put numbers in them, and say them confidently, sometimes people actually do them."

Leisa Reichelt

Opening Keynote: Operating in Context

November 7, 2018

Rachael Greene

"Getting to know someone as a person first—the vibe check—is the first step to successful UX research collaboration."

Rachael Greene Alison Davis

Building a Design Ops Practice that Really Works (Most of the Time)

October 2, 2025