How I Help
Most of my work starts in one of three situations: a product, technology, or idea still needs a business built around it; an established business is deciding where to invest for growth; or a strategy or investment is not producing the result leadership expected.
Where the work starts
Build
How do we turn this opportunity into a viable business?
You have a product, technology, capability, or business idea, and you still need to decide what should be built around it, or whether the opportunity justifies building anything at all.
Typical questions
- What customer problem are we solving, and for whom?
- What has to be true for customers to adopt it and for the economics to work?
- Which capabilities do we need, and which should we own?
- What should we build, buy, partner for, or not pursue?
- What can we prove before we commit to scale?
Grow
Where should we invest next, and how much opportunity is really there?
The business is established, and leadership has to decide which opportunities deserve more investment and how far they can realistically go.
Typical questions
- Where is the real opportunity once we test the assumptions behind it?
- Which customers, markets, products, or channels justify more investment?
- What does growth depend on: market capacity, conversion, economics, or capabilities we don't have yet?
- Where should we invest more, change course, or stop?
- What should we prove first before committing more?
Perform
How do we get better results from what we've already put in place?
The business has already committed people, systems, and investment, but the expected result isn't showing up consistently.
Typical questions
- What result are we trying to produce, and how is it supposed to be produced today?
- Where do ownership, handoffs, or measurement break down?
- Are we measuring activity because it's available, or the result the business needs?
- What can we improve with what's already in place?
- What has to change in the operating model for the strategy to work?
How I work
I work through problems in a consistent order, shaped by an engineering education and a career that started in Silicon Valley. It isn't always linear, and the problem itself dictates which parts deserve the most attention.
1Define the business questionWhat is actually happening, and what are we really trying to solve or decide?
Clients usually arrive with a goal, a symptom, or an explanation for what is going wrong. I don't assume the initial framing is the right one. I look at the data, process, assumptions, and handoffs underneath it to understand what is actually producing the result. A growth question may turn out to be a market-capacity question. A lead-quality problem may turn out to be a journey and ownership problem. Sometimes the original framing holds up; sometimes the question changes entirely. Only then do I get specific about what leadership needs to decide or change.
2Define the target stateWhat needs to be true when the work is done, and how will we know?
The target state is not always a single business metric. It might be a new process that gets the right data to the right person at the right time, a different organizational structure, a clearly defined ICP for a new product, or a product roadmap for commercializing a technology. The point is to make the future state concrete enough that we can work backward from it, understand what has to change, and know whether we achieved it. This is also where I ask what should now be possible, including what technology, data, or a different operating model could enable.
3Work backward to build the roadmapWhat has to happen to get from where we are to the target state?
Once the target state is clear, I work backward to identify the decisions, capabilities, dependencies, and changes required to reach it, and the order in which they have to happen. The roadmap is not always a detailed project plan. It is the logic of how the business gets from where it is today to the state we have defined.
4Evaluate the roadmapCan this work here, and if not, what needs to change?
I test the roadmap against the realities of the business: economics, organization, processes, systems, data, technology, capabilities, and external dependencies. When part of the path is not feasible, that does not automatically kill the idea. It may mean changing the path, narrowing the scope, sequencing the work differently, using capabilities already in place, or designing an MVP or pilot to prove the underlying idea. The objective is to arrive at one or more paths that can realistically work, along with a clear view of what still needs to be proven.
5Make the strategic choicesWhich path are we going to take?
Once the viable paths and tradeoffs are clear, leadership has to choose. That can mean deciding what to pursue, what to defer, where to invest, what to own, what to get from partners, and what not to do. The result should be an explicit direction and the commitments that go with it, not a menu of alternatives.
6Build, execute, and measureHow do we operationalize the roadmap and know it's working?
Once the direction is chosen, the work is to put the roadmap into operation, manage the execution, and measure whether it is producing the target state we defined. In a fractional role, I may lead that work directly; in an advisory engagement, I work with the leaders who own it. As execution creates new evidence, we adjust.
What technology makes possible
Technology shapes what a business can be, so I treat it as part of defining the target state and the path to it, not as tools to apply once the strategy is set. I look at what data, systems, automation, AI, and other technical capabilities make possible as part of the business problem itself. The question is: what should be possible, and what combination of business and technical capabilities would make it possible?
Read my perspective on AI →See how these kinds of questions played out in real engagements.
See examples of my work →Ways to work together
You work directly with me. The form of the engagement depends on the question, the work required, and how much ownership you need me to take: from ongoing advisory support, to a defined piece of work, to embedded executive leadership.
Strategic Advisory
Ongoing work with a CEO, founder, or senior leader on important business questions and decisions. It fits when leadership owns the work inside the business but wants an experienced outside perspective to challenge assumptions, work through alternatives, and help make the choices.
Defined Engagement
A focused engagement around a specific question, opportunity, investment, or performance problem. The scope is defined around the work required to reach a decision or outcome, rather than an ongoing advisory or operating role.
Fractional Executive Leadership
Embedded executive leadership when the business needs someone to take operating responsibility for a significant initiative, transformation, or area of performance. I work as part of the leadership team and own the work through execution. Fractional COO is one form this can take.
What you can expect
- Direct involvement from me throughout.
- The initial framing challenged before a solution is assumed.
- Alternatives and tradeoffs worked through, not hidden behind a single recommendation.
- An MVP, pilot, or staged rollout when that's the best way to prove the idea first.
- A recommendation to bring in a specialist when the situation needs one.
Have a business question worth working through?
Tell me what you're trying to figure out. We can start with the question itself and whether it makes sense to work on it together.
Start a Conversation