Professional
Leadership Philosophy
How I lead, and why
Enterprise UX: making it a structural decision, not a talent decision.
I’ve watched brilliant ideas stall, good people burn out, and teams with real aptitude still miss the mark. Almost never because the talent was missing. The best work isn’t linear, but it can be steady and predictable when the system around it is sound. My job is to build that system, so teams can spend their energy on the work instead of the friction around it. I pursue durable structure over hero moments, so a large organization can move with the speed and care of a small one, because every piece of it is built around people.
My leadership principles
01
Invisible work is enterprise risk.
When delivery, prioritization, and resourcing have no clear owner, the risk hides in plain sight until it surfaces as a missed date or a team that’s worn-out. I build the systems that make the work visible: intake, dashboards, alignment rituals. It ensures every stakeholder knows what’s real, what’s next, and where they can help.
02
Structure is a form of care.
People aren’t processors, and teams aren’t infinitely elastic. In an unclear system, your best people absorb the chaos quietly until the day they leave. I define roles, decision rights, and ownership clearly, so people have room to focus, work worth protecting, and no reason to walk.
03
Alignment beats enforcement.
Real momentum doesn’t come from a top-down mandate. That structure tends to fall apart by the second quarter. I’d rather give everyone the same few things: a clear vision, a shared focus, and a standard high enough that the team can act on it without me in the room.
04
Coach the seniors; change the system.
I don’t scale by doing more myself. I scale by making other people more capable of leading. If the system falls apart the moment I leave, I didn’t build a system. I built a dependency.
05
Data neutralizes resistance.
Good telemetry turns opinion into evidence and defensiveness into decisions. I lead with numbers, not because people are numbers, but because numbers get everyone out of the argument and back to the work.
50–65%
Reduction in rework cycles
~80%
Sprint commitment accuracy
$8M+
In Program governance across three regions
The part that isn't about the enterprise
These principles were forged in the enterprise, but they aren’t really about it. Strip away the Jira boards and the stakeholder maps and they say something simpler: people do their best when the space around them is built with care. That’s true for a design team of fifteen. It’s just as true for a classroom of teenagers.
“
Leadership isn't about having all the answers. It's about creating the conditions for others to find theirs and building something greater together.
What I'm focused on now
Leading
Enterprise UX teams and systems that create clarity and impact.
Creating
New artwork exploring identity, grief, and becoming.
Building
The Embodied Creative program for youth and communities.
Exploring
The relationship between creativity, healing, and leadership.
Let's create something meaningful.
I'd love to connect about design, leadership, or collaboration opportunities.