Design Systems Report 2026 - Adoption as an existential challenge
7
4:00 PM - 5:00 PM
Only 38% of design systems achieve wide adoption. For the rest, it's the problem that won't go away.
You can build the most elegant component library in the world — but if nobody uses it, does it matter? The DSR 2026 data reveals that adoption remains the existential challenge for design systems: 40% of teams are dissatisfied with organizational buy-in, "lack of resources" is the #1 challenge by a wide margin, and 61% of teams say they simply don't have enough people to do the job. Design systems are being asked to prove their value while being starved of the resources to do so.
In this session, we'll move past the usual "just communicate more" advice and dig into what actually drives adoption — and what quietly kills it.
We'll cover:
- Why adoption stalls — and why it's rarely a quality problem. Component completeness is the strongest driver of adoption, but it's not enough on its own. We'll look at why even well-built systems struggle to get traction, and the role that mandate, community, and governance play in closing the gap.
- The buy-in paradox. 40% of teams are dissatisfied with buy-in, yet "limited stakeholder support" ranks as a top-three challenge. We'll explore why leadership buy-in is so hard to sustain, how to build a case that sticks, and what the teams with high adoption are doing differently.
- Measurement as a survival strategy. 20% of teams track no metrics at all. Of those who do, most lean on component usage and accessibility compliance — but almost nobody measures ROI. We'll talk about what to measure, how to connect it to business outcomes, and why this is non-negotiable for long-term survival.
- The understaffing crisis and what to do about it. With 61% of teams reporting inadequate staffing and resources named as the top challenge across the board, we'll discuss realistic strategies for doing more with less — including contribution models, automation, and knowing what to deprioritize.
- From "nice to have" to infrastructure. 82% of teams report that their design system has improved collaboration — but perception doesn't always translate to protection. We'll share what distinguishes the systems that are thriving from those that are perpetually at risk.
Whether you're fighting for headcount, trying to prove value to leadership, or wondering why your well-crafted system isn't getting picked up, this session will give you data-backed strategies to turn adoption from your biggest vulnerability into your strongest argument.
Speakers
Madelin Snyder
Head of Product at zeroheight
Madelin (she/her) is Head of Product at zeroheight. She stumbled into tech 10 years ago, reveled in the whirlwind of early-stage companies, and has spent the past four years figuring out what design systems are all about. She’s happiest with a spicy bourbon in hand, asking too many questions, and exploring the systems that shape how we work.
Guy Segal
Director, Design & Design System at Thomson Reuters
Guy is a design leader with over 20 years of experience in the tech industry, specializing in UX, product design, and DesignOps. His expertise in design leadership and people management has allowed him to foster innovation and collaboration within design teams, establishing robust design practices and leading them to success. In recent years, Guy has focused on design systems, building and growing teams around the practice, and launching systems that optimize efficiency and enhance user experiences.
Henry Daggett
Design System Lead, VP Product Designer at Societe Generale
Henry Daggett is the Design Systems lead at Societe Generale and a Product Designer/Design Engineer with a specialty in building trading and complex technical tools for Finance, AI and Engineering. He’s an enthusiast for Design and Engineering collaboration, painting and a bit of writing.
7
4:00 PM - 5:00 PM