The worst design system project is one that starts too early. Wrong timing, wrong scope, wrong people and it dies in a folder somewhere, untouched.
In this episode, Symon and Marcello break down the three signals that tell you you're actually ready for a design system, the two signs you're definitely not, and how to scope a version one that people will actually use. They also cover the build or buy decision, and why adoption matters more than architecture.
This is Part 3 of a 3-part series on design systems.
💡 Key Topics:
The 3 readiness signals: when a design system actually makes sense
2 signs you're starting too early (and will waste the investment)
Build, buy, or borrow: product systems vs. web experience systems
Who needs to be in the room beyond design and engineering
How to scope v1 so it ships in weeks, not months
The 90-day check: how to know if it's working
Why the first step is always an audit
📖 Chapters:
0:06 — Series recap and what we're covering today
0:56 — The worst design system project starts too early
1:30 — Signal 1: Multiple teams making decisions independently
2:22 — Signal 2: You're scaling, rebranding, or rebuilding
3:55 — Signal 3: Recreating instead of creating
4:30 — Not ready: your brand isn't stable yet
5:33 — Not ready: no one to own it
6:09 — Build, buy, or borrow
7:49 — Web experience systems: Relume and Osmo Supply
8:27 — Who should manage the design system
9:39 — Scoping version one: start with what you rebuild every time
10:48 — The most common scoping mistake
12:05 — The 90-day check: is anyone actually using it?
12:57 — Start with an audit
13:33 — It doesn't have to be perfect. It has to exist.
Podden och tillhörande omslagsbild på den här sidan tillhör
tennis. Innehållet i podden är skapat av tennis och inte av,
eller tillsammans med, Poddtoppen.
