The first 90 days problem
The first 90 days reveal what the hiring process didn't ask about.
40% of senior hires fail within 18 months, costing 1.5–2x annual salary to replace. Most failures trace back to mismatched expectations about autonomy, culture, and the real scope of the role — things that a credential-focused interview never surfaces. The competency questions that feel uncomfortable to ask before the hire are exactly the ones that predict whether someone will make it through the first year.
The failure rate nobody talks about
Leadership IQ research found that 46% of newly hired employees fail within 18 months. The Corporate Executive Board's own data on senior leaders puts the number at 40%. These aren't failures from bad character or dishonesty — the vast majority of first-year failures stem from candidates who were technically qualified for the role but mismatched in ways the hiring process never examined.
The cost is significant. A failed hire at the senior level costs between one and two times annual salary once you account for recruitment, onboarding, the productivity ramp that never materialized, and the time the team spent managing a situation that wasn't working. The cost at junior levels is lower in absolute terms but often higher in organizational terms — a bad hire in a foundational role can shape a team's culture for longer than the person stays.
What the first 90 days actually test
The first 90 days test things that most interviews never evaluate. They test how someone handles ambiguity — whether they can operate without clear instructions when the context shifts, as it always does. They test how someone handles conflict — whether their approach to disagreement is productive or corrosive, and whether they're aware of the difference. They test coachability — whether feedback changes behavior or triggers defensiveness. And they test motivation — whether someone who seemed energized by the opportunity retains that energy when the work turns out to be harder and more mundane than it looked from the outside.
None of these questions are exotic. They are the obvious things to want to know about someone who is going to spend at least a year in your organization. And yet they are the questions most hiring processes avoid, either because they feel uncomfortable to ask, or because the interview format doesn't create the space to get a real answer, or because the team was in a hurry and focused on whether the candidate could do the core technical work.
The predictable failures
The most common first-year failure has a pattern. It usually involves a mismatch between the autonomy the candidate expected and the autonomy the role actually offered. They were hired for "ownership" and "strategic impact," they arrive to find they need three approvals to change a vendor contract, and within six months they're gone. This mismatch was not unforeseeable. It was predictable from a ten-minute honest conversation about how decisions get made in the organization — a conversation that almost never happens before the offer letter is signed.
The second most common pattern is a culture mismatch that got optimized away in interviews. The candidate learned to read the room and gave the answers that matched what the interviewers wanted to hear. The interviewers were looking for cultural fit and found it, because they were looking at the performance of it. Six months in, what people are actually like when the performance has stopped is less compatible with the team than the interview suggested.
What the hiring process should have asked
The questions that would have caught these failures aren't trick questions. "What conditions bring out your best work — and what conditions have historically made it hard for you to perform?" is a competency question about self-awareness and environment fit. "Tell me about a time a manager gave you feedback that you initially disagreed with — what happened?" evaluates coachability without being confrontational. "What specifically appealed to you about this role's scope, and what parts of it feel like a stretch?" surfaces expectation mismatches before they become expensive.
These questions are uncomfortable to ask because honest answers make the decision harder. A candidate who says "I work best with significant autonomy and struggle with bureaucratic processes" might be the right person for half the jobs you'd consider them for and wrong for the other half. That distinction is worth making in the interview room, not in month three.
The first 90 days problem is largely a first 90 minutes problem — a failure of the hiring conversation to ask the questions that the working relationship will eventually answer. Asking them early doesn't guarantee a good outcome. Not asking them almost guarantees you'll be surprised.