Onboarding process for senior hires: a 30/60/90-day plan that works

A new Operations Manager or Financial Controller arrives with a mandate, no relationships and a team that is watching closely. The business expects results quickly. The person is trying to learn the site, the people, the numbers and the unwritten rules all at once. If they are left to "find their feet", three things happen: they take longer to become effective, they make avoidable early mistakes that cost credibility, and a meaningful proportion of them leave within a year.

The early departures are the expensive part. Every one repeats the full cost of the search, the vacancy and the ramp-up, which we work through in the cost of a bad hire. A structured first 90 days is the cheapest insurance an employer can buy, and most of it is just deciding in advance what the person needs to know and who they need to meet.

Onboarding starts at acceptance, not on the first morning. Senior candidates typically serve four to eight weeks' notice, and that period is when counter-offers land and doubts creep in. Use it:

• Have the person they report to call within a week of acceptance, just to say they are looking forward to it.
• Send the practical material early: employment agreement countersigned, site information, parking, what to bring, who they will meet on day one.
• Share reading: the last few months of management reports, the strategic plan, the org chart with names and photos, the site health and safety induction.
• Invite them to something low-key before they start, such as a team lunch or a site walk, if they are comfortable.
• Have the basics ready for day one: laptop, logins, phone, access card, a desk. A senior person waiting three days for an email account reads it as a signal about the business.

When we place someone we stay in touch through the notice period for the same reason. It is the window in which placements are most likely to fall over.

• Day one, first hour: the manager meets them personally. Not HR, not a delegate.
• Safety induction completed and recorded before they go onto the floor.
• The written 90-day plan (below) handed over and talked through. Expectations, priorities, how success will be judged.
• Meetings booked with every direct report, one-on-one, in the first week. Thirty minutes each: what they do, what is working, what is not, what they need.
• Introductions to the leadership team, key peers and the people who make things happen regardless of title.
• A guided walk of the site or the process, ideally with a long-serving person who knows where things really are.
• Access to the numbers: budgets, KPIs, reports, the systems they will live in.
• Diary rhythm set: weekly one-on-one with their manager, leadership meeting cadence, any standing reviews.
• End of week one: a short conversation with their manager. What has surprised you? What do you need?

Write this before the person starts and give it to them on day one. It should fit on one page. The pattern is learn, then contribute, then own.

Days 1 to 30: learn

Objective: understand the business, the people and the numbers well enough to have an informed view.

• Meet every direct report and key stakeholder one-on-one; meet major customers and suppliers where relevant
• Understand the key metrics, how they are produced and what they are telling us
• Learn the core processes by observing them, not reading about them
• Identify the two or three most obvious issues, without acting on them yet
• Check-in at day 30: a one-hour conversation with their manager. What have you seen? What do you think? What do you need from me?

Days 31 to 60: contribute

Objective: start making decisions and delivering visible progress on something that matters.

• Pick one meaningful early win and deliver it, something the team will notice
• Take full ownership of the routine: the daily meetings, the weekly reports, the monthly review
• Present an initial assessment to the leadership team: what is working, what is not, what they propose
• Begin any people changes that are clearly needed, with support from their manager
• Check-in at day 60: review progress against the plan, adjust priorities, surface any friction

Days 61 to 90: own

Objective: be fully accountable for the role with a plan for the year ahead.

• Present a 12-month plan with measurable targets, aligned to the outcomes in the job description
• Have set expectations with each direct report and started regular one-on-ones
• Be the person the business goes to for that area, rather than the person who used to do it
• Review at day 90: a formal conversation. Is this working, for both of us? What is the plan for the next nine months?

The plan should be tied to the outcomes in the job description. If the description promised "delivery in full and on time above 96%", the 90-day plan should show the path towards it.

Onboarding fails most often because the new person's manager, usually the owner or GM, disappears after day one. They hired a senior person precisely so they could step back, and they step back immediately. The new person is left guessing at expectations, learning the politics the hard way and making early calls without context.

The manager's minimum commitment:

• A weekly one-on-one for the first 90 days. Non-negotiable, in the diary.
• Explicit expectations: what decisions the person can make alone, what to bring to the manager, and how the manager likes to be communicated with.
• Context the org chart does not show: the history, the relationships, who is trusted, what has been tried before.
• Public backing. When the new person makes a call, the manager supports it in front of the team, and raises any concern privately.
• Honesty about early concerns. If something is not working at week three, say so at week three.

Most placements that fail do so quietly. The new person is unsure about something in week four, does not want to look weak by raising it, and the manager assumes silence means all is well. By month four the gap has become a problem, and by month six someone is talking about it being "not the right fit".

A structured follow-up from someone outside the reporting line catches this early. That is why we run a post-placement follow-up programme with every person we place and with their manager: separate conversations at agreed points in the first months, asking how it is going, what has surprised each of them, and whether anything needs addressing. People say things to us they are not yet ready to say to each other, and most of what we hear is fixable if it is heard early.

If you are onboarding a senior hire yourself, borrow the idea. Ask a trusted senior person from another part of the business, or an external adviser, to have a coffee with the new person at 30 and 60 days. The question is simple: how is it really going?

• No plan. "Spend the first month getting to know everyone" is not a plan; it is an absence of one.
• Too much too soon. Handing over a crisis on day two, before the person knows the people or the process, sets them up to fail publicly.
• Too little too long. The opposite failure: keeping the new person in "learning mode" for months while the old way of doing things continues around them.
• Undermining from above. The owner keeps making the decisions the new person was hired to make. The team learns to go around them.
• Ignoring the team's reaction. An internal candidate who missed out, a long-server who is unsettled. These need attention in the first month, from the manager, not the new person.
• Relying on a 90-day trial period instead of an onboarding process. One is a legal backstop; the other is how you make the hire work.

Good onboarding is mostly attention: deciding what the person needs, making time for them, and asking how it is going before you assume. If you would like help with the plan for a senior hire, or want to know how our follow-up programme works, get in touch. Our permanent recruitment service includes onboarding support and follow-up as standard.