
Executive Assessment: Why the Executive Is 1/2 of the Search
November 16, 2026
Executive Pedigree Isn't Proof of Portable Capability
The Coaching Tree Fallacy: When Pedigree Gets Mistaken for Portable Capability
Every NFL hiring cycle, at least a few teams make a familiar bet. They hire a prominent assistant from one of the league's most successful organizations and hope that part of the system travels with them.
The logic sounds unassailable. The coordinator sat in the room next to the head coach. They designed the third-down packages or called the plays in the red zone. They worked twelve hours a day inside an operation that won. The owner and general manager assume that by hiring the assistant, they are importing some portion of the architecture that produced the winning.
Then the games begin.
The record is useful here. By ESPN's accounting through 2018, head coaches with Bill Belichick coaching-tree connections had compiled a combined .407 record; a later compilation put the group around .413 through 2020. Several highly regarded former Patriots assistants — Josh McDaniels, Matt Patricia, Joe Judge, Romeo Crennel, Eric Mangini — struggled significantly in their head-coaching chances elsewhere.
That is a striking pattern. It is also easy to misread. The temptation is to conclude that coaching trees from dominant organizations produce predictable failure. The current data complicates that story. The Shanahan and McVay networks have produced both failures and clearly successful head coaches — Matt LaFleur in Green Bay, Kevin O'Connell in Minnesota, DeMeco Ryans in Houston, Zac Taylor in Cincinnati. Not every branch of an elite coaching tree underperforms.
That counterexample isn't inconvenient. It is actually what makes the question worth asking.
Because the useful question isn't why do coaching tree hires fail. It is sharper and more interesting than that.
When someone succeeds inside an exceptional system, how much of the performance belongs to the person — and how much belongs to the system around them?
That is executive-search territory.
Executive Pedigree: The component fallacy
The pattern worth naming here is an attribution problem.
When an organization dominates its industry over an extended period, outside observers tend to distribute credit evenly across the leadership roster. If a company produces extraordinary results, the market assumes the Chief Commercial Officer, the VP of Supply Chain, and the Head of Product must each be world-class architects of that performance. If a football team wins consistently, the market assumes the coordinator who was there must be ready to run his own team.
Call this the component fallacy. It isn't the belief that dominant systems make mediocre people look great; most of them actually do contain exceptional people. It is subtler than that. The component fallacy is the belief that because someone performed exceptionally inside an exceptional system, they personally possess the capabilities required to recreate that system somewhere else.
That is a different claim, and it is the one hiring committees most often get wrong.
What the parent system actually provides
To see why the attribution matters, it helps to think about what a coordinator in a mature successful organization is operating inside.
They inherit established language and routines. They inherit a head coach whose credibility with ownership and the roster is already settled. They inherit a quarterback or defensive core that other teams don't have. They inherit a personnel philosophy with specific physical profiles already defined, and a scouting operation that has been feeding the roster for years. They inherit institutional football-research capability — in New England's case, Ernie Adams and the broader Football Research function that Belichick had built around him — that other organizations don't have equivalents for. They inherit a locker-room culture that has absorbed what the standards look like.
Inside that environment, the coordinator's job is bounded. They are optimizing a subsystem — the offense, the defense, a situational package — while a very large apparatus absorbs organizational shocks on their behalf.
When that same coordinator becomes a head coach elsewhere, they inherit nothing. They inherit a different system. Different ownership, different GM, different roster, different history, different media environment, different culture. What changes is scope. The surrounding architecture that used to be someone else's job is now partly theirs.
This is a role-expansion problem more than a talent problem. The capabilities that make a great coordinator — scheme design, in-game adjustment, player development inside a position group — are not the capabilities that make a great head coach. The head coach is responsible for the staff, the media, the ownership relationship, the culture, the roster, the integration between sides of the ball, the response to losing. A coordinator may be excellent at coordinating and still untested on most of that.
The same mechanism explains the LaFleur and O'Connell counterexamples. Neither of them succeeded because they imported "the McVay system." They probably succeeded because of a wider set of capabilities built before and alongside the McVay years — staff-building, quarterback development, leadership, the ability to adapt principles to a different roster. That is what traveled. The system didn't.
The corporate version
The same mechanism operates in boardrooms, and it may be more expensive there because the salaries are larger and the diagnosis is harder.
For decades, boards reflexively recruited executives who had grown up inside General Electric under Jack Welch. More recently, the same reflex has attached itself to Amazon, Google, Apple, and a handful of other admired companies. The reasoning is familiar: if this executive spent seven years scaling a $5 billion business unit at a scaled technology company, imagine what they can do with our $300 million industrial manufacturer.
Sometimes that works. Sometimes it works brilliantly. But the base rate of translation is less reliable than the pedigree suggests, and the reason is identical to the coaching tree.
At a scaled technology company, a senior executive may be operating with mature data infrastructure, deep specialist teams, strong recruiting pull, established operating mechanisms, substantial brand credibility with enterprise buyers, and a decision-making architecture that has been refined over many years. None of those conditions automatically travels with the executive. When they arrive at the mid-sized company, the ERP data isn't clean, there isn't a line of specialist candidates waiting to be hired, the brand doesn't open the first meeting for them, and the operating cadence they are used to has to be built from scratch rather than inherited.
The executive, accustomed to steering a well-equipped vessel, discovers they have been hired to build the engine. Many of them know how to drive the finished product and have never had to build the engine. That is not an indictment. It is a role-scope mismatch.
Principle versus ritual
There is a related failure mode that is almost always the proximate cause when a hire from an admired company doesn't work.
Executives leaving iconic organizations tend to carry two kinds of knowledge: the principles their former company operated on, and the specific rituals those principles were expressed through. Strong transplantation imports the principle and designs a new ritual appropriate to the new environment. Weak transplantation imports the ritual and expects it to produce the same outcome.
A six-page narrative memo at Amazon exists for a reason — it enforces written clarity, surfaces disagreement, and prevents the room-dominance effects of unstructured presentations. The principle is rigorous written thinking. The ritual is a six-page memo in a specific format. An executive who leaves Amazon and starts requiring six-page memos at a 300-person manufacturer may be solving a problem that company doesn't have, in a form that company can't absorb, while missing the thing that made the ritual work in its original environment.
The same thing happens in football. When a former Patriots assistant tried to treat veteran players in a different locker room with the cold detachment that was tolerated inside the Patriots' specific culture, the response was often different. The principle (standards don't move) might have been exportable. The ritual (how those standards were enforced) was not.
The gap between principle and ritual is where many pedigree hires fail quietly. The organization doesn't look like the parent, so the imported form is wrong, so the executive concludes the new organization is broken rather than concluding that the form needed redesigning.
Three questions worth asking
When a hiring committee or board is evaluating a candidate from a dominant parent organization, there are three questions that reveal more than resume review will.
What did your former organization do for you that you will have to do yourself here?
Candidates who understand what they inherited can answer this specifically. At my previous firm, I had a fifteen-person business intelligence team that cleaned data before it reached my desk; here, I know our reporting is going to be messy, and my first ninety days will be in the operational weeds learning the unit economics. Candidates who insist their former company was secretly disorganized and that they built everything themselves are telling you something else — that they haven't yet seen the architecture that was supporting them, which is a problem.
Which practices from your current organization would not work here, and why?
This is the principle-versus-ritual test. Candidates who can distinguish the mechanism from the mechanism's shape — who can explain what a given practice was actually solving for, and why that solution would need to be redesigned in a different context — are showing you they understand their own operating environment well enough to translate it. Candidates who treat every practice at their current company as universally applicable are showing you the opposite.
Which of the accomplishments you're most proud of depended materially on capabilities or people you will not have here?
This is the attribution question. An exceptional candidate can describe the organizational leverage that made their best work possible — the CEO who shielded them, the balance sheet that funded the bet, the brand that opened the enterprise customer, the specialist team that did the technical build. A candidate who claims total personal authorship over a major division turnaround at a Fortune 50 company is not necessarily lying — but they are not giving you data you can use either. The useful answer isn't nothing depended on anyone else. The useful answer is a specific, credible map of what they built and what they inherited.
Authorship versus inheritance
The language that may be most useful here, in a hiring conversation, is authorship versus inheritance.
Few successful senior executives are pure architects, and few are pure beneficiaries. Most are contributors inside systems they partly shaped and partly inherited. The search question isn't a verdict on the person. It is: how much of the success did they author, and how much did they inherit, and which of those capabilities are portable to the environment we are about to put them in?
A useful discipline for a board is environmental subtraction. Mentally remove the parent company's brand, balance sheet, data infrastructure, specialist teams, CEO, operating cadence, and customer access from the candidate's record. Then ask what capability is clearly left. The exercise isn't fair in a strict sense — none of us operate without an environment — but it does separate the executives whose work is legible from the ones whose work is not.
This isn't an argument against hiring from strong companies. Operating excellence inside a mature system is a genuinely valuable thing, and some organizations are hiring exactly for that. A company that already has strong infrastructure and needs someone to run it well is in a very different position from a company that needs the infrastructure built. The mismatch happens when the hiring organization needs building and selects based on operating pedigree.
The question underneath all of this is which capability the organization is actually trying to buy.
Executive Pedigree is evidence of exposure, not proof of authorship
The piece of this that is worth keeping in mind the next time a client says find us a Chief Commercial Officer who spent five years at the market leader: pedigree is evidence of exposure. It tells you what standards the executive encountered, what complexity they experienced, what quality of colleagues they worked alongside, what scale they operated inside. All of that matters.
What it is not is proof of authorship. Being present during the building of a great system is not the same as being able to build one. The coaching tree debate is finally the same debate as the Amazon-alumni debate and the GE-alumni debate before it. The parent company name is a signal. It is not a conclusion.
The next time a board wants the executive from the company everyone admires, the question to answer isn't only what that company taught them. It is what disappeared when you removed the company from the equation — and whether what's left is what the new organization actually needs.
Charlie Solorzano is Managing Partner at Alder Koten and leads the firm's Sports Executive Search practice. He also leads the Sports Practice at IMD International Search Group, a globally coordinated executive search network operating across 26 countries. His work focuses on senior executives, commercial and operational leadership, governance and board-level appointments across the sports ecosystem.
What's Left When You Remove the Parent Company From the Resume?
Pedigree tells you what a candidate was exposed to, not what they built. Let's talk about separating authorship from inheritance before your next senior hire.
Schedule a Confidential ConsultationWhat is the "component fallacy" in executive hiring?
It's the belief that because someone performed exceptionally inside an exceptional system, they personally possess the capabilities to recreate that system somewhere else. The claim isn't that dominant organizations lack strong people. It's that credit for the system's results gets distributed evenly across its roster, which hides what each person actually authored.
Do all hires from elite organizations underperform?
No. Some branches of elite coaching trees have produced clearly successful head coaches, which is what makes the question worth asking. The point is that pedigree is a signal, not a conclusion. The coaches who succeeded likely did so because of broader capabilities built alongside the system, such as staff-building and leadership, not because they imported the system itself.
What's the difference between importing a principle and importing a ritual?
A principle is the problem a practice was solving; a ritual is the specific form it took in the original organization. Strong transplantation imports the principle and designs a new ritual for the new environment. Weak transplantation imports the ritual and expects it to produce the same outcome.
What questions help separate what a candidate built from what they inherited?
Ask what their former organization did for them that they'll have to do themselves, which practices from it would not work in the new environment and why, and which accomplishments they're proudest of depended on capabilities or people they won't have. Specific, credible answers show the candidate can see the architecture that supported them.
Is hiring from a dominant company ever the right call?
Yes. A company that already has strong infrastructure and needs someone to run it well is buying a different capability than one that needs the infrastructure built. The mismatch happens when the hiring organization needs building but selects based on operating pedigree.




