A practical guide to Design System components
Design systems often borrow the language of product thinking — build, measure, learn. But unlike products, they’re not always treated with the same rigour. Components get rebuilt, ignored, or bypassed altogether. Adoption lags. Consistency slips. And most teams are left trying to figure it out from scratch, component by component.
My role
I wrote A Practical Guide to Design System Components to help close that gap. Based on years of hands-on experience building and maintaining large-scale systems, the book breaks down a repeatable process for designing, testing, and evolving components that people actually use.
Rather than offer abstract theory, the book focuses on practical methods—research steps, decision-making techniques, and alignment strategies that lead to better adoption and more sustainable libraries. It’s designed to support not just designers, but anyone involved in creating reusable UI: developers, PMs, and cross-functional contributors alike.
The book has since become a go-to reference for teams looking to raise the quality of their component libraries without starting from scratch each time.