About .
How I approach design.
I design products by focusing on finding the right problem to solve.
I spend my time balancing human needs with business goals, paying close attention to how products behave over time, where intent and usage diverge, and where systems break down under real-world constraints.
For me, design is less about producing artifacts and more about shaping products that hold up once they’re in use.
What experience has taught me
Over time, and across multiple 0–1 efforts, I’ve learned that strong products rarely come from personal conviction alone.
What I believe will be useful is often less important than what emerges through real usage. Iterating on user needs consistently leads to better outcomes, even though users don’t always know what the solution should be. My role is not to follow requests blindly, but to listen carefully, interpret patterns, and decide what actually belongs in the product.
I’ve also learned that possibility is not the same as necessity. Just because something can be built doesn’t mean it should be. Friction is not always a failure. In many cases, it’s what creates clarity, focus, and trust.
Working in fast-paced environments taught me that products often move faster than design. You can’t wait for perfect clarity, but you also can’t outsource judgment. Shipping quickly matters not because speed is the goal, but because it shortens the feedback loop and accelerates learning.
Design in an AI-driven world
As design tools accelerate execution, the value of design shifts away from producing interfaces and toward making sound judgments.
AI can generate layouts, flows, and variations quickly. It cannot determine what is necessary versus merely possible, where clarity should take precedence over completeness, or which tradeoffs are worth making. Those decisions depend on how problems are framed and how constraints are understood.
I use AI as a tool for exploration and stress-testing ideas, not as a substitute for understanding. Its value is highest when it helps surface weaknesses, not when it generates answers.
I see design’s role as making complex systems legible, responsible, and trustworthy, especially as automation increases speed without guaranteeing understanding.