Meet Spectrum, Adobe’s Design System
Summary
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."
Or choose a question:
More Videos
"We must not only fix today’s problem but also foresee what the future holds to build the best playground for our teams."
Ebru NamaldiDesigning the Designer’s Journey: Scaling Teams, Culture, and Growth Through DesignOps
September 11, 2025
"Early inclusion is less costly and more effective than retrofitting accessibility later."
Samuel ProulxInvisible barriers: Why accessible service design can’t be an afterthought
December 3, 2024
"People really hated using Harvest to log billable hours, some just put the same hours week after week."
Kristin Skinner Kamdyn MooreGroup Activity: A Deep Dive Into Value and Outcomes
October 23, 2019
"Empathy means constantly going back to the people using the tools and hearing their feedback."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
"Organize synthesis before the research happens by aligning on themes and goals with moderators and track leads."
Smitha Papolu Nova Wehman-Brown Melissa Schmidt Adam MenterTheme 3 Discussion
June 4, 2019
"In one project, a design change required approval from 32 people, which clashed with my low value on authority."
Ellen ChisaThe Values of Design
November 29, 2023
"Performative equity occurs when an organization advocates for DEI but there’s no practical action being undertaken."
Zariah CameronStreamlining an Inclusive Design Practice
October 3, 2023
"Inclusion is an opportunity to build relationships rather than create division."
Saara Kamppari-MillerTheme Three Intro
September 9, 2022
"As a design ops manager, I try to alleviate decision fatigue for design managers so they can focus on the decisions that need their input."
Michelle ChinThe DesignOps Starter Kit
September 29, 2021
