Episode 070 Deep Dive: Lasting Design System Infrastructure with Ben Callahan & Hannah Clarke

IntroductionHost Ben Callahan is joined by co-host Hannah Clarke, UI Engineer at Intapp, for a live deep dive on building design system infrastructure that lasts. The survey went to 1,061 practitioners and received 45 responses across four questions: company leadership model, dedicated team roles, who owns coded component delivery, and what actions create a system that endures. The conversation spans surprising results, web component delivery strategies, the framework agnostic debate, the unicorn-hire problem, API flexibility, and the human community that makes any system worth building.This episode is made possible by Mintlify. If your design system documentation lives in five places and satisfies no one, Mintlify can provide one beautiful, AI-powered home for everything your team builds (and the why behind those decisions).Try it free → https://bit.ly/try-mintlify (use code MINT-THEQ for 50% off Pro for 6 months)Show Notes00:02 — Welcome, Hannah's intro, and sponsor message (Mintlify)01:07 — Hannah's background: UI Engineer at Intapp, full-stack roots, how she found the design systems space03:25 — Survey overview: Four questions, 1,061 sent, 45 responses04:39 — Q1: "Led by product" came in at ~40%, surprising Ben; Hannah less shocked given her experience06:31 — Q2: Front-end dev outranked UI design in dedicated roles; reference to Sean Bent's post on design system hiring trends08:22 — Community as infrastructure: Awareness and human connection matter as much as tooling; user showcase idea from Hannah's team retro11:14 — Joshua: In-person labs where consuming teams experiment with the design system to make it feel engaging12:13 — Hannah's delivery approach: Stencil + web components, outputting to multiple NPM packages (tokens, styles, web components, React 18, React 19 + SSR)14:33 — Q4 theme: Framework agnosticism as a longevity strategy; design-side agnosticism and Penpot as a Figma alternative16:50 — Josh: Journey from web components wrapped in React to going all-in on React and why17:48 — Real challenges wrapping web components for React: Shadow DOM, team culture resistance, the "pure React" demand19:09 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements22:50 — Guy: AI workflow from Figma to production code; using Figma Console MCP to convert prototypes into design-system-compliant files; circumventing design tools altogether27:11 — Kelly: Laid off with her entire product design org; job postings pitting design vs. engineering; the value of tight cross-discipline collaboration30:54 — Hannah: The full-stack cycle — companies oscillate between specialists and generalists at their own peril32:23 — Greg: Flipping the unicorn question — even if unicorns existed, would they want to do everything expected of them?36:05 — Amy: Designers vibe coding directly in repos; how design systems can support that workflow and reduce chaos37:31 — Joanna: Built two full implementations (React + Angular) after teams refused a framework-agnostic approach; the real costs39:30 — Sean: Extending across iOS + Android; shared tokens, consistent naming, cross-platform rituals; treating Figma as a fourth platform41:22 — Managing cross-platform parity: Manual processes, shared style layers, prioritization by demand44:09 — Hannah: Why she moved away from "just React" thinking; the unsolved mobile challenge for a three-person team46:36 — API flexibility vs. rigidity: Joanna's case for flexible APIs; Hannah and Mike on finding the balance without losing consistency51:01 — Closing remarks and community announcementsWhere to Find the HostsBen Callahan, Founder of Sparkbox and Redwoods Design System Community: https://bencallahan.comHannah Clarke, UI Engineer at Intapp: https://bit.ly/47kl2lnGet the Raw Data: https://bit.ly/3OOuU0BReview the FigJam Notes: https://bit.ly/4rxa9E8Join the Conversation: https://bit.ly/answerTheQuestion