Most people think a design system is a Figma file with some brand colors and button styles. It's not. It's the infrastructure that connects how your brand looks to how your product actually gets built, maintained, and scaled. In this episode, Symon and Marcello are joined by Avi Debnath, a senior product designer at Intuit who works on the design platform serving TurboTax, Mailchimp, and QuickBooks. Together they unpack what a design system actually contains, how real teams use one, why governance is the part nobody wants to talk about, and what mid-market companies should know before building their own. This is Part 2 of a 3-part series on design systems.
Key Topics:
• The Lego analogy: the simplest way to explain a design system to anyone
• What's actually inside a design system: foundations, components, patterns, and documentation
• How designers, developers, and product managers use a design system day to day
• Why a brand guide and a design system are not the same thing
• Design system governance: who owns what, and what happens without it
• Opinionated vs. flexible: how Intuit decides what teams can and can't change
• Why adoption is a culture problem, not a technical one
• The ROI question: because it always comes back to ROI
Chapters:
0:00 — The Lego analogy for design systems
0:42 — Intro: Part 2 of the design system series
1:35 — Avi's role on Intuit's design platform team
3:08 — How the GenUX team serves internal business units
5:04 — Catching AI inconsistency before it scaled out of control
6:09 — Explaining a design system to someone who's never heard the term
8:42 — Why every new brick has to work for every set
9:52 — What a design system actually touches inside an organization
10:19 — Benefits: consistency, trust, and a shared language
11:47 — Drawbacks: slowing down in a world that moves fast
12:52 — Does a design system help resolve conflict between teams?
14:06 — When teams build outside the system (and why that's useful feedback)
15:55 — Fixed vs. flex: what's opinionated and what's open
17:20 — Advice for smaller companies: know your why
19:04 — The communication breakdown that kills adoption
19:52 — Getting people to actually commit: governance and culture
20:08 — Why it always comes back to ROI
22:42 — One thing to take away if you've never thought about design systems
25:08 — Symon's takeaway: know the why before you build
25:28 — Marcello's takeaway: the Lego analogy
25:55 — Where to find Avi
26:35 — What's next: Part 3 on building a design system
🔔 Subscribe for weekly episodes on design, web strategy, and building better digital businesses.