Blog

Driving Adoption in Design Systems

Building a design system is one thing. Getting people to actually use it is another. Across projects like El Español, Telefónica, Commons, and Metallicus I saw the same pattern: great components, zero adoption, and chaos creeping back in.

Creating and Scaling Design Systems

I've worked on a bunch of products over the years and most of them had the same issue. As teams grew the UI started to drift. One team shipped something new, another team updated an old screen, someone copied an old button from a file from 2019… you know how it goes. A design system became the only way to keep things clean and predictable.

Working with Engineers

Design systems only work when design and engineering move in the same direction. On projects like Bitloops, Clutch and Metallicus I learned that early alignment saves everyone time.

Rolling a Design System out

Rolling out a system is never "drop the library and pray". Each product needed something different.

Handling Resistance

There's always a moment where someone says "this component doesn't fit my team's flow." Most resistance is not about the component. It's about trust.

Keeping a Design System alive

Most design systems die after the first release. Everyone's excited for two weeks and then the product grows and the system stays still. Nothing fancy. Just consistent care.