Episode 075 Recap: The Design System Identity Crisis with Ben Callahan and Cassie Groos
In this recap of Episode 075, Ben Callahan and Cassie Groos unpack what they learned from the community on the subject of the design system identity crisis. Cassie is preparing a talk on this theme for Hatch Conference in Berlin and used The Question as her research engine.
The survey was sent to 1,083 design system practitioners and received 60 responses across five questions: team posture toward AI, belief in the "design systems as AI's necessary foundation" narrative, how roles have changed in the past 12 months, how respondents would redefine a design system today, and the bets they're making that might be wrong by next year. Ben and Cassie dig into what's actually driving AI adoption when only 25% believe it protects their roles, how DS practitioners can use their outsized organizational influence to own the AI quality bar, how the definition of "design system" is quietly expanding to include AI as an audience, and whether writing context files for AI means double work or just different work.
Show Notes
00:03 — Welcome and intro
00:18 — Recap of all five survey questions and methodology: 1,083 sent, 60 responses
02:25 — Acknowledging ongoing layoffs and supporting the community
03:34 — A standout open response: "from clear vision to navigating the moment"
04:08 — Cassie's reframe: an opportunity to decide where we end up
04:48 — DS practitioners as an unseen but outsized influence in organizations
06:33 — What's actually happening in Cassie's world right now: architecting under shifting ground
07:40 — The tweet that kicked this all off: "we don't need component libraries anymore"
08:11 — Cassie's talk at Hatch Conference, Berlin, September 18
09:05 — Q1 and Q2 combined: 3 in 4 actively adopting AI; only 1 in 4 believes it protects their role
10:27 — Owning AI workflows as the stronger protection narrative
11:12 — Who's most protected: those managing the AIs and staying in the loop
11:48 — Cassie on going straight in on AI from day one — and why
12:01 — Ben's kids as gen-Z AI skeptics; the ethics of how models are trained
15:04 — Question 4: what even is a design system? Neither of them can answer it cleanly
15:29 — How respondents split: ~half said unchanged, ~40% said definition is expanding, ~12% not ready to define it yet
16:32 — Cassie: at the top level, it's still just a system for designing stuff
17:17 — Skills and agents casually showing up in answers as design system resources
17:23 — Ben on culture as the real substance of a design system program
18:42 — The new work layer: context files, components as data, AI-readable rules
19:58 — Living in the seams: juggling human-serving and AI-serving outputs simultaneously
21:18 — Why visual components won't disappear: people still like to look at things with their eyes
22:46 — Token efficiency and the rising cost of AI: CRDs, compounding context, and who actually pays
23:26 — Cassie: maybe we don't care — and maybe that's fine
24:29 — Cassie's takeaway: want to see more demos and hear what others are actually building
25:24 — Don't let pressure to adopt AI make us abandon our principles on quality and accessibility
27:34 — Does Claude show up in Cassie's morning routine? Yes — Figma work via Claude Code, Copilot at work
Where to Find the Hosts
Cassie Groos is a freelance design systems specialist and senior product designer currently at Unily. Connect with her on LinkedIn:
https://bit.ly/4tsihGU
Get the Raw Data
Review the FigJam Notes
Join the Conversation
The Question explores design systems topics through community research and deep-dive discussions. Participate in future episodes and contribute to the next survey:
https://bit.ly/answerTheQuestionWhat is The Question: Design System Collaborative Learning?
The Question is a collaborative learning podcast about Design Systems. Smart people like you sign up, answer a few niche questions about design systems for each episode, and then we all get together to unpack the data we've gathered. Each week, I'll invite a new co-host to help facilitate the conversation. After the deep dive, the co-host and I record a recap of what we learned. That means, for each episode, you can listen to the recap and the full deep dive!
If you're a design system practitioner, subscribe today (https://bencallahan.com/the-question) to receive an invitation to each episode. This only works if the community joins in!
Stay in learning mode ❤️