A widely cited piece of product management orthodoxy holds the following position. When hiring a product leader, prefer skills over domain knowledge. The right person will pick up the domain quickly. Too much domain knowledge is a liability, because the hire mistakes themselves for the customer.
I have watched senior teams act on this advice for the better part of a decade. The results are remarkably consistent. The product leader arrives with a strong methodological vocabulary, runs a recognisable playbook, and produces output the board recognises as professional. Six to twelve months in, the people closest to the work start to disengage. Decisions get made on the strength of slide-ware rather than understanding. The product drifts. By the time the data shows it, the hire has moved on, the framework is blamed, and the next theory-first hire is already in the pipeline.
The orthodoxy was answering a different question
The argument against domain depth was not foolish when it was first made. It was a corrective to a real failure mode. Senior business sponsors were appointing internal experts as product owners and watching them treat their own preferences as user research. The remedy was sensible. Bring in someone whose job is to listen to users, not to channel their own twenty years of opinion.
The orthodoxy then drifted. The corrective became a rule. The rule became a hiring filter. By the time it reached most boards, the original nuance had gone, and what remained was a clean, defensible heuristic. Hire for skills. Treat domain knowledge as suspicious. Trust the framework.
This works tolerably well in mature consumer markets where the user base is broad, the domain is shallow, and the framework genuinely is the differentiator. It works badly in regulated, complex, technically demanding environments where the cost of misunderstanding the domain is paid by users who have no alternative.
Healthcare. Social housing. Financial services. Defence. Public infrastructure. The domains where boards most need product judgement are precisely the domains where theory-first hiring fails most expensively.
The cost shows up as governance
A theory-first product hire produces a recognisable signature at board level. Roadmaps look reasonable but slip repeatedly. User research outputs are generated but rarely connect to roadmap decisions. The team fills with proxies. The hire becomes a scribe between the business sponsor and the development team, because they lack the standing to make calls of their own. Decisions cluster around whoever currently has the most political capital, not whoever has the strongest case.
None of these symptoms read as a hiring failure. They read as delivery problems, communication problems, or stakeholder problems. The board reorganises, brings in a delivery coach, runs an offsite. The underlying issue is rarely named, because naming it implicates the hiring decision the board itself made.
The right diagnostic question is uncomfortable. When a senior product leader has to refer every substantive decision back to a subject matter expert, what is the board paying for?
The arithmetic has changed
Until recently the case for theory-first hiring had at least one defensible economic premise. Domain depth was slow and expensive to acquire. Methodological depth was portable. If the new hire absorbed the domain in twelve months, the cost of the ramp-up was a price worth paying for the pattern recognition they brought from elsewhere.
This premise no longer holds. AI tooling has compressed the methodology layer. The artefacts a competent product leader produces, including roadmaps, user stories, competitor maps, prioritisation matrices, communication plans, are now produced in minutes by anyone with a working brief. The portable methodology is no longer scarce. What remains scarce is the judgement to know which artefact is the right one to produce, against which constraint, for which user, in which regulatory environment.
Judgement is the part of the job which does not compress. And judgement is built from domain depth, not from frameworks.
The implication for hiring is direct. The candidate with twenty years in the sector and a willingness to learn modern product practice now outperforms the candidate with twenty years of product practice and a willingness to learn the sector. The arithmetic has inverted. Most boards are still hiring as if it had not.
What boards should look for instead
The hire worth having is the one who knows the domain well enough to challenge the obvious framing, and is comfortable enough with modern tooling to produce the artefacts at speed. They will not cite the canon as much. They will reach for first principles more often. They will have opinions about the user base because they have spent time inside it, and they will hold those opinions lightly enough to update them when research contradicts them.
This is not a return to the internal-expert-as-product-owner failure mode the original orthodoxy rightly warned against. It is the position the orthodoxy itself recommended in its first formulation. Domain depth, channelled through user-centred discipline, with the methodological scaffolding now made cheap by tooling.
The shorthand boards should hold in mind is this. The product leader who has only worked in the domain is too narrow. The product leader who has never worked in the domain is now too shallow. The hire worth making sits in the middle, and is rarer than the market admits.
Where the next NED conversation should go
For boards currently scoping a product or technology leadership hire, the question to put to the search is not whether the candidate has run the relevant framework. The question is whether they have made consequential calls in the relevant domain, and whether they have the methodological literacy to translate those calls into the artefacts the organisation needs.
If the search firm cannot answer the question, the search firm is not the right one for this hire.
The orthodoxy held when methodology was expensive and judgement came free with experience. Both halves of the statement have inverted in the last three years. Boards hiring on the old model are hiring confidently into a market shaped by the new one.