Studies of executive hiring put the failure rate between 56% and 81%.
Imagine batting .200 at anything else important in your business and accepting it as normal.
CEOs hear those numbers and assume the problem is candidate selection. Either they hired the wrong person, the recruiter sent the wrong slate, or the candidate misrepresented themselves. So the next time they hire, they tighten the interview process, do more references, run more meetings.
But the numbers don't improve.
The reason they don't improve is that the failure usually didn't happen during the interviews. It happened before the search even started.
The 93% problem
The most-cited cause of executive hiring failure is inadequate job definition. The research puts this at around 93% of failed hires.
Almost every executive hire that fails was built on a job that wasn't well defined to begin with.
I've seen this pattern many times. A CEO calls me to launch a search for a VP of X. We schedule the kickoff meetings. I ask the CEO what the new VP needs to accomplish in 6 months, 12 months, 24 months. I ask what types of experience matter most. I ask how success will be measured.
The answers are often vague. Sometimes I get the classic: "I'll know it when I see it."
I'm pretty sure they won't.
The standard job spec is the problem
Open a typical executive job spec and you'll see a list of qualifications and responsibilities:
- Drive revenue growth.
- Hire, train, and manage a world-class sales organization.
- Communicate effectively with other functional leaders.
Now ask yourself: what does success look like? You can't tell from that list. Nobody can. The CEO can't, the candidates can't, the board can't.
When the job isn't defined, three things happen.
Sourcing gets wide instead of deep. Without a clear target, the recruiter casts a broader net and brings more candidates. The slate looks impressive but isn't.
Interviews drift. Without clear deliverables, interviewers each evaluate against their own internal picture of the role. You get six interviewers and six different jobs.
Reference checks lose their edge. Without specific outcomes, references default to "good guy, hard worker, would work with him again."
The hire happens. The work begins. Twelve months later, the CEO is frustrated because the new VP isn't delivering what the CEO had in mind; the VP is frustrated because the CEO keeps changing what success means.
The 93% statistic isn't really about poor execution. It's about people avoiding a hard conversation.
Why job specs stay vague
CEOs know the standard spec is weak. They've read the books. They've heard the advice. They know "drive revenue growth" isn't a definition.
So why does it keep happening?
Because the honest version is uncomfortable.
A vague spec preserves optionality. It says, "we want someone great for whatever we might need." A specific, deliverable-based spec forces tradeoffs. It says, "this hire is going to focus on these three things over the next 18 months, which probably means they're not the right person to do these other things later."
That's a harder conversation. It requires the CEO to commit to a direction. It requires the board to agree on priorities. It requires admitting that no single executive is going to fix everything that's broken.
So the spec stays vague. The search proceeds. The candidates are evaluated against six different mental pictures of the job, none of which were ever written down. And the executive who's hired walks into a role that was never defined the same way twice.
Define the job in deliverables
The fix is to define the job in quantifiable, time-based deliverables. Three to six of them. Examples:
- Drive revenue from $15M to $25M in Europe over the next 12 months by developing partner relationships with three regional systems integrators.
- Within 18 months, transition the geographically-organized North American sales team to a vertically-oriented model focused on financial services and manufacturing.
- Within 6 months, build an inside sales team of 10–12 reps focused on the SMB SaaS offering.
Compare those to "drive revenue growth." The first set tells a candidate what the job actually is. The second set tells them nothing.
Get a 360 perspective and put it in writing
Don't build the job definition alone. Get input from the people who will work with this executive: peers, board members, advisors, direct reports. Where they disagree, resolve it before launching the search.
And put the final definition in writing. Sign off on it. The number of executive searches that go sideways because the CEO and the lead board member have different mental pictures of the job is far higher than either of them would guess.
If you can't write down what success looks like in three to six measurable outcomes, you're not ready to launch the search.
Not because the work is too hard. Because the prioritization conversation hasn't happened yet.
If you launch anyway, you're betting against the data.