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
-
•
Design systems at IBM function as an evolving language connecting decisions across teams and products, enabling consistent yet adaptable experiences.
-
•
Governance of IBM's Carbon design system includes core maintainers, design systems asset guilds, and an oversight implementation team ensuring quality and priorities.
-
•
Five principles guide pattern creation: focus on user needs, reproducibility, consistency, flexibility, and extendability to maintain effectiveness over time.
-
•
Sketch was pivotal in IBM's ability to build scalable, reusable component libraries accessible to thousands of products and millions of users.
-
•
Product teams must know when to break away from the design system to address unique use cases, injecting controlled innovation back into the system.
-
•
IBM uses the loop cycle—observe, reflect, make—as a fundamental process for tackling unknown technology and user needs iteratively.
-
•
The complementary Watson Moments design system helps integrate experimental AI features into existing digital products alongside the core Carbon system.
-
•
AI ethics are prioritized through dedicated educational modules to prepare designers and developers for the responsibility of AI decision-making on users.
-
•
Automated AI tools like AutoAI include bias detection and correction mechanisms, designed through detailed Sketch visualizations by IBM's design team.
-
•
Effective communication across multidisciplinary teams using shared tools like Sketch is critical as product quality reflects the quality of team collaboration.
Notable Quotes
"Design systems are the language of implementation; they allow us to communicate ideas in a common format and process."
"Every decision in a design system is like a puzzle piece; together they form a bigger picture that evolves over time."
"Previously, IBM designers were inventing their own buttons for every product, which exasperated chaos and inconsistency."
"Carbon is just the starting point for what can be imagined. We're hired for our expertise to adapt, not just follow directions."
"Discomfort and growth cannot coexist. You have to embrace discomfort to push innovation forward."
"When you get stuck, fall back to the loop: observe, reflect, and make. Get out and talk to users."
"Sketch made it possible to build a scalable library that millions of customers rely on with just a couple clicks."
"AI decision-making on behalf of billions of people isn’t just scary; it’s terrifying and dangerous, so ethics must be embedded."
"We’re literally using AI to help AI build AI, including bias detection and correction in the process."
"The product is the reflection of how well teams communicate. Without clear communication, success is impossible."
Or choose a question:
More Videos
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
"Change is messy and it can be uncomfortable, much like baking bread—it’s hard to imagine sticky dough turning into a perfect loaf."
Amy EvansHow to Create Change
September 25, 2024
"Too many companies wait until they think they know the solution to a problem and then they engage design as if design's only job is to make something look pretty."
Catt SmallMoving from Execution to Strategy as a Designer
December 6, 2022
"People are individuals first and part of communities second, which adds complexity to designing effective personas."
Lija HoganContexts of Use: A Framework for Connection
December 9, 2021
"A product mindset is still essential but brings limitations and blind spots we need to address with service thinking."
Tim ParmeeChanging Our Design Pressure Points
October 2, 2023
"Launching and shipping things is a big deal and shows real impact beyond metrics."
Dave Hoffer Joanne WeaverUX Job Search AMA #2 with Joanne Weaver and Dave Hoffer
April 3, 2025
"Product designers I have worked with have experience deeply grounded in standards like NIST, ISO, IEEE, and HL7 for healthcare."
Noreen Whysel Katie SaindonShort Take #4: UX/Product Lessons from Your Industry Peers
December 6, 2022
"How you make service is part of what you make; functionality and operability become one inseparable experience."
Jeff SussnaWhat DesignOps Can Learn From DevOps
November 6, 2017
"Researchers are becoming stewards of organizational wisdom, not just collectors of insight."
Eduardo OrtizTheme 3 Intro
March 13, 2025
Latest Books All books
Dig deeper with the Rosenbot
How can research and operations teams collaboratively evaluate new UXR tools for usability and operational fit?
What hidden costs should be accounted for beyond license fees when budgeting for research tools?
Why is it acceptable to prioritize empathy over methodological rigor in certain research contexts?