WritingTopic
Fundamentals
What a design system is, how it differs from a UI kit or a component library, and how to tell whether you need one yet.
7 articles
FundamentalsWhat is a design system? A plain-English guide for product teamsA design system is the shared decisions, parts and agreements behind a product's UI. What's inside one, how it differs from a UI kit, when you need one.13 min read · Guide
FundamentalsDesign system vs style guide vs component library vs UI kitFour terms people use interchangeably, and what each actually includes. A comparison table, a diagram of how they nest, and how to tell which one you have.8 min read
FundamentalsDo you need a design system? A decision guide for startups and growing teamsSeven questions, five maturity stages and the signs you've outgrown a UI kit. A practical way to decide whether your team needs a design system yet.11 min read
FundamentalsThe design system maturity modelFive stages of design system maturity, how to tell which one you're at, what the next step takes, and why aiming for the top too early backfires.7 min read
FundamentalsWhy design systems fail: ten failure modes and their antidotesThe ten ways design systems fail, from no engineering commitment to measuring usage instead of value, with the antidote and early warning signs for each.5 min read
FundamentalsDesign systems for startups: the minimum that pays offWhat a startup actually needs from a design system: tokens in code, a themed component library, a small Figma library, two owners, and when to add more.5 min read
FundamentalsMost design systems are just expensive UI libraries8 min read · on Medium ↗