I’m a product designer with a software-engineering foundation, specializing in real-world enterprise systems, operational workflows, and data-rich decision tools. I help teams make sense of complexity—so what matters gets the attention it deserves.
02 / About
I work best when the software is complicated, the workflow matters, and design has enough ownership to connect product intent with implementation reality.
A professional point of view
The interface is the visible part of the work. It isn’t the whole work.
A useful interface follows from understanding the user’s work, the information and decisions involved, the business rules, technical constraints, and the relationships between them. Making software look resolved cannot substitute for making the underlying system coherent.
01 / Engineering
I began professionally as a software developer. I understand that implementation has architecture, state, data, APIs, constraints, and consequences.
Technical fluency helps me ask better questions earlier, understand tradeoffs, and collaborate with developers without treating engineering as a downstream production function.
02 / Transformation
Digitizing paper forms and spreadsheets can be valuable. The larger question is: what becomes possible now that the workflow is software?
03 / Ownership
I work best with users, domain experts, product managers, developers, data specialists, and decision-makers. I am less interested in operating as a design service that receives requirements and produces screens.
Meaningful ownership means understanding why the product should exist, what outcome it needs to create, and where design judgment can change the direction—not only the interface.
Career chronology
Software development → visual communication → product design → complex enterprise product ownership
