How to Onboard a New Leader So They Don't Fail in the First Six Months
By Brendan Levin. 20+ years scaling businesses, from teams of 8 to 600 and budgets from startup to $100m.
Key takeaways
- Senior hire failure is almost always an onboarding failure, not a hiring failure.
- Without written decision rights and a spending threshold, every real call routes back to the founder by default.
- The hire needs named, checkable outcomes for the first 90 days before their start date, not after.
- The founder has to visibly stop making the decisions the hire is supposed to own, or the hire is powerless.
Why senior hires fail in the first 90 days
The autopsy on a failed senior hire usually finds the same things. No written decision rights. No standing weekly rhythm. No named outcomes for the first 90 days. And a founder who kept making the calls the hire thought they were taking. The hire was competent. The structure around them was not.
This is a founder-led business problem in particular. When everything has routed through one person for years, the organisation has learned to wait for that person. A new leader walks in and the team still routes to the founder by default, because the decision map was never redrawn. The hire loses credibility inside sixty days, and by day ninety they are either managing up to survive or already looking for the exit.
The fix is not a better onboarding conversation. It is a written operating structure that exists before the hire starts, and a founder who changes their own behaviour on day one. Without both, you are running an expensive experiment with a predictable result.
The four things that have to exist before the hire's first day
These are not nice-to-haves. They are the conditions for success. If any one is missing, you have an onboarding gap.
First, a written decision-rights threshold. Not a vague org chart, a real line. For example: any spend under $2,000, the owning person acts and tells you after. Any spend from $2,000 to $15,000, the hire approves and tells the founder after. Any spend above $15,000, the founder is in the decision. That is checkable. 'You own operations' is not. See how to define the actual threshold for your business.
Second, named 90-day outcomes written before day one. Not a list of responsibilities. Specific, checkable results. 'By day 90, the weekly ops review is running without me in the room' is an outcome. 'Responsible for operations' is a job description. The hire needs to know what winning looks like so they can organise their own first weeks instead of waiting to be directed.
Third, a standing operating rhythm the hire runs. A weekly cadence walking the numbers and surfacing what is stuck, owned by the hire, not the founder. If the founder is still running the Monday meeting in week four, the team has not transferred authority.
Fourth, a named list of decisions the founder is giving up. Written down. Shared with the team. If the founder does not say out loud which calls they are stepping back from, the team will keep routing those calls to the founder, and the hire will spend their first months fighting to be heard in their own domain. See building a leadership team that actually holds authority for how to run that handoff.
What the founder has to stop doing on day one
This is the part most onboarding plans skip. The hire cannot succeed if the founder's behaviour does not change. You can write the best decision-rights document on earth and then blow it in the first week by answering a direct report's question that should have gone to the hire.
Three specific founder behaviours that kill senior hires. First, answering questions from the hire's team directly, even helpfully and quickly. Every time you do it, you signal that the chain of authority still runs through you. Second, reversing or refining the hire's decisions in front of the team. Even once. Even with good intent. Third, running any meeting the hire was supposed to own. The room reads the leader, not the org chart.
The honest test: at the end of week two, ask the hire's direct reports who they go to first when they are stuck. If the answer is not the hire, you have a founder-dependency problem that no amount of culture work will fix. You need to change who owns the decision, not just who is listed as the decision-maker.
A quick self-test: is your business ready to receive a senior hire?
Before you post the role, answer these four questions honestly. They take two minutes and they will save you a six-figure mistake.
If you cannot answer all four with a specific, written artefact that exists today, you are not ready to bring in a senior hire. You are ready to build the structure first.
- Can I hand the hire a written list of decisions they own outright, with the spending or risk threshold at which they never involve me?
- Can I name three checkable outcomes for their first 90 days that are not just a summary of the job description?
- Is there a standing weekly rhythm they will run from week one, with a fixed agenda and the right numbers on the table?
- Can I name five decisions I am giving up from day one and commit to not being in the room when those calls are made?
Structure first, senior hire second
The most common mistake in founder-led businesses under fifty people is treating a senior hire as the solution to a structure problem. Hiring before the structure is built means you relocate the dependency onto the hire at a senior cost. If they leave, the work routes straight back to the founder.
The operating structure has to hold the business before the hire arrives. That means direction written as a single sentence with the two or three numbers that prove it moved. It means decision rights with real thresholds, not vague ownership. It means a weekly operating rhythm that runs on the structure, not on whoever is loudest in the room. When those three things exist, a senior hire has something to plug into. Without them, they are building the plane while the founder is still flying it.
If you are unsure whether your business is ready to receive a senior leader, the free Founder Dependency Diagnostic maps where your week actually goes and shows what still depends on you. That read will tell you whether you have a staffing gap or a structure gap before you make the hire.
If you are not sure whether your business is ready to hand authority to a senior hire, the free Founder Dependency Diagnostic will show you what still runs on you before you make the call.
Take the free diagnosticCommon questions
What is the most common reason a new VP or director fails in the first 90 days?
The most common reason is that the founder never changed their own behaviour. The hire was given a title and a scope, but the team still routed decisions to the founder by default because no written decision-rights threshold existed, and because the founder kept answering questions that should have gone to the hire. The hire loses credibility fast in that environment, and by day ninety they are either checking out or leaving.
How specific do decision rights need to be for a senior hire to actually use them?
They need to be specific enough that the hire can act without a conversation. A real threshold works: any spend under $2,000, the owning person acts and tells the hire after. Any spend from $2,000 to $15,000, the hire approves and tells the founder after. Anything above that, the founder is involved. 'You own the budget' is not a decision right. It is a description of a scope that will be disputed in the first month.
Should I give a senior hire a 90-day plan or let them build their own?
Give them the 90-day outcomes before day one, not a plan. The outcomes are yours to name: what does winning look like at day 30, 60, and 90, in checkable terms? The hire should own how they get there. That split respects their seniority while making sure you are aligned on what success actually means. A hire who builds their own plan from scratch often spends the first month in discovery mode when you needed them moving in week one.
How do I stop my team from going around my new senior hire and coming to me?
You redirect every single one of those conversations, out loud, in the moment. When a team member brings you something that belongs to the hire, you say: 'That is a decision for [name], go to them.' You do not answer it first and then say go to them. Every time you answer it, you confirm that the routing to the founder still works. Do it consistently for two weeks and the team recalibrates.
What is the difference between onboarding a senior hire and onboarding a regular employee?
A regular hire learns the system. A senior hire needs to own part of it from day one. That means the onboarding is not about orientation, it is about authority transfer. You are handing over a domain, and the onboarding protocol has to make that transfer visible to the team, not just described in a conversation between you and the hire. Written decision rights, a standing meeting they run, and a list of calls the founder is stepping back from are what make the transfer real.
What if I hire a senior person and realise too late that my business had no operating structure for them to run?
You have two options. The first is to build the structure alongside them, which means the hire spends their early months doing structural work that should have been done before they arrived. That is expensive and slows their impact. The second is to bring in outside help to install the structure quickly. Either way, name the problem clearly with the hire. A senior operator can handle honesty. What they cannot handle is being set up to fail without being told why.