Over the past decade, I’ve teamed up with all kinds of UI designers. As a front-end engineer, my main job is to turn their designs into working interfaces—but sometimes, I wonder what’s going on behind the scenes.

Are these interfaces just there to look pretty?
What’s the actual goal?
How do designers figure out what users really want?
What’s their approach to building the system’s UI, and how do they get it done? And when it comes to documentation, what’s the process there?

From what I’ve seen, a lot of the time, lower sales conversions can be traced back to a client’s design choices. I’d love to dig even deeper into this with more data. For now, though, designing with real customer feedback in mind is still the best way I’ve found to boost conversions.

To get a better handle on the design process, I’ve read a bunch of books, like:

• Laws of UX: Design Principles for Persuasive and Ethical Products – Jon Yablonski
• The Exhibition and Experience Design Handbook – Timothy J. McNeil
• 101 UX Principles (2nd edition): Actionable Solutions for Product Design Success – Timothy J. McNeil
• Handbook of Usability and User-Experience – Francisco Rebelo, Marcelo M. Soares, Tareq Z. Ahram
• Don’t Make Me Think, Revisited – Steve Krug

*If you have any book recommendations, please send them my way by email!

To me, design is all about bringing order to chaos. That’s why every interface design should take the whole system into account.

A quick note: When you hire a UX/UI specialist, share your brand’s vibe—but then let them do what they do best. If you’re always telling them how to shape your brand, you’re probably wasting your money. It’s better to bring on someone you trust and let them shine.

Alright, let’s start building a UI framework together.