Most design systems fade right after delivery. They land as polished Figma libraries, serve a single release, then slowly decay while teams spin off variants in every direction. The failure is seldom skill — it’s stewardship nobody signed up for.
Begin with tokens, not buttons
Teams that polish buttons first end up with flawless buttons in a dozen greys. Drop one level down instead: colour, type, spacing, and radius tokens named for their role, not their look. Rename “action” once and every dependent updates — code included, when tokens ship as variables.
Three layers, three caretakers
Split the library into foundations (kept by design ops), patterns (kept together), and feature-specific parts (kept by product teams). Only foundations need central sign-off to alter. The rest grows by suggestion, through a short proposal any designer can draft in an afternoon.
The single rule that counts
It is this: nothing joins the library until it has launched in two spots. That one bar removes guesswork bloat, demands proof in production, and turns the system into a log of choices — not a wishlist. Hold that line and the library will still breathe in two years.
