ApproachHow I think about product, and how I actually ship it.
I'm a product designer who trained as an engineer, so I rarely stop at the mockup. I design the work, build a fair amount of it, and ship a steady stream of my own ideas in between. To me, design and code aren't two jobs. They're one loop.
LearnStart from the best existing tools. Understand what already works, and why, before inventing anything.
ResearchDig into the problem, the users, and the constraints until the real question is obvious.
WireframeGet the idea out fast and rough, often thinking it through with AI tools like Claude before committing to pixels.
ValidatePut the cheap version in front of stakeholders early, so the expensive work starts on a direction everyone has agreed on.
DesignBuild it in Figma on real components and styles, never one-off screens. The system carries the consistency so my judgment goes to the hard parts.
PrototypeMake it interactive, pressure-test the flow, and send it for approval.
ShipHand off to engineering and stay through the build. I assist on the implementation, hold the intent, and answer the questions that only surface once something is actually being coded.
- The hard part of enterprise tools is the people, not the pipes.
- Design isn't finished at the mockup. It's finished when the shipped thing matches the intent.
- Start from what already works. Most problems are retrieval, not invention.
- Components are where taste scales. Build the system once, spend judgment on what's actually hard.
Design engineer, founding designer, or senior product roles where design and engineering aren't two departments. I do my best work where I can own a surface end to end, from the first wireframe to the shipped code.
Let's talk