Operating Principles

“I could lead a team that designs a perfect toilet or a web application.”

Good products emerge from the same constraints, regardless of industry or medium. User needs, requirements, dependencies, time, budget, and quality are universal.

1. Start With the Problem, Not the Solution

I don’t start with features, layouts, or technology. I start by getting clear on the user problem, the business objective, and the constraints we’re operating within. Once those are understood, the solution usually becomes obvious. Skipping this step almost always leads to rework later.

3. Build Systems That Scale

If something requires constant manual effort to stay relevant, it won’t hold up over time. I favor automation, clear structure, and repeatable systems over one-off solutions. It may take more upfront work, but it pays off quickly in quality, consistency, and trust.

5. Treat Constraints as Part of the Design

Time, budget, technical dependencies, and organizational realities are part of the problem, not obstacles to work around. I treat these constraints as design inputs that help teams make better decisions and focus on what actually matters.

2. Focus on Outcomes, Not Deliverables

Shipping work isn’t the goal — improving outcomes is. I prioritize based on impact, effort, and risk, not on how quickly something can be delivered. This keeps teams focused on solving the right problems instead of just staying busy.

4. Respect How Different Users Make Decisions

Not all users want the same experience. Some want to move fast and get in and out. Others want to explore, compare, and understand before acting. I design products that support both without forcing users down a single path.

6. Lead With Clarity, Then Get Out of the Way

My role as a leader is to make sure teams understand the problem, the priorities, and what success looks like. Once that’s clear, I trust teams to do the work. Strong products come from accountability and clarity, not micromanagement.