Design systems that outlive the agency that built them
A modern component system is documentation, tokens, and contribution rules, not a Figma file with 400 variants. This is how we hand enterprise UI to internal teams without a second rebuild.
Elena Voss · Head of Product Design · 6 min · May 21, 2026
Agencies love to ship a beautiful marketing site and call the component folder a design system. Internal teams discover the truth on week three: undocumented variants, inaccessible dialogs, and spacing that only works on the homepage.
A durable system starts with tokens that map to CSS variables, not magic numbers. Radius, color, type, and motion should be boringly consistent. Primitives come from a maintained set (buttons, inputs, focus rings) with accessibility as a default, not a ticket.
Contribution rules matter as much as components. If a product squad cannot add a pattern without breaking three pages, they will fork. We leave lint rules, Storybook (or equivalent), and a short “when to create a new primitive” guide.
The goal is not visual novelty. The goal is an interface language the company can still speak after we leave.