A design system nobody reaches for is just documentation.
Most systems don't fail in the token layer. They fail in the last mile — the gap between what the platform team built and what product teams actually ship.
The adoption gap, in five slides.
Why design systems stall after launch — a swipeable series built on the .carousel component. Swipe, scroll, use the buttons below the frame, or press ← → with the series focused.
Governed is not the same as used.
Two states of the same system, one year after launch. The first is where most teams stop. The second is where the payoff lives.
Built and governed
Tokens named, components documented, releases versioned, contribution rules ratified — and every product team still shipping its own buttons.
Enabled and adopted
Packaged for the teams that ship, so it gets installed, extended, and defended where the product actually gets built.
The numbers say it's a people problem.
62%
of design-system teams name adoption — not tooling, not tokens — as their hardest problem. The bottleneck is people, not components. Design Systems Survey · Sparkbox 2024
1/4
of product squads consume the official library without a local fork. Governance without enablement doesn't stop divergence; it just documents it. Enterprise UI Benchmark · 2025
2×
faster feature delivery for teams that start from shared components instead of rebuilding primitives per project. Platform Eng. Field Report · 2025
Meet teams where they already work.
Systems don't win by being right. They win by being reached for — at the moment a deadline makes the shortcut tempting.
The adopted systems ship copy-paste starters, answer questions in the channels where product teams live, and treat every fork as a bug report against their own onboarding — not as someone else's compliance failure.
Start where the work is.
Measure reach, not release notes. A system earns its keep one adopted component at a time.
01
How this page behaves
Without JavaScript
The series is a CSS scroll-snap container: swipe, trackpad, and the thin scrollbar all page through slides. The button row and dots stay [hidden] until the enhancement script wires them, so nothing renders dead.
Keyboard
The track is focusable (tabindex="0"); with the region focused, ← → move one slide and Home / End jump to the ends. Dots and arrows are real buttons with visible focus rings.
Reduced motion
Smooth scrolling only applies under prefers-reduced-motion: no-preference; otherwise every navigation is an instant jump. There is no autoplay to pause because there is no autoplay.
Made with hairlines and serifs by Vinny Carpenter. The 1.5px is on purpose.