Issue 214  9th March 2026

When the Output Becomes the Material

Yesenia explores how AI-driven interfaces shift design systems from component assembly to intent-driven adaptation, where product primitives like Tasks and Events become the primary design material. They demonstrate how context-aware systems can adapt UI based on user expertise and work phase, requiring design systems to define grammar for product primitives including their anatomy, relationships, and surface states.

Design systems are platform problems, not feature problems

Shaun draws on nine years leading design systems at Spotify to explain why design systems require platform organisation structures, not feature team environments. Feature teams optimise for speed and shipping, whilst platform teams focus on consistency and long-term scalability. Misaligning these through organisational placement creates structural problems that compound over time.

From basic adoption to meaningful measurement: How design system metrics evolve

Maya explains how design system metrics should evolve beyond basic adoption tracking, which often falls into the trap of measuring activity rather than meaningful impact. She introduces a framework distinguishing health metrics from goal metrics and strategic from operational metrics, helping teams tell a complete story of their system's value as it matures.

Managing Microcopy with Design Tokens and Style Dictionary

In part 15 of my Design Tokens and Style Dictionary series - I demonstrate how to manage microcopy (button labels, error messages, form hints) as design tokens using Style Dictionary and the W3C specification's ⁠$extensions property. By treating interface copy as systematically as colours or spacing, teams gain consistency, version control, and straightforward localisation.

Oh, and I'm also looking for client work <3

People's Primitives

Donnie explores why primitive tokens exist for human communication rather than system necessity. Primitives like color-red-500 should remain permanent values to meet user expectations, whilst semantic tokens handle contextual changes across themes. In truly semantic systems, you could assign values directly without a primitive tier, though large organisations benefit from maintaining them for cross-team discussion.

Figuring it out in chaos: implementing a new Design System in a legacy-heavy company

Cynthia reflects on implementing a new Design System in a legacy-heavy startup environment with no clear roadmap and unfamiliar stakeholders. They share how listening to feedback, building cross-functional allies, and embracing uncertainty helped them navigate pushback and create collective ownership, ultimately reducing designer QA time by 70% and establishing a sustainable system.