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
From component library to product engine
How design systems evolve to drive strategy and scale business intent
Signals from the top
What CEOs, research, and your own workflow are already telling you about design’s AI future
What a car taught me about control, collapse, and creative repair
On broken things, borrowed fixes, and making something whole again
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
JSON demystified: A field guide for designers
How understanding data structure improves your design process
Recommended
Building for coherence, not compliance
Lessons from Baldurs Gate 3 on contracts, governance, and judgment at the edges
What I stole from API documentation
Patterns from Stripe, GitHub, and Twilio that fixed my component architecture
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