A ProvenChaos Guide

Why Senior Hires Fail in the First 90 Days

Most senior-hire failures are condition failures, not selection failures: the authority was described rather than transferred, the outcome was never written, and the seams were never named. What the first ninety days should actually produce, and the founder’s half of the job.

A senior hire fails, and the post-mortem almost always lands on the hire. Wrong person. Bad fit. Interviewed better than they worked. Sometimes that is true. More often the person was capable, the selection was reasonable, and the company never actually created the conditions the job required.

That distinction matters commercially. If it was a selection failure, you fix the hiring process. If it was a condition failure, you will hire a second excellent person into the same conditions and get the same result, at the same cost, about a year later.

The Honest Failure Modes

They were hired to fix something nobody agreed was broken. The founder saw the problem. The leadership team did not, or saw a different one. The new leader arrives with a mandate that exists in exactly one person’s head, starts changing things, and meets resistance that reads as personality conflict and is actually an unresolved disagreement they walked into the middle of.

The authority was described, not transferred. They were told the function is theirs. Then the first real decision goes to the founder anyway, because it always has, and nobody announced that it would stop. The team watches where decisions actually land, not where the org chart says they land, and they figure it out in about three weeks.

They were given the outcome without the inputs. Own the number, but the budget still needs approval, the hiring is frozen, and the two people who would have to change how they work do not report to them. This is the most common one, and it is the least visible from the founder’s chair, because from there it looks like ownership.

Onboarding was information, not context. They got the systems, the org chart, and the numbers. They did not get why the last attempt failed, which relationships are load-bearing, what the founder is actually anxious about, or which decisions are one-way doors in this specific company. The first three of those are usually not written down anywhere.

What the First Ninety Days Should Actually Produce

Not a plan. Plans are what a smart new hire produces to demonstrate value, and they are mostly performance. What the first ninety days should produce is a shared, written answer to four questions.

1. What is this seat accountable for, in numbers? Three to seven outcomes, each an outcome rather than an activity, each with an expectation that is a number or a dated binary state with a source. This is the same structure as the Core Accountability System, and if the new leader is the first person in the company to have it written down, that is worth knowing about the company.

2. Which decisions are theirs, alone? Written, specific, with dollar figures where dollars are involved. “You own hiring for your team up to a Director level and a total comp of X, without checking with me.” Ambiguity here is not generous, it is expensive: it produces a leader who escalates everything to be safe, which is precisely the behavior you hired them to eliminate.

3. What are the seams? Every senior role has handoffs where the work crosses into somebody else’s territory. Name them and say who has the right of way. Unnamed seams are where invisible collisions happen, and a new leader has no history to navigate them with, so they hit every one at full speed.

4. What is the ninety-day check, and what happens after it? Set the date before they start. A scheduled honest conversation at ninety days is a gift to both sides; an unscheduled one at seven months is a crisis with a severance package attached.

The Founder’s Half of This

Two behaviors from the founder determine most of the outcome, and neither is about the hire.

Stop being the escape hatch. For as long as the team can route around the new leader by coming to you, they will, because it is faster and it worked yesterday. The only fix is to send people back, visibly, several times, including when you know the answer and it would take you nine seconds. This is uncomfortable and it is the whole job. If it feels impossible, the underlying problem is not the hire.

Say the standard out loud. New leaders fail against unwritten bars faster than anyone, because they have no accumulated read on your preferences. If good is defined only by your reaction, they will spend their first quarter learning your taste by breaking it, and you will spend it wondering if you hired wrong. If this sounds familiar, it is a standard that lives only in your head, and it costs more with a senior hire than anywhere else.

When It Is Genuinely Not Working

At ninety days, ask the diagnostic question honestly: is this a capability problem, a capacity problem, or a will problem? The Capacity Triangle separates the three, and the responses are completely different. Capability is coachable. Capacity is usually structural and yours to fix. Will is the only one where the answer is often the exit.

And check the conditions before you conclude anything about the person. If the authority was never transferred, the outcome was never written, and the seams were never named, you do not have a performance case. You have a management failure that will repeat. The reset or the release is the right frame once the conditions are genuinely clean, and not before.

The good news is that everything in this guide is cheap. Written outcomes, written decision rights, named seams, and a date on the calendar cost a couple of hours. The alternative costs a year and a good person.

Hire a second excellent person into the same conditions and you get the same result, a year later.