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
The value of junior designers
Over the last three years, I’ve spent a good chunk of time mentoring bootcamp graduates and self-taught designers who are looking to land their first role in UX and/or UI. Throughout our sessions, there’s a lot of back and forth, where I’ll provide design feedback, ask...
Solving complex problems with design thinking
Design thinking is a problem-solving process that uses creative methods to overcome complex challenges. It allows for new perspectives and innovative solutions by embracing change and uncertainty. Design thinking has been used in various industries, from healthcare to finance to manufacturing. Here we’ll explore how design thinking solves complex...
The importance of digital accessibility
Accessibility is something that should be baked into all digital strategies, and yet it receives very little resourcing and attention from organisations across the globe. In fact, in February 2021, when WebAIM ran their annual accessibility analysis on the Majestic Millions list, they found an average of 51.4 errors...
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