The Pedigree Trap

There is a certain kind of executive resume that can make otherwise smart people briefly lose access to their judgment.

The company names are beautiful. The titles are shiny. The schools, the scale, the board exposure, the “led enterprise-wide transformation across a global matrixed organization” language… it all looks very serious and expensive. The kind of resume that walks into a room before the actual human does.

And listen, I get it. Pedigree matters. Great companies can produce great leaders. Strong training, sophisticated systems, global scale, and real complexity are not nothing. A candidate who has operated in a high-performing environment may have seen what excellent looks like, and that can be incredibly valuable.

But pedigree is not proof.

It is not a leadership assessment. It is not a culture read. It is not a guarantee that this person can actually do the thing you need done, inside your business, at this stage, with this team, under these constraints, while Bob from Finance is quietly resisting the strategy and the CEO wants transformation by Tuesday. That is where companies get into trouble. The mistake is not being impressed; the mistake is letting impressive become enough.

Claudio Fernández-Aráoz wrote in Harvard Business Review about the importance of hiring for potential, not just experience, especially in a world where past success does not always predict future performance. That matters because a candidate can have all the right markers and still be wrong for the environment, mandate, pace, culture, or problem set in front of them. [1]

The pedigree trap feels safe. It gives everyone cover. If the hire works, wonderful. If the hire fails, people can shrug and say, “Well, look at the background. Anyone would have made that call.” But defensible and right are not the same thing.

I have seen companies fall in love with a candidate’s prior employer instead of interrogating the actual human sitting across from them. They hear “Fortune 50” and assume operating discipline. They hear “private equity” and assume urgency. They hear “global” and assume strategic. They hear “transformation” and assume the person transformed something, rather than possibly attending many meetings where transformation was discussed at length over lukewarm coffee.

There is a very big difference between being near impact and being responsible for it. This is a big one for me: differentiating what someone actually owned, led, and did.

There is also a very big difference between succeeding inside a machine and succeeding without one. A leader who thrived in a blue-chip environment may be excellent, but they may also be used to infrastructure your company does not have: clean data, built-out teams, established systems, brand permission, budget, support layers, and someone who mysteriously turns chaos into a board-ready deck by Friday.

Drop that same person into a founder-led, resource-constrained, fast-moving, slightly chaotic but full-of-potential business, and the question changes. Can they still lead when there is no machine? Can they build the machine? Can they make decisions without waiting for perfect information, perfect alignment, and a deck that requires its own zip code?

This is not a knock on big-company executives. Some are phenomenal. Some are exactly what a business needs. But the fit is not automatic, and the brand name should not do the vetting for you.

Adam Grant has made a career out of reminding smart people to rethink what they think they know, which is deeply inconvenient but useful. Executive hiring is exactly the kind of high-stakes decision where certainty can get expensive fast. When a resume makes everyone feel a little too comfortable, that is not the time to relax. That is the time to get nosy. [2]

Because the expensive mistake is rarely the obviously bad candidate. Most companies can spot those. The real danger is the candidate who looks so good on paper that everyone stops asking hard questions.

And that is where the cost starts building. Not just in compensation, although that hurts enough. The bigger cost is the time spent believing the right person is in the seat when they are not. Strategy stalls. Teams start working around the hire. Internal talent gets restless. Board confidence gets quiet first, then loud. Eventually everyone is back in the conference room trying to diagnose what went wrong, which is corporate-speak for, “How did we all agree to this?”

Usually, the answer is not that no one cared. It is that the process confused credentials with evidence. This is where hiring teams need to slow down and get specific. Not bureaucratic. Not over-engineered. Specific.

What did this person actually build, fix, lead, change, protect, simplify, accelerate, or save? What were they personally accountable for versus adjacent to? What conditions made them successful? What resources did they have then that they will not have here? What kind of team did they inherit? What kind of team did they leave behind? Where did they create value, and where did they benefit from an already excellent system?

That last question matters more than people think.

A candidate may have grown up inside a world-class company and learned all the right habits. Wonderful. Or they may have been carried by the brand, surrounded by unusually strong peers, protected by infrastructure, and never really had to operate without the halo. Less wonderful.

The interview process has to be designed to tell the difference.

Laszlo Bock, former SVP of People Operations at Google, has written about the importance of structured, evidence-based hiring. Loose conversations are where pedigree bias thrives. The more casual the process, the easier it is for charm, familiarity, resume sparkle, and “I just liked them” to quietly take over. [3]

And “I liked them” sounds harmless. Sometimes it is. Sometimes it means the candidate was excellent. It can also mean they felt familiar, spoke the same corporate language, came from a company we already respect, or made the room comfortable. Ruchika [Tulshyan] Malhotra has written about the importance of recognizing bias in hiring, including affinity bias, because comfort can masquerade as objectivity if no one is willing to name it. [4]

To be fair, resume sparkle is seductive. We are all human. A great background gives people a sense of comfort. It can make the decision feel cleaner than it really is. But that is also how hiring teams confuse borrowed credibility with demonstrated capability. That is how companies accidentally outsource judgment to someone else’s brand.

The better question is not, “Where did they come from?” The better question is, “What evidence do we have that they can succeed here?”

Here means this company. This stage. This culture. This CEO. This board. This team. This level of ambiguity. This mess. This opportunity. This particular flavor of organizational weirdness, because every company has one. Some just hide it better in the investor deck.

The best executive candidates can talk about their pedigree without hiding behind it. They can explain what they learned at great companies, but they can also tell you what would not translate. They know which parts of their old playbook are useful and which parts would be expensive nonsense in a different environment. They are not just proud of where they have been; they are thoughtful about what they have had to unlearn. That is often where the real signal lives.

Pedigree is a clue. It is not proof. A resume is a map of where someone has been, not a guarantee of where they can take you. The million-dollar mistake is not hiring someone with an impressive background. The million-dollar mistake is assuming the background did the vetting for you.