Craft in service of systems.
Systems in service of humans.

Every system serves someone. A booking flow, a discharge process, a rebooking algorithm at 2 AM — each one is a decision about who matters and how much. Design is where that decision gets made, whether anyone in the room names it or not.

I think in systems. Not just how they work, but who they work for — and who they leave behind.

How the same process that feels seamless for one person becomes a wall for another. That's not a UX problem. It's a dignity problem. And it's the reason I design.

I believe design leadership is a practice, not a title. It's the practice of seeing entire systems through the lens of human experience, having the courage to advocate for the people inside them, and building up the designers behind you. Empowering them, challenging them, making them better than you found them. Influence isn't given. It's earned by making the work undeniable.

I believe empowerment is performance. The leaders I admire most aren't the ones who hoard influence or gatekeep expertise. They lift others up. They lead with generosity even when the pressure is high. A leader who builds capability in others compounds her impact. A leader who only extracts output eventually runs out of both.

I believe the stakes demand dignity, not speed. When you're designing for someone who is sick, scared, exhausted, or stranded, you don't get to move fast and break things. Aviation, healthcare, wellness. These aren't products optimizing for engagement. They're systems where design decisions carry real weight, where getting it wrong is measured in human wellbeing, not conversion rates. Design, for me, is a form of service. Service to the humans inside the system. Service to the dignity they deserve. Service to the possibility that the system could be more humane.

The teams I want to be part of are organized for clarity. Systems designers hold the big picture: service maps, cross-channel flows, the ecosystem view. Craft specialists own the details where the system meets the human. The IC design leader has deep craft and systems fluency. They influence through quality, not headcount. That's the role I want to grow into.

Inside that structure, designers don't sit adjacent to product and engineering. They sit inside the same system, co-creating from problem framing forward. Critique is a practice, not an event. Work gets reviewed against the system it serves, not against aesthetic preference. Growth means craft depth, systems fluency, and the ability to influence without authority. Not output volume. Not visibility.

What I want to add to that kind of team is rigor and care, held together. Rigor without care produces burnout. Care without rigor produces mediocrity. The best teams I've seen hold both, and they do it through leaders who are kind and empowering even when the pressure is high. People who lift others up instead of hoarding influence. That's the kind of environment where people do the best work of their careers and stay long enough to compound it.