Essays, conference talks, and podcast conversations. Most of it draws on what architecture taught me about building for the people who live with the result.
Designers are being told to accept an AI future defined by speed and “execution support.” A case for pushing back: tracing our long slide into abstraction, testing the limits of language as a design tool, and demanding tools that capture intent.
Why one-size-fits-all frameworks lead to digital homogenization, and what vernacular architecture teaches us about building design systems rooted in local context.
Strategies for proving a design system’s value and drawing a straight line to the business metrics stakeholders care about most.
Watch on YouTube (opens in a new tab)Design systems last when contributors span developers, designers, content, and product. How to share ownership without losing coherence.
Watch on YouTube (opens in a new tab)A live, collaborative session on what makes a design system feel local to its organization, culture, and brand, built around my Vernacular Design Systems essay.
If the way we build design systems has a fatal flaw, it’s waiting for enough investment to get it right. Why your product teams’ success is your success, and how to show value without asking first.
The value of design systems and their challenges, accessibility, and practical ways designers can close the gap with developers.