The market no longer rewards what you build.

Who it's for

Leaders building and bringing software products to market.

When the market stops rewarding output, building more becomes the expensive way to stand still - spend that doesn't move the numbers, teams busy on the wrong things, and losing ground to whoever adapts first.

What's possible

Every part of the company points at the same thing - the outcomes that matter to your users and the business.

Success isn't how much you build; it's whether the results move. That's a whole-company sport: product, design, and engineering own the outcomes, not just the outputs; sales sells what actually delivers value, not whatever closes; marketing carries the value users came for; leadership hands teams the problems worth solving; finance funds durable teams; and customer success feeds what it learns back into what the company builds next.

Users feel all of it - products that reliably move the results they care about, instead of a stream of features nobody asked for. The company wastes less on what doesn't matter and keeps winning as the market moves - because a company organized around outcomes can adapt, and one organized around output can only keep building.

What I bring

Since I have worked the whole arc - reaching a first product, scaling it, reinventing a stalled one - and every seat on it, I can meet you where you are.

My work runs across a company in both directions: east-west, the whole product lifecycle - product management, design, and engineering; and north-south, from the people doing the work up to the executive team setting direction.

I have been a CEO, three times. I have led product management as a CPO, led engineering as a CTO and VP of Product Development, and led all three together - product, design, and engineering - as a CPO and CPTO. Before all of that, I was a software engineer and a product manager. So wherever the work is stuck - between functions or between levels - I have stood on both sides of it.

Working both ends of the same arc, I have helped early companies find product-market fit the lean-startup way - that work shows up in Eric Ries's The Lean Startup and Ash Maurya's Running Lean - and led the move to the Product Operating Model once a company has outgrown how it first found fit.

How I help

The work is with leaders across the company, on two fronts: changing how the product functions (engineering, product management, and product design) work, and holding that change together across the boundaries with the rest of the company. I shape every engagement to where the company actually is - whether a fixed-scope read, a coaching engagement, or an advisory or board role.

The engagement to get a company there usually takes one of these shapes:

• Product organization assessment. A fixed-scope, focused look inside it and at its boundaries - what's moving outcomes, what's in the way, and where to start.
• Leadership coaching on putting the product operating model in place. The creation and adoption of a product operating model unique to the company - including the strategy and incentives that align what teams work on, and how you measure them, to the outcomes the business needs.
• Product and engineering leadership coaching. Aligning the CPO/CTO relationship and the line between them through the lens of the product operating model - one of the boundaries the work has to hold together.
• Building product leadership. Defining, hiring, and onboarding the leadership the next stage needs - across product management, design, and engineering - so the roles actually take.
• Engineering, product management, and design coaching on empowered teams. The creation and adoption of empowered teams working together on outcome-driven discovery.
• Stepping in to lead. On a selective basis, taking a hands-on leadership role where that's the right way to help the company make progress.

Let's talk →

How I work

I start by understanding, not prescribing - I learn what's actually happening, rather than walk in with a prescribed answer. I locate the hard "what to change" decisions in evidence and discovery - not in opinion or edict - and I keep the work pointed back at the people the company is serving, connecting the business model, the operating model, and the product through their unmet needs.

I look beyond the product team to include who's doing product work across the company. Inside the product org, I get people reaching past their titles - an engineer in a customer conversation, a designer or PM building a working prototype. I incorporate people outside the product team who are already doing some product work without the title, e.g. a Customer Success Manager testing real demand for a change - now possible more than ever due to GenAI tools.

When something's stuck, I look for what's stopping progress - what would have to be true for this to work - before reaching for "do more." I read the human systems as closely as the org chart - what's really happening between people, on a leadership team, inside a team, at the boundaries - not just what's on the whiteboard. That's usually what makes the operating model work in practice rather than on paper.

Then I push to prove it end to end before optimizing anything - one real product, one real customer outcome, all the way through, before tuning the parts. Getting a single instance to work end to end is the hard part; once it exists, making it better is the easier part. I move from the whole down to the detail and back up, continuously, so the parts stay connected to the outcome.

Let's Talk

If you recognize yourself in any of this, I'm easy to find. A forty-five-minute conversation, peer to peer - what you're navigating, and whether there's a fit. No pitch, no process, no intake form, and no interest in selling you more than you need.