About

I am a Principal-level product designer focused on systems, leverage, and long-term impact.

I design product ecosystems, workflows, and design systems that help organizations make sound decisions. My work sits at the intersection of customer experience, business economics, and emerging technology. I am most effective in high-stakes environments where problems are not fully defined and teams need structure they can trust.

Quick Proof

15+ years designing complex enterprise and platform products
Shipped 150+ UX initiatives across multiple product lines in 2025
Helped drive 83% YoY growth in wholesale fees
Built AI-assisted design-to-dev workflows using Figma MCP + Claude Code

What I Do

Platform and workflow design: I design end-to-end flows that reduce confusion and rework.
Design systems that teams actually use: Tokens, patterns, standards, and contribution workflows that scale.
AI trust and clarity: I design AI experiences that reduce user anxiety and drive adoption.

How I Operate

Start with first principles and the real constraint: I define the user goal, business goal, and system constraints so we solve the right problem before we design anything.
Make tradeoffs explicit early: I write clear decision criteria (time, risk, scope, quality) so everyone knows what "good" means and why we chose option A over B.
Run tight design plus engineering alignment: I partner with engineering from day one using working sessions, dev-ready specs, and edge-case reviews so implementation matches intent and delivery stays predictable.
Build reusable systems, not one-off screens: I create patterns, tokens, and contribution rules that scale across teams, reduce rework, and speed up future delivery.
Document decisions so teams can move without me: I capture the why, what, and next steps, then push updates to the right channels so product, stakeholders, and leadership stay aligned without chasing status.

Design Philosophy

My design philosophy is built for scale.

These principles show up in how I run cross-functional alignment, build scalable patterns, and ship dev-ready work that teams can maintain.

Integrity

Integrity is how I protect quality while moving fast.

Clarity is respect. I make intent, decisions, and constraints visible so people do not have to guess.
Consistency builds trust. I use patterns, rules, and standards so products feel coherent across teams and time.
Teach the system, not the answer. I mentor by sharing reasoning, frameworks, and tradeoffs so others build judgment, not dependency.

In practice: I work across levels from junior designers to managers to raise the bar on research, design systems, and execution. I share context early, explain decision logic, and invite challenge. When people understand how decisions are made, they stop waiting for permission and start leading.

Courage

Courage is how I keep teams honest and outcomes real.

I step into ambiguity. When direction is unclear or timelines compress, I help the team name the risk and choose a path.
I ask hard questions early. That prevents late-stage surprises that burn trust and budgets.
I model curiosity over ego. I encourage "why" before "how" so we solve the right problem, not just the visible one.

In practice: I create space for direct thinking. I surface assumptions, test them quickly, and make tradeoffs explicit. Courage is not being loud. It is being steady when the work gets uncomfortable.

Unity

Unity is how you turn talented people into a delivery engine.

Shared thinking beats handoffs. I bring product, design, and engineering into the same problem-solving loop.
Shared artifacts reduce friction. I use clear specs, prototypes, and decision logs so teams align without constant meetings.
Shared ownership raises the bar. When outcomes belong to the team, quality and speed improve together.

In practice: I blur the lines between roles with shared language and shared workflows. I use practices like peer-designing to improve idea quality, increase trust, and reduce rework. Unity is not consensus. It is alignment that accelerates execution and compounds impact.

How I Operate Day to Day

I operate with intention, consistency, and respect for people's time and attention.

Day to day, this means:

Aligning on the problem before debating solutions
Making decision criteria explicit so trade-offs are visible
Working alongside product and engineering rather than through handoffs
Using shared artifacts to keep thinking transparent and reusable
Measuring progress by outcomes, not activity

I ask why early to prevent costly rework later. I surface risks while they are small. I document decisions so teams can move independently without losing context.

I balance urgency with thoughtfulness. When speed matters, I help teams move decisively. When stakes are high, I slow the work just enough to improve decision quality.

My goal is simple: help teams think clearly, move together, and ship work worth standing behind.

About Me