Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan

Episode 069 Deep Dive: Rebuilding a Design System Mid-Flight with Ben Callahan & Shimaa Hassan

Introduction
In episode 069 of *The Question*, host Ben Callahan (founder of Sparkbox and the Redwoods Design System Community) sits down with co-host Shimaa Hassan to tackle one of the most universal challenges in the space: rebuilding a design system while the products it supports are still in production.

Ben surveyed 1,061 design system practitioners and received 53 responses across four questions: a 0–5 range question asking how often respondents think about throwing their system away and starting over, plus three open-text questions — (1) what's the one decision you'd make differently on day one, (2) how do you keep product teams confident in a system being rebuilt underneath them, and (3) share a story about rebuilding mid-flight. Key themes include token architecture, composability, governance, and the honest reality of how rarely formal migration mandates get enforced.

---

Show Notes

- 00:02 — Welcome and intro
- 00:27 — Shimaa's background: from Alexandria, Egypt to design systems at Square and Remote
- 02:28 — Shimaa's current challenge: rebuilding at Remote while the product ships continuously
- 04:46 — Survey methodology and overview of the four questions
- 05:43 — Question 1 results: roughly 50/50 split; Ben's sentiment analysis of the extremes
- 08:48 — Question 2 highlights: token architecture, simplicity, composability, governance, leading with documentation
- 10:09 — Erin on a cross-platform parity audit (iOS, Android, web) and handling breaking changes
- 11:36 — Shimaa on balancing live product state with new system decisions
- 12:37 — Guy on semantic versioning: one major release per year, advance communication, and a CLI tool that automated 70% of breaking change migrations
- 14:34 — Taylor on SLAs, defining "breaking change" for your system vs. the org, mono repo vs. component-level versioning
- 17:45 — Maintaining parallel systems: running old and new simultaneously
- 18:53 — Peter references Kim Williams' Clarity talk on managing system transitions
- 22:36 — How do you get teams to actually switch? Selling the value of migration
- 26:26 — Shimaa's pro tip: run the codebase locally; use AI to audit token usage and map point-A-to-point-B
- 29:16 — Guy on mandates that exist on paper but aren't enforced; lower org maturity can work in your favor
- 31:41 — Taylor on the system as a place of stability; introducing an "additive threshold" for governance
- 36:50 — Shimaa on triage logs tagged "approved / will not do / future"
- 38:19 — Peter on adaptable (not rigid) infrastructure; wanting early involvement with consuming teams
- 42:07 — Taylor's feature status Airtable for centralizing and communicating request progress
- 45:46 — Shimaa introduces Norma Labs: a space for ideas not yet mature enough for the core system
- 47:06 — Aaron on component-level versioning with 20 components needing updates simultaneously
- 48:30 — Tallulah and Liz on capacity constraints; offering support windows to encourage faster migration
- 50:45 — Liz on her IBM experience building testing infrastructure to keep React and Angular in parity
- 52:31 — Peter's closing mantra: "Don't show me different, show me better"
- 53:01 — Shimaa's closing reflection; Ben's announcements

---

Resources Mentioned
- Kim Williams' Clarity Conference talk on transitioning between design systems (https://designsystems.media/video/kim-williams-start-with-your-brand-purpose/)

---

Where to Find the Hosts
Ben Callahan—Founder of Sparkbox and the Redwoods Design System Community. Individual and team coaching for design system programs. https://bencallahan.com

Shimaa Hassan—Senior Product Designer at Remote, specializing in design systems. https://www.linkedin.com/in/shimaahassan/

---

Get the Raw Data
Access the complete survey data from Episode 069 to conduct your own analysis: https://bit.ly/46s0G9w

---

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

---

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