AI doesn't need your design system to be perfect. It needs it to be honest.
Why documenting your mess matters more than fixing it
❖ Writing about design, systems, and the organisations that build them.
Processing your application
Please check your inbox and click the link to confirm your subscription.
There was an error sending the email
Popular posts
Slots and the control paradox: Why loosening your design system might save it
How Figma's newest feature exposes an uncomfortable truth about the way we've been building systems
We're still terrible at the people parts
Why teams with perfect systems still build around them instead
The hidden cost of design system entropy
How AI tools surface every shortcut and inconsistency
Your next design system user is an agent
How to structure components for machine readability, semantic clarity, and long-term resilience
Moneyball for designers: Data-driven design decisions from baseball's analytics revolution
How evidence-based thinking transformed America's pastime – and what it means for creating better digital products
Why your components break in production (and how to fix it)
How to build design systems that gracefully handle the complexities of real-world API data
The component adoption gap: Understanding the psychology behind design system success
Why some elements become team favourites, while others gather digital dust –and what you can do about it.
Designing for outcomes, not features: Shifting the conversation in product teams
Moving beyond feature factories to create measurable impact in product design
From handoff to harmony
How continuous collaboration and iteration create better products and teams
Designing with APIs: A practical guide for beginners
How designers can embrace collaboration, flexibility, and real data when working with APIs.
Recommended
Design system archaeology
Reading a system you didn't build, and why the first 90 days look nothing like building
Agents are the most honest reviewers your design system will ever have
The most useful feedback your system has ever produced is on a thirty-day timer
What your components look like as data
Why every layer name, variant, and token reference is an architectural decision