How I think
Frameworks should clarify the work—not replace judgment.
These principles are not a proprietary operating system or a stack of branded diagrams. They are practical ways to diagnose problems, connect decisions and turn good thinking into action.
Principle 1
Lead at the intersections.
The most consequential business problems rarely belong to one department. They live at the organizational intersections, and no result arrives until every function delivers its part. Functional leaders often focus on the one they manage and treat the others as someone else’s responsibility. Business leaders know to connect across functional lines.
You cannot collaborate with a function whose constraints you do not understand. Understanding comes first, and collaboration follows from it. Building that collaboration is the leader’s work — it does not happen because an organization chart puts two teams under the same executive.
Questions to ask
- Which function sees something the others are missing?
- Where are two functions measured in ways that pull against each other?
- Which function is the real constraint here, and does the plan respect it?
- What must a function be able to do that it cannot do today?
- Are we optimizing one department at the expense of the business?
Principle 2
Just because we can build it doesn’t mean we should.
AI has reduced the time, cost and specialist effort required to turn an idea into a working product. That is valuable—but it also puts more products, features and experiments into the system. More output does not automatically create more customer value.
When almost any plausible idea can be built, the differentiating questions move upstream.
The ability to build is no longer sufficient justification for building. Strong product and business leadership includes the discipline to kill weak ideas before they absorb more capital, attention and organizational credibility.
Questions to ask
- Why should this exist?
- What meaningful customer problem does it solve?
- Why will customers choose it, pay for it or change their behavior?
- How will it reach the market successfully?
- What evidence would cause us to stop?
Principle 3
Structure → Process → People → Outcomes
Organizations often jump directly from disappointing outcomes to conclusions about people.
Start earlier. Does the structure create clear ownership? Does the process support good decisions and execution? Do capable people understand what is expected and have what they need to deliver?
People matter enormously. But asking people to compensate indefinitely for confused structure and broken process is not leadership.
Questions to ask
- Is ownership genuinely clear?
- Where do decisions stall or get reversed?
- Which handoffs repeatedly fail?
- Are we evaluating people inside a system that enables success?
Principle 4
Strategy → Execution → Accountability
Strategy is not complete when the presentation is finished. It becomes real when priorities change, resources move and people understand what they must do differently.
Execution requires choices. Accountability requires clarity about commitments, evidence and consequences—not simply more meetings or more urgent language.
Accountability is where most of this breaks down. Organizations create handoffs to divide work, but handoffs also divide accountability: a team completes its deliverable, passes it to the next function and declares success, even though the business outcome that justified the work has not happened yet. A department’s output is not the business outcome. The owner of an initiative stays engaged across the boundary until the investment produces the result it was meant to create.
Questions to ask
- What will we stop doing?
- What changes on Monday morning?
- Who owns the outcome rather than the activity?
- Who remains accountable after the handoff?
- What evidence will tell us whether the strategy is working?
Principle 5
Solve the root cause—not the visible symptom.
My engineering background shaped how I approach business and leadership problems. Before changing the organization, replacing a person or prescribing a familiar answer, understand how the system actually works and identify the root cause.
The first explanation is often a symptom: missed commitments, weak sales, slow decisions, poor accountability or conflict between departments. Solving that symptom may produce temporary movement while leaving the underlying constraint untouched.
Experience is valuable, but it creates its own risk: recognizing a familiar pattern too quickly. Strong problem solving tests the pattern against the facts, separates evidence from assumption and traces the problem far enough upstream to understand why it keeps recurring.
Questions to ask
- What do we know, and what are we assuming?
- Is this the problem or evidence of a deeper problem?
- Where in the system does the failure first appear?
- What would have to be true for the obvious explanation to be wrong?
- Will this solution remove the cause or merely relieve the symptom?
Where these come from
I did not assemble these from books.
Each one is a pattern I hit as an operator — carrying a P&L, leading functions I had never worked in, and being accountable for outcomes that depended on teams I did not manage.
Principle 4 is the clearest example. For years I watched Sales, Marketing and Product pull against each other, each function doing its job correctly while the result fell through the gaps between them. When I began operating as the person accountable for the whole commercial outcome — not just product definition and delivery — Sales and Marketing came to rely on it, and it became how we worked.
If these resonate, you have probably been the one expected to fix it.
Let’s talk about what’s on your mind.
The useful work begins when we can see the technical, commercial, financial and organizational realities at the same time.
Start a conversationA brief, confidential conversation about your role, the situation and whether I’m the right person to help.