Leadership

Less about screens. More about environments.

My job as a UX leader isn't to make the prettiest artifact — it's to build the conditions where a whole team can make great decisions. Here's how I think about it.

Pillars

Clarity over cleverness

Ambiguity is expensive. I turn fuzzy business problems into a clear point of view a whole team can rally around.

Environments, not artifacts

The best design leaders spend less time creating screens and more time creating the conditions where great design happens.

Research-driven, business-anchored

Decisions come from evidence — customer feedback, workflow observation, and market signal — but they always ladder up to business outcomes.

Growth through trust

Mentorship, honest critique, and cross-functional trust are how a design team becomes more than the sum of its people.

Frameworks I use

01

Design Maturity Model

A pragmatic model I use to assess where an organization sits — from ad-hoc UX to embedded product design — and what the next honest step is.

02

Feedback Rituals

Weekly critiques, quarterly portfolio reviews, and a repeatable customer-feedback loop that becomes an internal process, not a one-off ask.

03

System Governance

A lightweight governance model that keeps a design system alive after launch — contribution paths, ownership, and adoption reviews.

"Good UX outcomes depend on organizational alignment, not just design quality."

— Lesson from ten years of leading teams