Leadership

Every interface decision is downstream of an organizational decision, a strategy decision, a business model decision. I've never been interested in designing screens in isolation. The work that matters happens at the level where design and strategy are the same conversation, and that's where I try to operate.

Most design problems are legibility problems in disguise. The team can't agree on what they're building. The product can't explain what it does. The user can't find what they need. Whether I'm directing a team or sitting with a founder, my role is to find the frame that makes the problem solvable. Sometimes that's a product strategy document. Sometimes it's a single well-placed question.

The most expensive design mistake is asking people to learn when they don't need to. I've designed cockpit interfaces for test pilots and command systems for naval operators. The lesson is always the same: understand the existing system well enough to know what's worth keeping. Innovation earns its place by answering one question: what does this give the operator that the convention didn't?

I measure the success of my leadership by the clarity and confidence of the people I work with, not by the number of features shipped. That means building decision autonomy into the team, creating real space for development, and making it genuinely safe to ask the questions that expose wrong assumptions, because those questions are usually the most valuable ones in the room. I invest equally in relationships inside the team, across the organization, and with clients. The trust that makes good work possible is built long before the work begins.