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
"Innovators can listen to what is unsaid."
John MaedaMaking Sense of Enterprise UX
June 9, 2016
"Demographics don’t cause thinking; they can exacerbate discrimination, but for everything else, they've lost context."
Indi YoungThinking styles: Mend hidden cracks in your market
January 8, 2025
"Collaboration between data teams and design teams can create delightful experiences for customers."
Chris ChapoData Science and Design: A Tale of Two Tribes
May 13, 2015
"Effective teams integrate across silos to enhance productivity."
Elizabeth ChurchillExploring Cadence: You, Your Team, and Your Enterprise
June 8, 2017
"I love experiences. I love designing them and I love experiencing them."
Rusha SopariwalaRemote, Together: Craft and Collaboration Across Disciplines, Borders, Time Zones, and a Design Org of 170+
June 9, 2022
"Human-centered design makes you feel like we're centering on humans, but that is not always true."
George AyeThat Quiet Little Voice: When Design and Ethics Collide
November 16, 2022
"Every once in a while, it's okay to turn your video off."
Ariba JahanTeam Resiliency Through a Pandemic
January 8, 2024
"Being a design educator rather than just a designer helps teams collaborate effectively."
Julie Gitlin Esther RaiceDesign as an Agent of Digital Transformation at JPMC
June 9, 2021
"The greater part of progress is the desire to progress again."
Matteo GrattonCan Data and Ethics Live Together?
October 1, 2021
