I usually start by understanding what the product needs to do, then shape the interaction and visual design around that.
Define the problem at the system level before designing interfaces.
Create interaction models and information architecture that make complexity understandable.
Shape the experience so it feels clear, predictable, and usable in practice.
Work closely with engineering so the design holds up in production.
My design work often spans:
I prioritize clarity, predictability, and usability so experiences remain understandable even as products scale.
I use research across design, product, and business questions. Depending on what we need to learn, that can mean understanding users, testing an experience, evaluating a product direction, or challenging assumptions before the team invests too far.
I stay close to product and engineering throughout the work, especially when technical constraints affect the interaction model. That helps us catch problems earlier and keeps implementation closer to the design intent.
I am most effective when design is used to:
That is where design has the most leverage.
