UX engineering, in practice
Practical takes, honest opinions, and the occasional fictional UX engineer.
How to Turn Your Design System Into Something Teams Actually Want to Contribute ToHow to Turn Your Design System Into Something Teams Actually Want to Contribute To
You built the design system. You documented the tokens, shipped the components, maybe even got leadership to mandate adoption. Teams keep building their own buttons anyway.
The hidden cost of component inconsistencyThe hidden cost of component inconsistency
Inconsistent components fragment the user experience and inflate maintenance costs. The real price is distributed across code reviews, accessibility debt, onboarding friction, and constrained upgrades, and it compounds faster than most teams realize.
Are your design tokens doing more harm than good?Are your design tokens doing more harm than good?
Design tokens are meant to unify design and development, but structural gaps can limit their effectiveness and create hidden costs.
Why your design system score is lower than you thinkWhy your design system score is lower than you think
Exploring the common gaps between perceived and actual design system health, and why teams often overestimate their progress.
Accessibility debt: why it compounds and how to fix itAccessibility debt: why it compounds and how to fix it
Accessibility debt doesn't start with bad code. It starts with bad architecture. Learn how to address the root causes and build a more accessible product.
What a broken handoff actually costs your engineering teamWhat a broken handoff actually costs your engineering team
A broken design-to-code handoff process can generate hidden costs for engineering teams, leading to duplicated work and inefficiencies.
Build or buy: making the right choice for your design systemBuild or buy: making the right choice for your design system
Deciding whether to build a design system in-house or buy a commercial solution is a critical choice. Here's how to evaluate your options and make the best decision for your team.
Component libraries for teams that support multiple frameworksComponent libraries for teams that support multiple frameworks
Teams that build for React, Vue, and Angular face a real architecture challenge. This article covers the three main approaches: web components, headless patterns, and token-driven architecture.
What is a design system audit?What is a design system audit?
A design system audit identifies inconsistencies, accessibility gaps, and structural problems in your component library before they become expensive. Here's what one covers and why teams commission them.