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
-
•
Adobe's Spectrum supports a vast portfolio of over 130 products across multiple business units and platforms.
-
•
The design system began organically and was formalized in 2015, allowing for improved structure and teamwork.
-
•
Key challenges include naming components effectively to accommodate diverse user mental models and frameworks.
-
•
Spectrum prioritizes documentation to capture design decisions and provides transparency on component health and evolution.
-
•
Accessibility is a core commitment, with tools like Leonardo ensuring color contrast ratios meet standards for inclusivity.
-
•
The system allows for flexible theme support, ensuring usability across various platforms while respecting their conventions.
-
•
Spectrum encourages community engagement through town halls and office hours, fostering collaboration and feedback.
-
•
The team employs a decentralized approach to implementation, working closely with various product teams to ensure design fidelity.
-
•
Regular iterations and updates to components are part of Spectrum's living system, adapting to changing user needs and technologies.
-
•
Continuous evolution is needed to address gaps in functionality and enhance user experiences across Adobe's offerings.
Notable Quotes
"Spectrum is a living and breathing thing that will evolve over time."
"Naming things is the hardest part of managing a design system."
"We had to learn to work smarter, not just harder, to support Spectrum."
"Our team does not actually build the components consumed by product teams."
"We document every design decision and capture open issues related to components."
"Using design tokens helps us avoid duplication and customization errors across products."
"We've established a strong working relationship with implementation teams to better define and improve our libraries."
"We now have over 110 components in spectrum contributions, which increases visibility and feedback."
"Our priority is placing customer needs first in every aspect of our design."
"Spectrum makes it a priority to support multiple themes while ensuring accessibility and inclusivity."
More Videos
"We are definitely kind of feeling out some phases."
Jacqui FreyFlow and Superfluidity for Design Orgs
November 7, 2018
"Human connection is a basic and evolutionary need; without it, we struggle to foster resilience."
Laura Gatewood Laine ProkayBeyond Buzzwords: Adding Heart to Effective Slack Communication
September 23, 2024
"The product leadership doesn't see the value in research and they're thinking about shutting the research team down."
Johanna KollmannInsights-Driven Product Strategy: Get your Research to Count
December 6, 2022
"We will absolutely promise to let you know when these resources are available for you to enjoy."
Bria AlexanderDay 3 Welcome
September 25, 2024
"Designing for an edge case can benefit everyone."
Billy CarlsonIdeation tips for Product Managers
December 6, 2022
"It's easy to stay immersed in digital, but physical contexts matter immensely for designing multi-channel experiences."
Catherine DubutBridging Physical and Digital Spaces: Approaches to Retail Service Design
March 18, 2021
"Onboarding processes should empower new hires to integrate smoothly into the team."
Kim Holt Emma Wylds Pearl Koppenhaver Maisee XiongA Salesforce Panel Discussion on Values-Driven DesignOps
September 8, 2022
"Be curious, understand what other people's experiences have been."
Adrian HowardSturgeon’s Biases
September 25, 2024
"It's important to assume positive intent."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
