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."
Or choose a question:
More Videos
"Iteration means don’t prepare your talk the night before. Start early, practice, and evolve your message over time."
Louis Rosenfeld Jemma Ahmed Christian Crumlish Uday Gajendar Chris GeisonCoffee with Lou #3: What Makes for a Successful UX Conference Presentation?
May 2, 2024
"We share the inconvenience of meeting times across time zones, alternating so no one team always bears it."
Jilanna WilsonDistributed Design Operations Management
October 23, 2019
"Mini apps might not be useful for you, but they are for someone, and now those people can have them."
Matt WebbContext Window: Five Futures for AI
June 11, 2025
"Accessibility features like voice assistants and captions make the world better for everyone, not just people with disabilities."
Sam ProulxAccessibility: An Opportunity to Innovate
September 8, 2022
"EMRs and EHRs have terrible user experience and are ripe for design innovation, similar to FinTech years ago."
Theresa NeilDesigning for Wellness: Specializing in Healthcare
May 22, 2024
"Evals are everywhere, right? Everybody's talking about evals. It is like one of the key things in developing useful AI products."
Peter Van DijckHands-on AI #2: Understanding evals: LLM as a Judge
October 15, 2025
"How are executives going to invest in you if you don’t show the work? If they can’t see it, they won’t invest."
Rachel Posman John Calhoun"Ask Me Anything" with Rachel Posman and John Calhoun, Authors of the Upcoming Rosenfeld Book, The Design Conductors
September 25, 2024
"Building trust across functions means simple acts like scheduling lunch or coffee meetings with no agenda."
Tricia WangThe most popular design thinking strategy is BS
January 27, 2022
"Civic action as proof of concept to get government moving, to get the wheels turning was really interesting."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
