Summary
Defining a design system that’s adaptable, modular and more importantly, future proof, is a monumental task. With several years of contributing to their design system and software suite, Mitchell Bernstein, AI Design Lead, will go through IBM’s experience on this topic, sharing key takeaways about their evolving Carbon Design System. Mitchell will also dive into details on how to adapt any design system to complex, AI-powered software with the help of Sketch.
Key Insights
-
•
IBM's Carbon design system is supported by a governance model that includes a small core team, asset guild contributors from product teams, and an implementation team to maintain priorities and quality.
-
•
Design systems are more than code; they are a language of implementation involving people, guidelines, design tools, and shared decisions evolving over time.
-
•
Many IBM designers previously created unique buttons for products, creating chaos; Carbon design system solved that by standardizing reusable components.
-
•
Five principles guide the creation of UX patterns: user needs, reproducibility, consistency, flexibility, and extendability.
-
•
Sketch was pivotal in scaling IBM’s design system by enabling editable component libraries and making design language mutable and accessible.
-
•
Design systems typically cover 80-95% of use cases; product teams need permission and guidance to break or extend the system to solve unusual problems.
-
•
Injecting controlled 'chaos' or experiments beyond the design system can lead to improvements incorporated back into the system, as demonstrated by motion design innovations.
-
•
IBM approaches emerging technologies like AI through design thinking—starting with observation and prototyping to learn and iterate, accepting discomfort as necessary for growth.
-
•
The Watson Moments design system was created to facilitate AI integration into existing products and includes ethics components to check biases in AI models.
-
•
Clear communication and shared tooling platforms like Sketch are essential for effective collaboration across design, development, and product teams, reflecting team success in the product.
Notable Quotes
"Design systems are the language of implementation; they communicate ideas in a common format and process."
"Previously, designers were inventing their own buttons for each product, exasperating chaos and frustration for developers."
"Carbon is just the starting point for what can be imagined; we’re hired for our expertise to adapt, not just follow directions."
"You have to admit we don’t know everything, we have to ask each other and ask our users, so we can learn together."
"Discomfort and growth cannot coexist — to innovate monumentally, you need to embrace discomfort."
"Sketch was the first to make it possible to build a scalable library for thousands of products and millions of customers."
"When the design system doesn’t cover 100% of use cases, product teams must decide when and how to break from it."
"We’re literally using AI to help AI build AI — with systems detecting bias and asking for user confirmation before proceeding."
"The product is the reflection of how well teams communicate."
"If the pattern isn’t solving a real user need across multiple products, stop working on it."
Or choose a question:
More Videos
"Innovation in conservation practices is desperately needed to keep pace with environmental changes."
Alex Hurworth Bonnie John Fahd Arshad Antoine MarinDesigning a Contact Tracing App for Universal Access
October 23, 2020
"We started to ask ourselves, does every new Design Ops practitioner need 10 years of experience like Lisa and I? What opportunities are we missing by not having more junior roles?"
Laine Riley Prokay Lisa GordonCarving a Path for Early Career DesignOps Practitioners
September 9, 2022
"We stopped talking about patterns and consistency and started talking about scalability and speed to connect with stakeholders."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Rather than aiming for the chief strategy officer directly, build relationships with junior strategists who are more accessible."
Nathan ShedroffDouble Your Mileage: Use Your Research Strategically
March 31, 2020
"You can just pick up your phone and start testing accessibility instantly without procurement or licensing hurdles."
Sam ProulxMobile Accessibility: Why Moving Accessibility Beyond the Desktop is Critical in a Mobile-first World
November 17, 2022
"Product and design teams are usually the best initial stakeholders to engage for rapid research programs."
Feleesha SterlingBuilding a Rapid Research Program (Videoconference)
May 18, 2023
"Brand and product become two sides of the same coin when user insights have a seat at the top table."
Neil BarrieWidening the Aperture: The Case for Taking a Broader Lens to the Dialogue between Products and Culture
March 25, 2024
"A well framed project is a rare thing — it’s also a creative exercise that unleashes teams’ possibilities."
John DevanneyThe Design Management Office
November 6, 2017
"It’s not about the specific tool, but about how you expose people to the insights in a way that excites them."
Katy MogalBut Do Your Insights Scale?
March 12, 2021