Design systems reframed as organizational infrastructure, not component libraries

Source type	Practitioner
Confidence	High
Last verified	2026-03-20
Topics	design-systems design-leadership

Insight: After a year of community writing, the Design Systems Collective identifies a persistent pattern: design systems are now framed as organisational infrastructure rather than component libraries. Key recurring tensions: consistency vs flexibility, enablement vs control. Adoption matters more than technical elegance, ownership never quite settles, and governance always shows up late but never quietly.

Detail: Nathan Curtis warns the community is too focused on design tokens at the expense of component architecture: "Component architecture is an order of magnitude more complicated." He also identifies design-and-code drift as the biggest ongoing risk. The pattern of design system work being "less about the UI and more about alignment, judgement, and responsibility" echoes across practitioner accounts from multiple organizations.

Sources

• Shane P. Williams / Design Systems Collective — "One year in: the patterns that wouldn't go away" (2026-02-02)
• Nathan Curtis via Design Systems Collective — "interview" (2026-02-02)

Related: existing entry "Design systems governance patterns" in external/design-systems.md — COMPLEMENTS