I build engineering teams that deliver outcomes.

How I lead

Clarity comes before autonomy.

You can't expect someone to take ownership of a problem they don't understand.

People need to know what we're trying to achieve, why it matters, and where they can make decisions.

High standards and empathy go together.

Avoiding difficult conversations doesn't make someone a caring leader.

People deserve clear expectations, honest feedback, and a fair opportunity to grow. You can care deeply about people and still hold them accountable for their work.

Outcomes matter more than output.

A team can ship ten features and still accomplish very little. It's easy to confuse being busy with making progress.

I care about what happens after we ship. Did customers benefit? Did the business improve? Did we actually solve the problem?

Fix the system, not just the symptoms.

When delivery slows down, the instinct is to add more people, more meetings, or more pressure.

But often the problem is too much work in progress, unclear priorities, or decisions that take too long. I've seen teams deliver more by taking on less.

Good judgment matters more than ever.

AI is making software faster and easier to build. But faster execution doesn't tell us which problems are worth solving.

Knowing what to build, what to simplify, and when to say no matters even more when the cost of implementation falls.

Stay close to the work.

Engineering leaders don't need to write every line of code. But it's hard to make good technical decisions when you're disconnected from the technology and the people building it.

I stay hands-on because understanding the work makes me a better leader.