How I work
I treat every project like I co-own it — not just the screens, but the problem behind them. Before opening Figma, I want to understand who we're building for, what's breaking in their experience, and what success looks like for the business. That clarity is what turns good-looking screens into products people actually use — and that stakeholders actually want to ship.
My best work has always come from being deeply embedded with product managers, engineers, and real users — not designing in isolation and throwing specs over the wall. I bring structure to ambiguous problems, facilitate alignment when priorities conflict, and keep the user's perspective anchored throughout the build.
On the craft side, I think in systems. Whether it's a single feature or a full redesign, I design components that scale, document decisions as I go, and actively reduce future design debt. These days, AI is a big part of how I work — not as a shortcut, but as a way to do more rigorous research, faster synthesis, and better documentation within the same sprint.
1
Own the full design lifecycle — from 0→1 scoping to post-launch iteration
2
Collaborate early and often with engineers to avoid expensive late pivots
3
Build and maintain design systems as a shared team resource
4
Use AI tools for workflow automation
5
Communicate decisions clearly — rationale, trade-offs, and what was left out
