How I Lead
I care deeply about the work — and just as deeply about the people doing it.
Over time, I've learned that strong outcomes don't come from clever ideas alone. They come from clarity, trust, and teams who feel supported enough to do ambitious work. The principles below shape how I design, how I give feedback, and how I show up for the people around me.
Raise the bar, then help people reach it.
I care deeply about craft and quality, and I'm not shy about setting high standards. But standards without support aren't leadership.
I invest time in clear feedback, thoughtful critique, and helping designers see what "great" looks like — and how to get there. Sometimes that means pushing a little harder. Sometimes it means protecting space so someone can do their best work without unnecessary noise.
Strong teams don't happen by accident. They're built through consistency, clarity, and care.
Invest in people, not just projects.
Projects ship. People grow.
I think about development intentionally — what someone wants to get better at, where they feel stuck, where they need stretch. I try to create an environment where it's safe to ask questions, challenge ideas, and admit uncertainty.
Psychological safety isn't softness. It's what allows teams to take risks, have honest conversations, and improve faster.
When people feel trusted and supported, the work improves naturally.
Build bridges before you need them.
Alignment is part of the design work.
Some of the most impactful projects I've led required navigating tension across teams, systems, and priorities. I've learned that relationships built early make hard conversations easier later.
Good ideas don't move forward on merit alone — they move when people trust each other enough to build them together.
It isn't done until it's simple.
Shipping something that "works" isn't the same as shipping something clear.
As a leader, I push for simplicity — not minimalism for its own sake, but clarity that reduces cognitive load and makes the right thing easier to do. That often means asking one more question, refining one more flow, or stepping back to see if we're solving the right problem at all.
Simplicity is rarely accidental. It's the result of restraint.
Design for real conditions, not ideal ones.
I design for how things actually work in the world — when technology lags, when incentives are misaligned, when users are under pressure, and when systems aren't perfect.
That mindset influences how I guide teams. I encourage designers to pressure-test their work:
What happens when the app is slow?
What happens when behavior doesn't match our expectations?
The goal isn't perfection. It's resilience.
What my team can expect from me
If you're on my team, you can expect:
Clear expectations and direct, thoughtful feedback
Context for why decisions are being made
High standards applied consistently
Space to disagree and be heard
Support when the work gets hard
I'll push for quality. I'll protect the team when needed. And I'll always be open to learning alongside you.
I'm still learning.
Leadership isn't static.
I'm continually refining how I balance speed with craft, when to step in versus step back, and how to best create space for others to grow without over-directing. The tools we use are evolving, the problems are getting more complex, and I believe the best leaders adapt with them.
I don't pretend to have everything figured out. But I care deeply about getting better — for the team, for the work, and for the people our products serve.