How to Onboard a New Hire

The offer is the start line, and most leaders read it as the finish.

That misreading is expensive, because a hire that fails at onboarding looks exactly like a hire that failed at the pick. Same symptom: a capable person underperforming eight months in. Same instinct: the screening must have been too loose. So the leader tightens the front of the process, adds an interview, orders another assessment, and never touches the ninety days where the damage was done. A leader who cannot see their own part in a failed landing will keep sharpening the wrong tool for the rest of their career.

That is the subject of this guide. Onboarding is where a leader's ownership of a hire gets tested, and the test does not end at the signature. It begins there.

There is something useful buried in the five steps that got you here. If you ran them, you did not only pick a person. You produced the raw material of their landing, and most of it is sitting in documents you are about to file.

Most failed hires were mis-landed, not mis-picked

When a hire goes wrong it usually goes wrong inside the first year, often inside the first ninety days, and usually for reasons that had nothing to do with whether the person could do the work.

They could do the work. What went missing was alignment. Nobody told them what winning looked like in the first month. The priorities they were handed contradicted each other. The leader who recruited them so attentively went quiet the day they started and reappeared only to deliver a correction. The new hire assembled the job from fragments, guessed wrong on a few that mattered, and got judged for the guesses.

None of that is a hiring miss. It is a landing miss, and the misdiagnosis is the costly part, because it sends the leader back to fix a stage that was working.

Bad candidates cause very few hiring failures. Misalignment, communication gaps, and absent support cause most of them.

Fit was provisional when you signed

The mistake hides inside a word. Fit gets discussed as though it were a property a candidate either has or lacks, something you screen for across a few interviews and then check off. Screen hard enough, the thinking goes, and the right person walks in pre-assembled.

The model treats a living relationship as a static measurement. Interviews can confirm that a candidate is capable, aligned on values, and plausibly suited to the work. What they cannot confirm is that the fit will hold once the person is inside the actual texture of your company: your pace, your politics, your particular way of running a job. Fit has seven dimensions and every one of them is provisional at the offer. They get proven, or lost, in contact with reality.

Fit also runs both directions, which is the part the screening model misses entirely. You are not the only one assessing. The candidate spends those first months deciding whether you and the company match the future they signed up for, and both sides own that verdict. A hire who concludes in week six that the job was described wrong starts leaving long before they resign, and no amount of front-end rigor prevents it if the landing is neglected.

You already wrote the landing plan

Every step of the hire produced an artifact that belongs in the first ninety days, and most companies throw all four away at the signature.

The job description defined what success looks like at thirty, sixty, and ninety days. It was written to tell a candidate what winning meant. That makes it the new hire's first-year map, and walking through it out loud in week one is the conversation that stops month four being a surprise to either of you.

The interview process produced a register of accepted risks. A risk you decided to carry knowingly is a day-one onboarding priority, and it stops being visible to anyone who was not in the debrief the moment a start date exists.

The interviews and reference calls produced development findings. A confirmed gap that matches what you already saw is onboarding input. Build the ramp around it, and tell the new hire what you are doing and why.

The decision produced ratings. Every "qualified but requires training" was a promise of specific coaching in a specific area inside a specific window. The strengths each interviewer named become what you build on. The gaps become the first check-in agenda.

Four artifacts, one landing plan, already paid for. The waste is not that companies fail to write onboarding plans. It is that they write them during the search and then file them under the closed search.

What makes a landing plan a plan

A landing plan is a plan only when three things exist: what will be done, who on your side owns it, and the date you check. "We will build the ramp around it" is a wish, and that wish is what the failed matches have in common. Name the owner and put the date on the calendar before the offer goes out.

The shape is straightforward for a new project manager. The first thirty days are for context, not output: meet the supers and the key trades, walk every active job, learn how this company runs a buyout and a change order, build the relationships the role depends on before anyone grades the work. By sixty days the plan names a real handoff, a project or a scope the PM owns outright, with the leader close enough to catch a fall and far enough back that the work is genuinely theirs. By ninety days there is a defined win, concrete enough that both people can look at it and agree the landing worked.

Written down and handed over with the offer, that sequence replaces the vague "watch and learn" that drowns good people in their first quarter. It also converts a feeling into a structure, which is the only form of fit anyone can be held to.

Make the company ready before the person arrives

Before the start date there is a call with the hiring team, and its purpose is to prepare the company rather than the hire. Four things get settled.

• Role ownership. What this person owns, agreed out loud before they walk in.
• The ninety-day sequence. The early milestones that will show whether the match is taking hold.
• Key relationships. The handful of people this hire has to connect with first, and who makes each introduction.
• Likely friction. The risks and gaps named before they bite.

A newly hired project manager was expected to own the schedule from week one. Leadership assumed the superintendent would walk them through a detailed handoff. Nobody had said that to either of them. One call before the start date closed the gap, and the PM never spent a confused morning guessing at it.

Most construction leaders, buried in projects and deadlines, do not check in with new hires as often as they intend to. This call is what makes the first month intentional instead of reactive.

Experience is not a substitute for training

Busy teams are rightly thrilled to hire someone who already knows the industry, and that relief turns into an assumption fast: this one will need less. No slowing down to onboard a veteran.

Your company is not another general contractor. You have developed a signature way of winning, and it is invisible from outside. How you manage schedules. How you resolve an RFI. How you define done. How you handle owners, inspectors, and chaos. A seasoned superintendent arrives with muscle memory built from a different shop's rules, standards, and vocabulary. They are used to operating someone else's machine, and nobody hands a new operator an excavator without the manual on the assumption that machines are all alike.

The assumptions pile up in predictable places: definitions, procedural steps, expected behavior, how problems get escalated and to whom. Without correction the new hire makes calls that do not match your intent, pushes hard in ways that read as disrespect, and underdelivers because no one told them what good looks like here. The damage is quiet, like water behind a wall. Bad habits set, trust erodes, schedules wobble, and the team starts questioning the skill of the person they were thrilled to hire.

Two corrections do most of the work. Explain every layer of the company out loud, from values and philosophy down to systems, processes, and the terms your people use without thinking. The act of explaining is worth as much to the leader as to the hire, because core values that have gone unspoken for years get examined on the way out. Then choose the teacher carefully. Excellent practitioners are often poor instructors, having forgotten what not knowing felt like. Appoint someone patient who will enjoy the work of making this person succeed.

None of this is hand-holding. It is calibration, and even the best operators need a field manual when they change teams.

The first two weeks are an emotional verdict

A new hire decides whether they made a mistake long before they decide whether they can do the job. They decide it in the first two weeks, sometimes the first two days, and they decide it on feeling. Onboarding is an emotional experience before it is a procedural one, and the leader who built the first weeks owns the verdict.

Five conditions are worth building on purpose, and each one has a failure mode that ends the relationship quietly.

• Valued. Direct communication and recognition that means something. The failure is a welcome email and a branded jacket, which reads as effort spent on the appearance of care.
• Connected. Introductions to the crew, a real mentor, inclusion in meetings before anyone has technically earned a place in them. The failure is an outsider doing careful work alone.
• Supported. Guidance, resources, and an obvious way to ask for help. The failure is a new hire who feels unprepared, which is a verdict on the process and never on the person.
• Clear. The role, the priorities, and the way work gets done here, stated on day one. The failure is ambiguity, and ambiguity spends confidence faster than difficulty does.
• Trusting. Promises kept, truth told, accountability modeled before it is demanded. The failure is silence, which a new hire reads as disapproval and fills with their own worst assumption.

Unnecessary stress in the first weeks is one of the cleanest predictors of fast turnover. Pace the learning curve and watch for the moment you have stopped training someone and started drowning them.

The temptation, when a start is rough, is to read it as proof you hired the wrong person. More often it is proof you onboarded them into uncertainty and then resented them for being uncertain.

Check-ins are guardrails, not the driver

A guardrail does not steer a truck. It keeps a capable driver off a cliff they could not see coming. A structured check-in works the same way: it does not replace a leader's mentorship, and it does not relieve anyone of building a real relationship with their team. It makes sure the conversations a busy leader intends to have happen instead of falling through a deadline-heavy quarter.

• Week 1. Do they feel welcome? Do they have what they need to work?
• Month 1. Are they integrating? Any early concern worth naming while it is small?
• Month 2. Have the right relationships formed? What is still unclear?
• Month 3. What is working, what is not, and where does the support have to improve?
• Month 6. Are they set up for the long run?
• Year 1. What did this hire teach the leadership team about doing the next one better?

A newly hired estimator arrived at a second-month check-in frustrated: no access to the software the bid calculations required. Leadership had assumed IT handled it. The gap had been throttling productivity for weeks and would have become a resignation eventually, because that is what unaddressed friction turns into when nobody asks the right question at the right time.

Three questions do more than a well-built agenda. Are you getting enough feedback? Do you understand what leadership expects of you? Have you told your manager how you prefer to receive feedback? The third one moves ownership of the experience to the person living it, which is where a good share of it belongs.

If the search included a bilateral assessment, revisit it once the two people have worked together. At the decision it predicted working styles and friction points. In the first month it becomes testable. A superintendent and a project executive who both scored high on assertiveness kept colliding, each reaching to lead the same conversation, until the review gave the dynamic a name. Once it had a name they adjusted how they spoke to each other rather than concluding the other was difficult.

Look at what they walked into

The most overlooked onboarding problem is almost never the new hire's competence, and it is not always in the hire at all. Sometimes it is in the environment you dropped them into.

A builder I work with hired a project manager into what looked, on paper, like a healthy team. A long-tenured, well-liked employee was quietly poisoning it. That person had influence and was vocal, and the negativity moved through the group until relationships the owner had held for twelve years went cold and even the client turned. When the employee finally quit, the team and the client both exhaled. Nobody had realized the culture was sick until the infection left.

With that gone, the new PM said the thing out loud in a management meeting: you are a micromanager, nobody can work like this. It could have ended badly. The owner leaned in, invited the rest of the feedback, owned their share, and told the PM to call it out in real time if it continued. Over the following weeks the team could see that the micromanagement had been compensating for the departed employee's lack of follow-through. With someone competent in the role, the gaps were obvious.

Had the owner told the PM to toughen up, they would have lost a high-potential hire, and not for lack of capability. Strong people leave when naming a problem gets them treated as one. Before you conclude that a struggling hire is the problem, audit the ground they are standing on, including the people already standing on it and your own management style.

Ninety days is not a probation

Some companies make the evaluation explicit: a probationary period, a trial, a ninety-day window before anyone commits. The logic is that naming the scrutiny produces better behavior.

There is no right answer on trial periods, only skillful and clumsy versions of them, and the difference is entirely in how the expectations were set. Three principles separate the two.

• The company is on trial as well, and the hire has to feel that. A new employee who senses they are being tried out while the firm risks nothing will behave accordingly.
• Never use a trial with a candidate you are undecided about. Commit or do not. Asking someone to take a risk you are unwilling to match is how the arrangement backfires.
• Define what a successful period looks like, give them the goal, and coach to it. Encouragement and structured criticism aimed at making them succeed, not a running tally of failures.

The deeper problem with the ninety-day question is what it admits. If it takes ninety days to learn whether a hire will work out, the expectations set during the search were not clear enough. An explicit probationary period at the management level is a company that knows its hiring process is unreliable and has chosen to move the cost onto employees rather than fix it. Candidates should read it that way, and so should you when you catch yourself writing one.

Before your next hire, write down articulately why this person will succeed, and then hold yourself to being right, which means making it right. The candidate did not hire themselves.

When the landing is failing

Sometimes it does not take, and the honest move is to say so early.

The failure to avoid is the surprise. A hire who is let go without having been told clearly, more than once, that something was not working has been managed badly on the way out as well as on the way in. Surprise firings expose an absence of communication about problems, and the team reads them accurately: if that could happen with no warning to someone else, it can happen to me.

Most of what looks like a bad hire at month three is not a character problem, which is why the diagnosis has to come before the decision. Work out what went wrong first, because the answer is often upstream of the person and will otherwise repeat. When separation is genuinely right, there is a just way to do it, and it starts long before the conversation.

Onboarding never ends, because alignment never ends

A hire can be technically in place and still out of alignment, and alignment drifts the way anything drifts when nobody tends it. You do not pour a foundation and walk away from it. You watch the cure and check for cracks as the structure goes up.

• Months 0 to 3, the foundation. The risk is loading someone with information and no connection. The goal is that they understand expectations, the team, and what they own.
• Months 3 to 12, practical integration. The risk is assumption, because the person looks up to speed while still learning how problems get solved here. The goal is structured feedback often enough to catch a struggle early.
• Years 1 to 3, performance and growth. The risk is stagnation. The goal is a visible path forward and a role refined around what they turn out to be good at.
• Year 3 and beyond, evolving leadership. The risk is complacency, since senior people are assumed to need nothing. The goal is revisiting their purpose in the company as goals, markets, and ambitions change.

None of that is onboarding in the paperwork sense. It is the same work under a different name, which is why the handoff to retention is not really a handoff. People stay where they are still growing, still aligned, still chosen. A leader who checks in at thirty days and disappears for a year has not onboarded anyone; they have deferred the drift. A leader who tends the match keeps the person they already paid to find, and one who assumes it pays to find them again and calls the churn a market problem.

Continuous development is also how a strong project manager becomes a capable executive, which is the only version of succession that arrives on time. A new hire cannot align themselves to a target only the leader can see.

Think about your last hire's first ninety days. What were they designed to produce, and who owned that design. If the honest answer is nobody, you have found the place where your next hire will be won or lost.