Every CPO Job Is a Turnaround: The First 90 Days

The short version

I have been CPO four times, at Commure, Crisis Text Line, SOCi, and Smartcat, and every one of those jobs was secretly a turnaround. Nobody hires a Chief Product Officer when product is working. Companies promote from within when things are healthy and go outside for a CPO when growth has stalled or the org has lost trust. So the title is a lie about the job. The real CPO mandate in the first 90 days is diagnose the real problem in 30 days, make one visible change by 60, and install a new operating model by 90, in that order, not a reorg on day one. And in the AI-native era the turnaround is bigger, because you are not just fixing the product org, you are converting it to an outcome-to-prototype model where build cost has collapsed. Here is what the first 90 days actually require.

I have held the CPO title at four companies. From the outside, four CPO roles reads like a steady climb. From the inside, every single one started the same way. Something was broken, the people who hired me half-knew it, and the job description politely declined to say so.

Nobody hires a CPO when things are going well

Think about when a company actually goes outside for a Chief Product Officer.

When product is humming, you promote the strong VP who is already there. You reward the bench you built. The board is happy, the founder is happy, and bringing in an expensive outsider to run product would be a vote of no confidence in a winning team.

You go outside for a CPO when something is wrong and the inside answer is not obvious. Growth flattened. The roadmap lost the plot. The product org and the go-to-market org stopped trusting each other. A founder who used to run product can no longer hold it and does not know who can. By the time the search firm calls, the patient is already sick. The CPO search is a symptom.

So the title is a lie about the job. It says scale, it says vision, it says next chapter. The actual job is turnaround, and the sooner you accept that, the better your first 90 days go.

“

Nobody hires a CPO when product is working. You go outside for one when something is already broken. Every CPO role is a turnaround wearing a growth job description.

”

The first 30 days: diagnose the real problem

The biggest mistake I have watched new CPOs make, and made myself once, is to act on day one. You arrive, you feel the pressure to look decisive, and you reorganize around the problem you were told about in the interview.

That problem is almost never the real one. The stated problem is what leadership can see from where they sit. The real problem lives in the gap between what the executive team believes is wrong and what the people closest to the customer believe is wrong. Your first 30 days exist to find that gap.

So do not touch the org chart yet. Talk to customers before you talk to the board deck. Sit in on how product decisions actually get made, not how the process doc says they should. At one of my CPO roles, leadership was certain the problem was velocity, the team shipped too slowly. Thirty days of listening told me the real problem was that the team shipped fast and built the wrong things, because nobody owned the customer outcome. A velocity reorg would have made it worse, faster. That is the kind of mistake the first 30 days are designed to prevent, and it is the same outcome-first reflex I lean on across a clean 30-60-90 for product leaders.

The first 60 days: one visible change

By day 60, you need one credible, visible win. Not a transformation. One thing that proves the org can move and that your read of the problem is right.

This is psychological as much as operational. A product org that hired a turnaround CPO has usually been stuck long enough to stop believing it can get unstuck. The team is tired. They have seen leaders come in, announce big plans, and leave the plans unfinished. Your first visible change is how you buy the trust you will need for the hard part.

Pick something that maps directly to the real problem you diagnosed, not a flashy unrelated launch. If the real problem was that nobody owned outcomes, ship one team that owns one outcome end to end and show what changes. Small, real, and pointed at the actual disease. Done by day 60, while you still have the org's attention.

The first 90 days: install the operating model

The change has to outlast your attention, or it was theater. That is what day 90 is for. You install the operating model that makes the fix permanent after you stop personally pushing it.

This is the difference between a CPO who creates a spike and one who creates a slope. The spike comes from your energy. The slope comes from a system that produces the right behavior without you in the room. How outcomes get set. How decisions get made. How the product org and go-to-market stay honest with each other. This is the product operating model work, and it is the part most turnaround CPOs skip because it is slow and invisible and nobody claps for it.

Skip it and the org snaps back to its old shape the month you get distracted by something else. Install it and the turnaround compounds without you.

The AI-native CPO mandate is a bigger turnaround

Here is what changed, and why the next generation of CPO turnarounds are harder.

For most of my career, a product turnaround meant fixing how the existing machine ran. Better outcomes, better ownership, better operating model, same fundamental shape of work. Build was expensive, so you were optimizing a team built to ration scarce build capacity.

That constraint is gone. An AI-native CPO is not just fixing a product org, they are converting it to a different kind of org. One where build cost collapsed, where a customer outcome can become a working prototype the same day, where the scarce resource is judgment and taste, not engineering throughput. The turnaround now includes rewiring how the team works, not just what it ships.

“

The old turnaround fixed how the machine ran. The AI-native turnaround changes what the machine is, because build cost collapsed and judgment became the only scarce thing left.

”

A team that is still optimized for scarce build capacity is solving last decade's problem with admirable discipline. The CPO who walks in today has to diagnose that, install agentic workflows and same-day prototyping, and move the whole org's judgment to outcome-first, all inside the same 90-day window, all while the patient is already sick. The job got harder and the clock did not.

Pick one thing to try this week

If you are stepping into a product leadership role, write down the problem you were told about in the interview. Then spend one week, before you change anything, talking only to customers and watching how decisions actually get made. At the end of the week, write down the real problem in one sentence. The distance between those two sentences is your turnaround. Diagnose before you reorganize, every time. The day-one reorg feels brave and is almost always the move you most regret.

Sources: Silicon Valley Product Group, on product leadership · Harvard Business Review, on the new CEO and executive transitions · First Round Review, on the first 90 days in a leadership role