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