A new executive arrives with a laptop, a calendar full of introductions and a folder of strategy decks. Ninety days later the company finds out whether the hire worked. Very little that happens in between is designed.
What goes wrong is rarely the thing the hiring committee worried about. A 2013 Egon Zehnder survey asked more than 500 executives worldwide what made taking on a new role difficult. The leading answers were a poor grasp of how the organization works, at 69 percent, and cultural misfit, at 65 percent. Difficulty forming alliances with peers came third at 57 percent. None of those are competence problems.
An executive onboarding plan exists to shorten the period in which a capable person is operating without a map. It is not a checklist of systems access and benefits enrollment, and it is not a welcome. It is a deliberate transfer of context, relationships and permission, with someone accountable for it.
What this comes down to
The new executive needs three things faster than they will get them alone. An accurate picture of how decisions really get made. Honest relationships with the four or five peers who can block or accelerate the work. And early agreement on what they are expected to change, and what to leave alone. Everything below is in service of those three.
The failure is almost never about capability
The hiring process tests capability heavily and tests context not at all. A candidate is assessed on track record, functional depth and how they think. They are not assessed on their ability to read an unfamiliar power structure at speed, because nobody can assess that from outside it.
So a strong hire arrives and starts making reasonable decisions based on how organizations they have known tend to work. Several of those decisions are wrong here for reasons nobody has explained, because the reasons are unwritten. By the time the pattern is visible, the new executive has spent credibility they cannot easily earn back.
This is fixable, and it is cheap to fix relative to the cost of a failed executive hire. It requires someone to say the unwritten things out loud, early, to a person who has no way of discovering them otherwise.
What has to exist before day one
The gap between the accepted offer and the first day is the most wasted period in executive hiring. Three things should be settled in it.
First, a written mandate agreed by the hiring executive and the new hire. It covers what must change, what must be protected, and the two or three outcomes that define success in year one. Disagreement here surfaces best before the person starts, when it is still a conversation rather than a conflict.
Second, a named integration owner who is not the hiring manager and not HR generically. Someone with standing, whose job for ninety days is to answer the questions the new executive does not know to ask.
Third, a stakeholder map that is honest about relationships rather than reporting lines. Who was a candidate for this role. Who was close to the predecessor. Which two functions have an unresolved dispute the new executive is about to inherit.
The ninety days, in three phases
Days 1 to 30: learn the system, not the org chart
The objective is an accurate model of how the organization actually operates. Structured conversations with fifteen to twenty five people, most of them below the executive's own level, asking the same small set of questions so that patterns emerge rather than anecdotes.
Useful questions are concrete. What decision took far longer than it should have this year? What do we consistently say and not do? What would you change if this were yours? Who do I need to know who is not on my list? Resist making changes in this window, with one exception: anything that is unsafe, unlawful or losing money daily.
Days 31 to 60: form a point of view and test it privately
By day 35 or so a view is forming. Write it down and test it with three or four people individually before presenting anything to a group. This is the phase where a new executive learns the reason behind a practice that looked irrational. Or confirms that it is indeed irrational, and that nobody has had the standing to say so.
Both outcomes are valuable, and both require doing the testing in private. A point of view first aired in a large meeting cannot be revised without cost.
Days 61 to 90: commit to a small number of things
Pick two or three changes, not eight. Announce them with the reasoning, the sequence and the measure attached, and say clearly what you are choosing not to touch this year. The restraint is what makes the commitments credible.
One of the chosen items should produce a visible result inside ninety more days. Early evidence that this executive finishes what they start buys the room for the harder items.
The assimilation session most companies skip
There is a well established facilitated format, usually called a new leader assimilation session, that compresses months of relationship building into about three hours. It runs somewhere between weeks three and six.
A neutral facilitator meets the new executive's direct reports without the executive present. The group works through a short set of questions. What do we know about this person? What do we want to know? What do they need to know about us? What are we worried about? What should they not change? Responses are captured thematically rather than attributed.
The facilitator then briefs the new leader privately, and the group reconvenes for the leader to respond to the themes and commit to a few specific things. It works because it gives a team permission to say in week four what would otherwise leak out over eighteen months. The new leader gets an unusually direct read on what they have walked into.
Onboarding the team to their new leader
Almost every executive onboarding plan is written one way: the company briefing the leader. The reverse transfer is left to chance, and it causes as much damage.
A team that has just lost a leader is reading the new one constantly and interpreting normal behavior as signal. A quiet first fortnight reads as disapproval. A direct question reads as a threat. The team needs to be told plainly how this person works. How they prefer bad news delivered. What a request means versus what an instruction means. What they will want consulting on, and what they genuinely will not.
It takes one hour and it prevents a quarter of misreading. Unresolved conflict left over from the previous regime has to be surfaced too. A new leader inheriting a team with existing fractures will be blamed for them within two months.
What the sponsor owes the new executive
The hiring executive has obligations that usually go unstated. The first is visible sponsorship in the first month, in front of the peer group, in a form that transfers standing rather than merely welcoming the person.
The second is candor about the things that were softened during recruitment. Every hiring process oversells something. The sponsor should correct the record early, while it still reads as honesty rather than as a discovery.
The third is a scheduled thirty, sixty and ninety day conversation with a real agenda, not a passing check in. Many organizations also bring in external coaching at this point. It is one of the clearest situations where a coach earns their keep. The new executive needs somewhere to think out loud that is neither their boss nor their team.
The place this usually falls apart
It falls apart in week six, and the cause is almost always that the integration owner has gone back to their day job. The plan is written, the first weeks are busy and well supported, and then attention moves to the next thing. The new executive is by then fluent enough to look settled. That is exactly when the unwritten rules start to bite, and nobody's job is explaining them any more.
The second failure is quieter. The mandate agreed before day one was written in general language, so the new executive and their sponsor have different pictures of what is being changed. Nobody notices until the executive does something the sponsor considers out of scope, usually around month four. Because both parties believe they agreed, the resulting conversation is about trust rather than about scope, and that is a much harder conversation to recover from.
A third pattern is worth naming because it looks like success. The new executive is embraced quickly by the existing group and adopts their view of the organization within a month. The company has just paid a large sum for an outside perspective and lost it, and nobody will notice for a year.
Try it on one hire before you build a program
You do not need a program to find out whether this works. Take the next senior hire and run the reduced version. A written mandate before day one. A named integration owner with protected time. The assimilation session in week four, and the thirty, sixty and ninety day conversations actually held.
That costs a few hours of executive time and no budget. At day 120, ask the new executive three questions. What did you have to learn the hard way? What did you get wrong because nobody told you? What would have saved you a month? Their answers are your design document, and they are far more specific than anything a template will give you.
Run it twice and you will know which parts to systematize. If transitions in your organization keep going the same way, the cause is usually structural rather than individual. Our organizational development practice is built for exactly that diagnosis.
Frequently Asked Questions (FAQs)
How long should executive onboarding last?
The structured plan should run at least ninety days, with formal checkpoints at thirty, sixty and ninety. Full integration takes longer than that, and support that stops at day 90 typically stops just before the hardest period. A light touch continuation to month six, built around the mandate rather than around orientation, is a better design.
What is the difference between executive onboarding and standard employee onboarding?
Standard onboarding transfers process, systems and role knowledge. Executive onboarding transfers context, relationships and political permission, most of which is unwritten and cannot be handed over in a document. The new executive also has to establish authority with peers who did not hire them, which no orientation program addresses.
Who should own an executive onboarding plan?
A named individual with organizational standing who is neither the hiring manager nor the new executive's direct report. The hiring manager cannot fill the role because the new executive will not ask them the questions that reveal confusion. HR can design and run the process, but the integration owner needs enough internal credibility to explain how power actually works.
Should a new executive make changes in the first 90 days?
A small number, announced late in the period and chosen deliberately. Anything unsafe, unlawful or losing money daily is addressed immediately, and everything else benefits from the context gathered in the first month. The common error is not moving too slowly but committing to too many things at once, which spreads attention until nothing visibly finishes.
What should be measured during executive onboarding?
Whether the mandate is still agreed by both parties at day 90. The quality of relationships with the four or five peers who can block the work. And whether at least one committed change is producing visible evidence. Time to productivity metrics tend to measure activity. These three measure whether the person is actually able to operate.