Designer. Frontend thinker. Systems builder.

Over 8+ years I've worked where product design, engineering, and business overlap — the places where most products quietly get confusing. My job is to make complex systems make sense: to users, to the team, and in the code. I lean on clarity-first design that reduces cognitive load, accelerates onboarding, and drives adoption.

I started as a frontend developer, which still shapes how I design. I think in objects, states, and edge cases, and I design the product architecture and mental models — the objects, relationships, and workflows — that everything else is built on.

Over time that grew into a broader practice: research, information architecture, AI interaction design, design systems, and the marketing sites that bring people in. Today I run a design studio and use AI workflows — including Claude Code — to move from thinking to working systems faster.

Clean visuals are the easy part. The hard, valuable work is upstream: architecting the domain model behind the interface, defining how data and system behavior fit together, surfacing the business logic and assumptions the product runs on, and shaping what it must reliably produce.

So I treat it as a repeatable discipline: bring structure to complexity before pixels, pressure-test the model against real edge cases, and keep refining until the product is something people can understand, use, and trust.