The Question: Design System Collaborative Learning

Episode 072 Recap: Extreme Design System Support with Ben Callahan and Doug Neiner

Host Ben Callahan and co-host Doug Neiner, a design system practitioner at Planview, sit down immediately following the Episode 072 deep dive to reflect on what they heard from the community. The survey was sent to 1,081 design system practitioners and received 49 responses across four questions: what support do you currently offer; how would you change it without constraints; what prevents better support; and share a story of going above and beyond. The conversation covers the standout data points: the written vs. video documentation gap, the surprisingly high rate of dev environment access, embedding, private vs. public support channels, the balance between high-touch support and burnout, and the importance of being perceived as a helper rather than a blocker.

Show Notes
00:00 - Introduction and episode overview
01:46 - Q1 data highlights: written vs. video documentation gap
02:13 - Dev environment access: higher than expected at nearly 50%
02:48 - Lowering the bar for video production with modern tooling
03:15 - The perfectionist/design system practitioner Venn diagram
04:00 - Q3 data: unclear ownership is low; headcount and competing priorities dominate
04:30 - What "competing priorities" really means for system teams
05:46 - Doug's support approach at Planview: docs, Slack channels, onboarding, and local debugging
07:53 - Going beyond "access": running consumer products locally for deeper support
08:28 - The most extreme example: getting an org-issued PC to support a heavy product
09:42 - DMs vs. open channels: why private requests matter for trust
10:34 - Not everyone is comfortable asking publicly—meeting people where they are
11:20 - The problem with ticketing systems and over-streamlining support
11:49 - How private support builds trust that eventually leads to public participation
13:25 - Prioritizing relationship over efficiency: creating tickets on behalf of consumers
14:10 - Scale vs. effort framework for thinking about support types
15:42 - Embedding: initially looks high-effort/low-scale, but the impact compounds
16:21 - Doug on embedding: modeling behavior, referencing docs together, building self-sufficiency
17:50 - The other side: high-touch support and the risk of design system team burnout
18:47 - How to gauge when a support request warrants deep mentorship vs. a quick fix
21:56 - Recap of embedding discussion: Sean's reverse embedding process from Spotify
23:28 - Doug's one experience with reverse embedding and its lasting impact
24:06 - Alexander's story: misaligned incentives can undermine embedding programs
25:08 - Rebecca's insight: being a helper vs. a blocker, and how hard trust is to rebuild
26:06 - What embedding teaches you about your own system's pain points
26:31 - Staying connected to product work keeps system teams grounded in consumer reality
27:31 - Mapping stakeholders: identifying high-influence non-advocates and converting them
28:35 - Doug: influence can come from the product, not just the person
29:57 - AI in design system support: useful for self-service, but reduce touch points with caution
31:01 - Closing reflections and thanks
31:39 - Outro
Where to Find the Hosts
Ben Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.com
Doug Neiner is a Principal Software Engineer at Planview. Connect with him on LinkedIn.

Get the Raw Data
Access the complete survey data from Episode 072 to conduct your own analysis: **https://bit.ly/41H6Tf7**

Review the FigJam Notes
Dig into the collaborative notes we took as a community during the deep dive: **https://bit.ly/4mm3uLZ**

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/answerTheQuestion**

Episode 072 Deep Dive: Extreme Design System Support with Ben Callahan and Doug Neiner

Host Ben Callahan is joined by co-host Doug Niner, a design system practitioner at Planview, to explore extreme design system support—what it looks like, what gets in the way, and what truly moves the needle with consuming teams. The survey was sent to 1,081 design system practitioners and received 49 responses across four questions: what support do you currently offer; how would you change your program if unconstrained; what prevents better support; and share a story of going above and beyond. The conversation covers the surprising prevalence of dev environment access, the rarity and outsized impact of embedding, the tension between high-touch support and burnout, and why building trust may matter more than any specific tactic.

Show Notes
00:00 - Introduction and welcome 
00:37 - Guest background: Doug Niner on getting into design systems at Planview 
01:38 - Topic framing: what is "extreme design system support"? 
02:07 - Survey overview: the four questions asked 
03:34 - Survey stats: 1,081 sent, 49 responses 
03:59 - Q1 findings: what support are teams currently offering? 
04:30 - Reactions: video vs. written docs, dev environment access 
05:27 - Video documentation: perfectionism vs. "good enough" screen recordings 
06:25 - Q3 findings: headcount, bandwidth, and competing priorities dominate 
07:17 - Key insight: teams know what good looks like but lack people and time 
09:10 - Embedding: high effort, but potentially exponential impact through advocacy 
10:10 - Community discussion: what does "embedding" actually mean? 
11:07 - Sean shares his team's embedding process: runbooks and buddy systems 
15:36 - Alexander: forward embedding failures vs. reverse embedding wins 
17:53 - Reverse embedding: consuming team members join the design system team 
19:50 - Disruption and ROI: is onboarding a stream of embeds worth it? 
21:16 - Turning embedded team members into lasting design system advocates 
23:09 - Rapid bug turnaround as a trust-building extreme support tactic 
24:57 - Embedded collaborators as a source of honest, continuous feedback 
25:53 - "Runners": rotating on-call support roles and AI-assisted quick fixes 
26:45 - Rebecca on trust: being a helper vs. a blocker 
27:14 - Supporting private requests alongside public channels 
28:35 - Over-systematizing support and why removing friction builds trust 
29:31 - Q4 stories: going above and beyond for consuming teams 
29:43 - Taylor's story: building buy-in for a generational system change at Fidelity 
33:12 - Doug's story: burning trust with a team and winning them back over 18 months 
34:37 - Mapping stakeholders from saboteur to advocate 
35:30 - Jane's perspective: extreme support drives adoption but risks burnout 
36:53 - Hand-holding vs. empowerment: when is high-touch support too much? 
37:19 - Transitioning from high-touch support to self-service empowerment 
43:51 - Live prototyping as a low-effort, high-value support approach 
45:15 - Figma detachable components and slots discussion 
45:50 - Christine's bi-weekly demo program at office hours 
47:56 - Closing reflections; encouragement to read Q4 survey answers 
48:25 - Community updates: Redwoods, Design System Triage, Converge in Newcastle 
50:09 - Outro

Where to Find the Hosts
Ben Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.com
Doug Neiner is a Principal Software Engineer at Planview. Connect with him on LinkedIn.
Get the Raw Data
Access the complete survey data from Episode 072 to conduct your own analysis: https://bit.ly/41H6Tf7
Review the FigJam Notes
Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4mm3uLZ
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/answerTheQuestion

Episode 071 Deep Dive: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman
In Episode 071, host Ben Callahan is joined by co-host Vitaly Friedman—UX Lead, author, and founder of Smashing Conference—for a deep dive into the criticality of design systems. Vitaly brings experience from complex enterprise environments, including a multi-year engagement consolidating 199 European Parliament websites into one across 25 languages.
The survey was sent to over 1,000 design system practitioners, yielding 61 responses. Participants were asked four questions through the lens of their single most critical product: (1) what level of impact would a product failure have on end users—loss of comfort, discretionary money, essential money, or life; (2) the size of their engineering team; (3) how they ensure their design system supports that criticality; and (4) whether anyone in their org is doing workflow analysis with users.
Show Notes
00:04  Introduction and episode overview
01:48  Vitaly's background: complex systems, B2B, insurance, European Parliament
03:01  The pressure of high-stakes work and measuring before/after impact
05:19  Ben's upcoming book, published by Smashing Magazine
05:44  Survey overview: methodology and FigJam data access
06:11  Q1 Results: 57% selected "loss of essential money"; write-in responses
07:08  Q2 Results: even distribution across team sizes; Cockburn's scale model
08:03  Vitaly on loss of trust and reputation as missing modern categories
09:29  Expanding the criticality framework for today's digital landscape
10:52  Defining workflow analysis vs. task analysis
14:33  Financial app example: importing a portfolio (task) vs. market analysis (workflow)
15:56  Key finding: workflow analysis correlates with team size, not criticality
17:23  Peter: using AI agents as a team of one to conduct workflow analysis
19:41  Community discussion: respondents who selected "loss of life"
20:09  David (Mayo Clinic): design system tokens and cascading patient-room risk
21:32  Taylor: higher criticality means more questions and stakeholders, not a different process
23:52  Vitaly: poor data visualization choices can cascade into financial loss
24:20  Reference: The Fifth Discipline by Peter Senge (1990)
25:08  Hattie (John Deere): autonomous vehicle safety warnings and multi-team sign-off
26:41  Jesse (NAVA): public benefits delivery—if this fails, someone doesn't eat
28:10  Vitaly: legacy systems as an underappreciated source of fragility and criticality
30:06  Taylor: legacy is an iceberg—you don't know what you've got until you knock
31:58  Kele: integrating a design system and AI tooling into existing enterprise SaaS
33:17  Level-setting AI expectations with leadership
35:42  Greg: AI tooling as a potential accelerator for legacy accessibility migration
39:38  Vitaly: migrating away from legacy means designing the change, not just the UI
40:06  Ben: FOMO-driven AI adoption decisions
41:32  Taylor: legacy systems are often politically protected
44:15  Ben: systems thinkers evaluated on product KPIs—structural misalignment
46:35  Kele: reframing "healthy tension" as creative friction with different mandates
49:22  Closing and thank-yous
49:48  Redwoods membership, UX London, previous episode with Hannah
Where to find the hosts
Ben Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.com
Vitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn: https://bit.ly/43Iig8B
Get the Raw Data
Access the complete survey data from Episode 071: https://bit.ly/4rYcRTk
Review the FigJam notes
Dig into the collaborative notes from the deep dive: https://bit.ly/4bKWSlt
Join the conversation
Participate in future episodes and contribute to the next survey: https://bit.ly/answerTheQuestion

Episode 071 Recap: The Criticality of Design Systems with Ben Callahan & Vitaly Friedman
Introduction
Host Ben Callahan and co-host Vitaly Friedman reflect on the insights from the Episode 071 deep dive on the criticality of design systems. Vitaly is a UX lead, founder of Smashing Conference, and practitioner working in complex enterprise environments—most recently with the European Parliament.
The survey was sent to 1,069 design system practitioners and received 61 responses. Respondents were asked four questions through the lens of their single most critical product: how failure would impact end users (loss of comfort, discretionary money, essential money, or life); the size of the engineering team; how their design system supports that criticality and scale; and whether anyone in their org is doing workflow analysis with product users.
Show Notes
00:00 - Welcome and introductions; Vitaly reflects on surprises from the deep dive
00:27 - How The Question works: survey Monday, deep dive Thursday, recap to follow
01:41 - The Coburn Scale and how it shaped the survey questions
03:45 - Survey results: why "loss of essential money" topped the criticality scale
04:23 - Vitaly's take: loss of reputation and trust as proxies for financial loss
05:30 - Write-in responses: loss of transparency, essential data, and future compatibility
07:28 - Hyper-personalization and ephemeral UI: validating experiences we can't fully see
08:50 - Decisions as infrastructure: encoding decisions into markdown and design systems
11:57 - Automation and AI across design, code, and UI—and what that means for human oversight
13:52 - "Flying blind": the risks of building layers atop systems we don't fully understand
16:30 - Defining workflow analysis vs. task analysis and why it matters
19:37 - The hypothesis: does higher criticality correlate with more workflow analysis? The data didn't confirm it.
22:01 - What the data did show: team size as a stronger predictor than criticality
25:32 - Design systems sandwiched between product teams and top-down quality guidelines
29:35 - Legacy software: an underappreciated risk factor and political minefield
32:39 - Migrating legacy means migrating flows, habits, and ways of working—not just UI
34:46 - What Vitaly is working on: events, video courses, design patterns, and upcoming books
36:14 - How to stay connected; Redwoods community open for membership
---
Where to Find the Hosts
Ben Callahan is Founder of Sparkbox and Redwoods Design System Community. Read his writings, have him present at your event, or engage with him as a coach or consultant at https://bencallahan.com
Vitaly Friedman is a UX Lead and founder of Smashing Conference. Connect with him on LinkedIn https://bit.ly/43Iig8B
Get the Raw Data
Access the complete survey data from Episode 071 to conduct your own analysis: https://bit.ly/4rYcRTk
Review the FigJam Notes
Dig into the collaborative notes we took as a community during the deep dive: https://bit.ly/4bKWSlt
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/answerTheQuestion

Introduction
Host 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 Notes
00: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 space
03:25 — Survey overview: Four questions, 1,061 sent, 45 responses
04:39 — Q1: "Led by product" came in at ~40%, surprising Ben; Hannah less shocked given her experience
06:31 — Q2: Front-end dev outranked UI design in dedicated roles; reference to Sean Bent's post on design system hiring trends
08:22 — Community as infrastructure: Awareness and human connection matter as much as tooling; user showcase idea from Hannah's team retro
11:14 — Joshua: In-person labs where consuming teams experiment with the design system to make it feel engaging
12: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 alternative
16:50 — Josh: Journey from web components wrapped in React to going all-in on React and why
17:48 — Real challenges wrapping web components for React: Shadow DOM, team culture resistance, the "pure React" demand
19:09 — Post-processing scripts on top of Stencil: Default values, required props, types files, and developer quality-of-life improvements
22:50 — Guy: AI workflow from Figma to production code; using Figma Console MCP to convert prototypes into design-system-compliant files; circumventing design tools altogether
27:11 — Kelly: Laid off with her entire product design org; job postings pitting design vs. engineering; the value of tight cross-discipline collaboration
30:54 — Hannah: The full-stack cycle — companies oscillate between specialists and generalists at their own peril
32: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 chaos
37:31 — Joanna: Built two full implementations (React + Angular) after teams refused a framework-agnostic approach; the real costs
39:30 — Sean: Extending across iOS + Android; shared tokens, consistent naming, cross-platform rituals; treating Figma as a fourth platform
41:22 — Managing cross-platform parity: Manual processes, shared style layers, prioritization by demand
44:09 — Hannah: Why she moved away from "just React" thinking; the unsolved mobile challenge for a three-person team
46:36 — API flexibility vs. rigidity: Joanna's case for flexible APIs; Hannah and Mike on finding the balance without losing consistency
51:01 — Closing remarks and community announcements

Where to Find the Hosts
Ben Callahan, Founder of Sparkbox and Redwoods Design System Community: https://bencallahan.com
Hannah Clarke, UI Engineer at Intapp: https://bit.ly/47kl2ln
Get the Raw Data: https://bit.ly/3OOuU0B
Review the FigJam Notes: https://bit.ly/4rxa9E8
Join the Conversation: https://bit.ly/answerTheQuestion