About me

I’m a product designer who thinks like an engineer. I’ve spent over a decade building complex software, first as a frontend engineer and then as a designer, the kind where the user is sharp, the edge cases are real, and a vague decision quietly turns into an expensive one.

Daniel Morris
Daniel Morris working in the office

I started out as a frontend developer, which means I was writing HTML and CSS long before I was making Figma files. That history still shapes how I work: I’d rather test an idea in something running than argue about it in static frames, and I stay close to the medium the product actually ships in. It keeps the work honest.

Constraints are the part I enjoy. Developer tools, low-code platforms, technically dense interfaces, these are domains where good design isn’t decoration; it’s the difference between a product people trust and one they fight. That’s the work I keep choosing.

How I work

I’m most useful early, before the brief has hardened into assumptions. I do the research to find the problem actually worth solving, then stay through execution so the answer that ships is still honest to what we learned, not whatever survived the handoffs.

And I’d rather show than tell. I use Figma for systems and component work, and Claude Code to build interactive prototypes that are quick enough to put in front of users and real enough that they react honestly, instead of politely.