I take the product seat, full-time, interim, or fractional. I rebuild how your team operates around AI and install it. Or I come in for a bounded read and get you to the decision. Same operator discipline in all three. They differ by how much you hand over.
Full-time for the right company. Also interim or fractional. I hold the seat, make the calls nobody's making, and get the team back on a rhythm.
A CPO left, or performance's been drifting for a while. I hold the seat, make the calls nobody's making, and get the operating rhythm back. Direction, ownership, and cadence, reset.
Execution starts with sharp product thinking. I cut the portfolio down to what matters, tie investment to outcomes, and stay in the room for roadmap and product reviews.
Execution rarely breaks on the roadmap alone. It's structural. I read the org design, reset who owns what, and get Product, Engineering, Design, and GTM pulling toward the same outcomes. When it's needed, I help hire the leaders and manage the transition.
Most teams use AI to move faster inside the same workflow. The ones restructuring the workflow itself get a different company. I help the leaders who own the team move from scattered tool adoption to redesigning how their orgs build, validate, and operate. That draws on systems I built and run in production.
Sometimes you don't need someone to hold the seat or rebuild the model. You need the thing everyone keeps circling to actually get decided. Fixed fee, fixed end date.
A focused look at where momentum stopped and why. I take in what's actually happening, from the people doing the work rather than the summary of it, and come back with a position. Not a survey, and not a deck of options.
Pre-work with the people who actually know, then a working session where the decisions get made live, in the room, with everyone watching. I run it and I bring a real position to react to. Progress comes from people reacting to something in front of them, not from a blank page.
A ranked list of what to do first, with my call on every item and a blank line for yours. Where we disagree is the useful part, and that's what the conversation is for. The decision is yours. It always was.
Priorities cut to what moves the business. Roadmaps reflect reality, not internal noise.
Clear decision rights, real ownership, a cadence that ties the team to outcomes. Product, Eng, Design, and GTM move together.
The new way of working is what the team reaches for, not a mandate they route around.
How you build and decide gets rebuilt around AI, not bolted onto the old way.
Change how the work happens and you change what people do all day. That spooks a team, and quiet resistance is what kills most AI mandates. So I don't route around it. We design the new model with the people who'll run it, so it's theirs, not imposed. AI takes the production work; people move up to judgment, not out. And your own people, trained through the pilot, own it when I leave.
Decisive and focused. We audit how the team really works, redesign it together, and put it into a real pilot.
A focused read of where momentum slowed and why. We surface how your products, people, and workflows actually run, and where AI changes the operating model, not just the tooling.
The team comes in. I don't pretend to know your products or how you work. We surface what your operating model needs to become, then design the redesign together.
We put it into a real pilot and build the discipline around what to keep, what to kill, and what good looks like. Along the way I train two or three of your own people to own the new operating model, so it keeps running after I leave. Human Systems Architects. Not new hires, people you already have.
Depending on your situation, engagements typically result in: