A quick-reference index of what I do, backed by where I've actually done it.

Whether I have a research team or just need answers, I can find them. The depth of research matches what's actually at stake, not just what's convenient to skip.

Good UX strategy is business strategy. My MBA gave me the vocabulary to make that case directly: reframing a stated problem, advocating for a rebuild, or holding my own in a pricing or roadmap conversation.

Complex B2B data doesn't organize itself. I map how information actually moves through a system end to end, and I'm not precious about restructuring it once a cleaner model reveals itself.

I love design systems, unreasonably so. My front-end background means the components, patterns, and documentation I build actually hold up in code, and accessibility is built in from the start, not retrofitted later.

Fullstack, not just "I can talk to developers about code." I design with an eye on what the systems underneath can actually support, and I can step into front-end (and some back-end) implementation myself, so what ships matches what got designed.

I own things end to end and work close enough to engineering to speak the language, documenting thoroughly enough that ownership can move between people without losing consistency. I bring AI tools into that process deliberately, not as a shortcut.

Nothing ships on faith. I test early in low fidelity and keep testing as a design gets more resolved, not just once at the end.

MBA-backed business conversations (pricing, roadmap tradeoffs, stakeholder alignment) show up across nearly every case study here.

Most of my career has lived inside legacy architecture, third-party APIs, and phased engineering rollouts. I design for the constraints that are actually there, not the clean-slate version of the problem.