How I work
Designing for systems, not features
My focus is on building interoperable, scalable systems rather than isolated screens. I think in terms of platforms, patterns, and long-term extensibility—designing solutions that can support future use cases, teams, and growth without constant rework.
Embracing ambiguity and define direction
I’m most effective in spaces where problems are not well-defined. I help teams move from ambiguity to clarity by framing the problem, exploring tradeoffs, and making principled decisions that balance user needs, business goals, and technical constraints.
Partner deeply with product and engineering
I work closely with PMs and engineers as a thought partner, not a downstream executor. This means shaping strategy early, aligning on intent, and making design decisions that are technically sound, realistic to ship, and meaningful to users.
Optimize for leverage and impact
I prioritize work that creates outsized impact—design systems that reduce friction, patterns that accelerate delivery, and decisions that unblock multiple teams. If a solution doesn’t scale beyond the immediate problem, I reconsider it.
Raise the bar for teams
Beyond individual contribution, I invest in people and design maturity. I hire thoughtfully, mentor designers, give clear feedback, and build shared standards that help teams move faster while maintaining quality.
Reflect and iterate
After shipping, I look at outcomes—not just outputs. I reflect on what worked, what didn’t, and how the system or process can be improved next time. Learning compounds when it’s intentional.