The CPO role was designed for a person who doesn’t exist
What the role actually demands and why nobody admits the full list.
I sat in my first board meeting as CPO. The CFO had built a slide deck I can only describe as a financial novel. EBITDA. Adjusted EBITDA. Gross margin evolution by quarter. He was clearly in his natural habitat. I was nodding. Professionally. Strategically. And almost completely lost.
I was not stupid. I had built products people loved. I had led teams through hard things. I understood revenue and costs in the abstract. But sitting in that room, listening to a language I had never been properly taught, I understood something uncomfortable for the first time: the CPO role expects you to be fluent in conversations that most product careers never prepare you for.
I learned the language eventually. I can hold a proper P&L conversation now, ask the right questions when the CFO walks through the numbers, understand what is actually being signalled when someone says the EBITDA margin is compressing. I built that. But I will not pretend it ever became the thing that excites me most about the role. It still does not light me up the way a product conversation does. It probably never will.
So let’s have some real talk today.
Read any CPO job description carefully and you will find something interesting. The role asks for a genuine visionary who can also present a gross margin bridge to the board, run a design critique with conviction, build scalable processes, inspire an all-hands, earn the trust of engineering, develop the next layer of product leaders, and tell a story compelling enough to move investors who have seen everything.
That is not a job description. It is a list of nine different people.
And yet companies hire for it as if the person exists. CPOs take the role as if they are that person. And the gap between the fiction and the reality does a lot of damage quietly, before anyone names it.
There is a piece of research that days: boards looking to hire a CPO consistently look for three non-negotiable signals: P&L fluency, board-grade storytelling, and what gets called “talent magnetism.” Just those three already ask for a rare combination. Financial sharpness, narrative ability, and the kind of presence that makes people want to follow you. Most careers build one of those. Two is unusual. All three at the same time is genuinely rare.
And that is before you add the full list of what the role actually demands day to day.
Genuine vision. The ability to see where a market is going before the evidence is obvious, to articulate a product direction that does not exist yet, and to get smart people to believe in it before there is proof. A polished roadmap is the output of that. It is not the thing itself.
Financial fluency. Understanding gross margins, P&L ownership, CAC payback, cohort decay, and being able to hold that conversation with the CFO and the board without losing the thread or quietly deferring to someone else. This one matters more than most product careers prepare people for. Research from a CPO coaching community puts it plainly: financial acumen is typically not required for product managers or mid-level leaders, but it becomes fundamental at the CPO level because the people you interact with most are no longer in the product team. They are the CEO, CFO, COO, and board. They think in financial terms. You need to as well.
Analytical sharpness. The ability to sit inside a messy dataset, find what actually matters, and build a narrative that moves a decision. Anyone can put charts on a slide.
Design sensibility. Enough taste to guide a design team, to push back when something feels wrong, to hold a standard for what good looks like without standing over every pixel. Creative teams know immediately when this is genuine and when it is performed.
Operational discipline. The ability to build structures that scale, create processes that survive the CPO’s absence, and resist the natural pull toward chaos when a company is growing fast. Some people are wired for this. Others have to work for it deliberately.
Confident public presence. On stage at an all-hands, in front of investors, in a press conversation, with enterprise customers. The role requires the ability to calm a room and energise a room, sometimes in the same hour.
Cross-functional trust. The kind where engineering, sales, marketing, and customer success want to bring you in early, before the decision is made, rather than briefing you when it is already too late to change anything.
People development. Building a product organisation where leaders make good decisions without the CPO in the room. Mentoring strong performers is the easy part. The harder part is building the layer below them.
And board-level storytelling. Anyone can deliver an update. The CPO needs to reframe the company’s situation in a way that creates conviction in people who are professionally sceptical and have watched a lot of companies make expensive mistakes.
Now think about how many people you know who are genuinely excellent at all nine.
The expectation shifts depending on where the company is in its life.
At an early stage, the CPO is essentially a very senior player-coach. Close to the product, helping find market fit, working directly with a small team. Vision and customer intuition matter most here. The financial conversations are simpler. The processes are minimal by design.
In a growth stage company, everything changes. The CPO now has to scale teams, align multiple functions toward a coherent strategy, start thinking about unit economics, manage churn alongside roadmap, and translate product direction into language the board will fund. The role gets wider fast.
In an enterprise, the CPO is running what is effectively a portfolio business. Multiple product lines. Governance structures. M&A decisions. Innovation pipelines alongside mature products. The financial and operational dimensions of the role become as important as the product ones.
The person who is excellent at the early stage version of this job is often not the person who thrives at the enterprise version. And yet companies talk about the role as if the title describes a fixed thing.
Here is where the fiction becomes expensive.
When a CEO hires a CPO, the mental model is often the complete package. Visionary, commercially sharp, design-literate, operationally excellent, a confident communicator, trusted across every function. When the search does not produce that person, because it never produces that person, the hire goes to whoever performs that completeness most convincingly in the interview process.
And then the role starts.
The gaps do not stay invisible. Organisations are very good at revealing what a leader cannot do, usually under pressure, usually at the worst possible moment. A CFO who loses patience in a board discussion because the CPO cannot hold the financial conversation. An engineering team that quietly stops trusting the product direction. An all-hands where the energy in the room goes flat because the person on stage has not figured out how to carry a room yet.
There is a gender layer here that rarely gets named in these conversations. Women make up around 35% of senior product leadership roles despite near-parity in overall product teams. Part of what creates that gap is the informal dimension of the CPO role that nobody puts in the job description: the trust-building that happens in spaces that were not designed with everyone in mind. The after-dinner conversations. The unspoken assumptions about who reads as credible by default and who has to keep proving it. These are real costs. They sit alongside the nine formal dimensions, not instead of them.
When a CPO cannot name their gaps to the person who hired them, those gaps become something else. They become whisper campaigns. Reputation problems. The slow erosion of confidence that eventually ends with the CPO either leaving or being managed out, and everyone describing it as a culture fit problem rather than a gap that was never talked about honestly.
The CPOs who develop the furthest are not the ones with the fewest gaps. The research on this is consistent, and what I see in practice matches it. The ones who grow are the ones who named their gaps earliest, worked through them explicitly, and built the kind of relationship with their CEO that made that honesty possible.
That conversation, where a CPO names their weaknesses directly to the person who hired them, is one of the most clarifying things that can happen in the role. It is also one of the rarest. Because the default on both sides is to perform completeness. The CEO wants to believe they hired the full package. The CPO wants to be the full package. So the gaps stay unnamed until the organisation names them instead.
What actually works is the opposite of that. A CEO who understands the real width of the role, who knows that no one person covers all nine dimensions, can build the team and the conditions around the CPO to complement what is missing. A CPO who can say “I am not strong here yet and I want to work on it” creates the conditions for honest development rather than managed decline.
That kind of transparency is also, as it turns out, exactly what prepares someone for the CEO role. The habit of accurate self-diagnosis under pressure. The ability to name what you do not know to the people who need to know it. The trust that builds when people realise you will not hide the hard things.
The CPO role is often described as a stepping stone to the CEO. That is true, but not because the CPO eventually learns all nine dimensions. It is because done honestly, the CPO role teaches you something more valuable than any single dimension: how to lead while being visibly incomplete, and how to build a system around you that covers what you cannot.
The CPO role was not designed for a perfect person. It was designed for a complex human being who is expected to perform like one.
The most dangerous thing you can do in that role is to believe the fiction. The most useful thing, for CPOs and for the CEOs who hire them, is to name clearly where the fiction ends.
That conversation is not a weakness. It is the actual work.
This is the work I do with CPOs and VPs of Product. If you want a thinking partner who tells you the truth, learn more at stephanieleue.com.
The CPO role fails for a structural reason most organizations never name. It isn't that the candidates aren't good enough. It's that the role was invented to hold together decisions that span product, commercial, and technical ..decisions that were never cleanly owned anywhere in the organization. The CPO becomes the workaround for missing coordination infrastructure. No individual survives that for long. You can't hire your way out of an architecture problem.
This line nails it for me Stephanie:
"the CPO role teaches you something more valuable than any single dimension: how to lead while being visibly incomplete, and how to build a system around you that covers what you cannot."
What is unsaid here is that the CEO is typically not complete, but is provided an infrastructure that covers where they're not strong.