Why Design Systems Fail — and a Framework to Make Them Ship

A design engineer with experience across three design systems argues that most such systems fail because they are built in isolation, optimized for design or infrastructure rather than continuous shipping. The author proposes a bottom-up framework that begins by identifying core product constraints — such as team size, data complexity, and deployment cadence — before writing a single component. Phase one focuses on documenting three to five key constraints in the first week, while phase two prioritizes building design tokens for spacing, typography, and color ahead of any UI components. Starting with tokens, the author contends, allows engineers to implement a shared source of truth quickly and lets design changes propagate instantly across an entire system. Following this approach, the author claims shipping velocity can increase by two to three times compared to traditional top-down design system workflows.