Work

The Best Idea Wins

Innovation doesn't respect org charts. I've seen breakthrough ideas come from junior designers, engineers, PMs, and support teams — and I've seen the loudest voice in the room kill a better one. My job is to build the conditions where good thinking surfaces and gets resourced: open crits, cross-functional reviews, and a culture where challenging the current direction is expected, not exceptional.

Data Is a Discipline, Not a Shortcut

Shipping ads and commerce experiences to hundreds of millions of people taught me that data is the only honest feedback loop. I build teams that treat experimentation as a core design practice, not a post-hoc validation step. But metrics tell you what happened, not why. The real discipline is holding both: the quantitative rigor that tells you what's true, and the qualitative depth that tells you what matters.

Clarity Enables Autonomy

The most expensive thing I can do is give a team unclear direction. At the scale I've operated, unclear direction multiplies fast. When the destination is shared — the user problem, the business outcome, the definition of success — talented people don't need to be managed; they need to be trusted. I stay close through design crits, dogfooding, and end-to-end experience reviews, not to direct, but to make sure the work stays connected to what we set out to solve.

Protect the Conditions for Bold Work

In ads and commerce, the safe choice is always to iterate on what's already converting. Ambitious design — the kind that creates new formats, new patterns, new ways for people to interact with products — requires permission to fail, and that permission has to come from the top. I set the tone, but more importantly, I shield teams from the pressure that defaults people to safe choices: arbitrary timelines, risk-averse stakeholders, the organizational gravity toward what's already been built. The trust battery charges through consistency: I say what I mean, I follow through, and I go to bat for the work.

Challenge the Status Quo

Every team inherits constraints — legacy patterns, accumulated decisions, mental models that made sense three product cycles ago. The ones that are genuinely load-bearing deserve respect. The ones that are just habit deserve to be questioned. I push teams to distinguish between the two, and I give them cover to challenge what's familiar, even when it's uncomfortable.

Structure Shapes Outcomes

How you organize a team is itself a design decision, with consequences that show up in the work. At Microsoft, I restructured my team around customer journey phases instead of platform silos. Within three months, the product org followed. How people are grouped determines what problems they see, who they talk to, and where they focus their energy. I pay close attention to structure, both within design and in how design connects to the broader product organization.