The Domain Expertise Trap
The most common filter in CPO hiring optimises for comfort, not competence. And the people who apply it know this, somewhere.
There’s a question I’ve been asked so many times now that I can feel it coming before the recruiter finishes their opening pleasantries. It arrives about ninety seconds in, right after the bit about the role being “really exciting” and the CEO being “very product-minded.” The question is: “Have you worked in [our industry] before?” And depending on my answer, the conversation either opens up or quietly begins to close. Not dramatically, nobody says “well, that’s a problem,” but the sentences get shorter and the energy shifts, and you can feel the mental filing happening in real time, the little internal note that says interesting but risky.
I understand why CEOs ask for domain experience. I genuinely do. If you’re hiring a Chief Product Officer, someone who’s going to own your product strategy, shape your roadmap, influence your engineering investment, and sit in rooms with your biggest customers, you want to feel confident they won’t spend their first six months learning what your customers actually care about. You want someone who already speaks the language. Who knows the regulatory landscape, the competitive dynamics, the unspoken rules of how your market works. That’s not unreasonable, it’s a de-risking instinct, and if you’ve ever made a senior hire that didn’t work out (and if you’re a CEO, you have), you know how painful and expensive that is. The domain experience filter feels like insurance, like the grown-up, responsible thing to ask for on the job spec.
The thing is, I’m not sure the filter actually does what people think it does. What it de-risks isn’t the hire itself, it’s the feeling of hiring, the anxiety of handing someone the keys and hoping they don’t crash it. And those two things, the actual risk and the felt risk, are much further apart than most CEOs realise.
I should back up though because I have a specific experience that sharpened this for me. A few years ago I took a product leadership role at Körber, a supply chain technology company. I had no supply chain experience. None. I couldn’t have told you the difference between a WMS and a TMS with any confidence before I walked through the door. And I remember the early weeks being genuinely uncomfortable, not because the work was beyond me, but because I was surrounded by people who had spent decades in logistics and warehousing and I was asking questions that probably felt, to them, like I should already know the answers. “Why do we do it this way?” is a very different question when it comes from someone with twenty years in the industry versus someone with none. From the veteran, it’s a strategic challenge. From the newcomer, it sounds naive.
But here’s the thing I noticed. Those naive questions, the ones I asked because I literally didn’t know any better, turned out to be the most productive questions anyone had asked in a while. Not because I was smarter than the people around me, I definitely wasn’t, but because they’d long ago stopped asking why things were done a certain way. They’d internalised the logic of the domain so completely that its assumptions had become invisible. The way the product was structured, the way customers were segmented, the way roadmap decisions got made, all of it rested on foundations that nobody examined anymore because they felt like facts rather than choices. I didn’t have that problem. Everything looked like a choice to me, because I had no framework telling me it was inevitable.
Cognitive science has a name for this, the curse of knowledge, and it’s more than an academic curiosity when you’re leading product. Once you know something deeply, you lose the ability to reconstruct what it was like not to know it. Mind the Product published research showing how this sabotages product people in three specific ways: it distorts how you communicate with users, it warps your assumptions about what’s intuitive, and it makes you blind to opportunities that sit outside your existing mental model. So the deeper your domain expertise, the more likely you are to build withinthe current frame rather than noticing that the frame itself might be the constraint.
Which brings me to what I actually mean when I say the domain expertise filter is a trap. Domain knowledge isn’t bad, it’s useful, and the right CPO will acquire enough of it within months to be dangerous. The trap is that when you make it the primary filter, you’re optimising for someone who will operate fluently within your existing paradigm. And that is almost never why you’re hiring a CPO. If you needed someone to maintain the current product direction with minor improvements, you’d promote internally. You’re hiring a CPO because something needs to change, because the strategy needs rethinking or the product org needs restructuring or the roadmap needs a harder edge. You’re hiring for transformation and then filtering for continuity. That’s the contradiction, and most of the CEOs I’ve spoken to, when I put it to them that directly, will pause and acknowledge it. They know, they just haven’t connected the two thoughts yet.
The evidence for outsider advantage at the senior leadership level is actually substantial, though it tends to get discussed more in CEO appointments than CPO ones. Alan Mulally came from Boeing to Ford with zero automotive experience and engineered one of the most celebrated turnarounds in corporate history. Lou Gerstner went from RJR Nabisco, a food and tobacco company, to IBM and fundamentally redirected the company from hardware to services, a strategic shift that no IBM insider would have made because hardware was IBM’s identity. Angela Ahrendts came into Burberry from outside luxury fashion and tripled the stock price by doing things the industry hadn’t thought to do. In each case, the outsider saw the dysfunction that the insiders had normalised, and they saw it because they hadn’t been marinating in the same assumptions for a decade, not in spite of it.
Egon Zehnder, who arguably know more about executive hiring than anyone, recently published their current framework for what makes a great CPO, and it lists five traits: systems thinking, AI fluency, culture gravity, narrative power, and operator instincts. Domain experience doesn’t appear. Not because they think it’s worthless, but because it’s the kind of thing you can acquire in months, whereas the traits that actually predict CPO success are built over years across multiple contexts, across different industries, different product types, different organisational shapes. Their own analysis of where CPO hires go wrong backs this up: overweighting brand prestige and domain familiarity, while underweighting adaptability and strategic range, is one of the most common and most costly mistakes companies make.
And yet the data from UK hiring managers tells a different story to the one they’d give you in conversation. 40% of product management candidates are rejected at screening stage for lacking domain experience, even though those same hiring managers say they want generalists. The stated preference and the actual filter are in direct conflict, and I think the reason is that senior hiring decisions aren’t purely rational assessments of capability. They’re anxiety management exercises. The CEO is about to hand someone significant authority over the company’s product direction, and that’s a terrifying thing to do, and domain experience is the thing that makes it feel less terrifying even when it doesn’t actually make the outcome less risky.
I want to be careful here because I’m not arguing that domain expertise is a negative signal. A CPO who brings both strategic capability and domain knowledge is, all else being equal, better positioned than one who brings strategic capability alone. But “all else being equal” almost never applies in practice. What actually happens is that the domain filter eliminates candidates whose strategic capability, organisational instincts, and leadership range far exceed those of the domain-matched candidates who make it through. You end up comparing the best available domain expert against a much stronger field you never saw, and you don’t know what you lost because they were filtered out before anyone could find out.
The irony, is that the CEOs who are most vocal about needing a CPO who can “challenge our thinking” and “bring fresh perspective” are often the same ones who insist on ten years in their vertical. They want transformation delivered by someone who already thinks the way their organisation thinks, the outsider’s insight without the outsider. And that’s not a hiring strategy so much as it’s a wish.
I don’t think this changes overnight. The de-risking instinct is deep and it’s reinforced by every recruiter who builds a longlist filtered by industry tags. But I do think it’s worth naming what the filter actually costs. It costs you the person who walks in and asks why your product is structured around your org chart rather than your customer’s workflow. It costs you the person who spots a pattern from a completely different industry that solves your thorniest problem, or the person who hasn’t yet learned what’s “impossible” in your domain and so goes ahead and tries it anyway. Those are expensive things to lose, especially when you didn’t even know they were on the table.
Reference links: