Skip to content
The Pragmatic Leader

Leadership & ManagementCross Organizational

Onboarding Is Where the Hire Is Won or Lost

Aaron Wise · · 8 min read

A newly planted sapling tied to a wooden stake beside a green field, young trees guarded

“The beginning is the most important part of any work.”
— Plato, Republic, Book II (Jowett translation)

Most companies treat the signed offer as the end of hiring. It is closer to the halfway point. The interview process tells you whether a person can do the job. The first ninety days decide whether they will do it here, with this team, on these problems. A strong hire who spends the first quarter without access, context or a clear first goal often looks like a weak hire by the end of it, and by then the company has usually started to believe it.

Onboarding belongs to the hiring manager, not to HR. HR can own the paperwork, the laptop and the benefits enrollment. Those matter, but they are the floor. What decides whether a senior or technical hire succeeds is whether the manager has done the work to set them up: clear expectations, the right relationships and a meaningful problem to solve early.

Why the first ninety days carry so much weight

New hires form their view of a company quickly, and so does the company form its view of them. Both views harden early. A senior engineer who spends the first two weeks waiting for repository access concludes that the company is disorganized. A VP who has no clear mandate in the first month starts building one alone, often in a direction the CEO did not intend. Meanwhile the team watching them forms its own impression, which is hard to reverse once it settles.

Senior hires have it hardest. They are expected to contribute quickly and are paid accordingly, but they also need the most context: the history behind decisions, the politics between functions, the commitments already made to customers and the board. That context is rarely written down. It lives in people’s heads, and the new hire has to find out whose.

The data on how most companies handle this is not encouraging. Gallup reports that only 12% of employees strongly agree their organization does a great job of onboarding new employees. Even allowing for the limits of a survey question, that is a large gap between how much the first months matter and how much effort most companies put into them.

Onboarding as the last step of hiring

The useful reframe is to treat onboarding as the final stage of the hiring process, with the same owner and the same standards. The hiring manager wrote the role, ran the interviews and made the decision. They are best placed to translate what they learned in the process into a plan for the first ninety days.

That reframe has a practical consequence: the onboarding plan should start before the offer is signed. During interviews, the panel learns where the candidate is strong and where they will need support. A well-run process, of the kind described in building hiring into a talent engine, produces written evidence against defined criteria. That same evidence should shape the onboarding plan. If the panel thought the candidate was technically excellent but untested at managing across functions, the plan should put them in front of their peers early and often.

It also changes who is accountable when a hire fails. If onboarding is the last step of hiring, a hire that fails in the first six months is a hiring failure, and the hiring manager owns the review. That is uncomfortable, and it is the point. A company that blames every early departure on the person learns nothing about its own process.

What good looks like

Good onboarding for a senior or technical hire comes down to a few concrete things that are done before the person arrives, not improvised after.

A written 30/60/90. A short document, written by the manager and agreed with the hire in their first week, that says what success looks like at thirty, sixty and ninety days. The first thirty days are usually about learning: meeting the people who matter, understanding the systems and the customers, and forming a view. The next thirty are about a first contribution. By ninety days the hire should own something real. The plan is a starting point, not a contract, and it should change as the hire learns. What matters is that both people have the same picture of success and can see when it drifts. The product version of this, frameworks for a product leader’s first 100 days, adapts well to engineering and data leaders.

A first win, chosen deliberately. Pick a problem the hire can solve in their first month or two that matters to the team and is visible to the people they need to work with. It should be real but bounded. For a senior engineer, it might be a reliability issue that has bothered the team for months. For a new head of data, it might be one trusted metric the executive team argues about. The first win builds credibility, teaches the hire how the company actually works, and gives the manager an early read on how they operate.

Access on day one. Laptop, accounts, repositories, dashboards, documentation, calendars and the right channels, all working on the first morning. This sounds basic and is routinely missed. Every day without access is a day the hire spends learning that the company does not plan ahead. For technical hires, a working development environment on day one is the clearest signal you can send that the company respects their time.

A named partner. One person, not the manager, whose explicit job for the first ninety days is to answer the questions the hire does not want to ask the boss. Who actually makes this decision? Why does this team distrust that one? What happened the last time someone tried this? The partner should be a peer with standing and enough context, and they should have time set aside for it. A partner chosen at random from whoever is least busy is worse than none.

Add to those a schedule of introductions planned before the start date, and a manager who holds a short weekly check-in through the first ninety days, and most of the risk is covered.

What bad looks like

The familiar failures are easy to recognize. A hire arrives to find no one expected them that day. The manager is traveling for the first week. The onboarding plan is a list of compliance trainings and a link to a wiki last updated two years ago. The hire is told to “take a few weeks to get your bearings,” which means nobody has thought about what they should do.

The senior version is subtler. An executive hire is given a broad mandate and no specific expectations, and left to define the role alone. They spend the first two months meeting everyone and forming a view, then present a plan that conflicts with what the CEO assumed they would do. Neither person is wrong. They simply never wrote down what success looked like. That pattern is one reason many senior hires at early-stage companies do not last, a problem examined in why some startups are not ready for senior engineering leadership.

The other failure is the opposite: throwing the hire into a crisis on day one because they are senior and the team is stretched. Sometimes there is no choice. But a hire whose first experience is firefighting never gets the context to understand why the fires keep starting, and often burns out on the same problems the last person did.

The cost of a failed hire

The direct costs of a failed senior hire are easy to list: recruiting fees, salary for the months they were in the role, severance, and the cost of running the search again. Recruiting alone is expensive: SHRM’s 2025 benchmarking survey put the average cost of making one executive hire at $35,879, before a dollar of salary, and a failed hire means paying it twice. The indirect costs are usually larger and harder to see.

A failed engineering leader leaves behind decisions made on a plan nobody will continue, a team that has been through a change of direction twice, and peers who are now wary of the next hire. Good people on the team may leave, because a bad six months under a struggling leader is a common reason for strong engineers to start looking. The company also loses time it rarely has: a role that was critical enough to hire for sits effectively empty for the better part of a year.

Put next to those costs, the investment in onboarding is small. A manager who spends a few hours writing a 30/60/90, choosing a first win and briefing a partner, then thirty minutes a week checking in, is buying insurance on one of the largest decisions the company makes that year. If you need to make the case for that time to a leadership team, the arithmetic in making the data-driven case for growing your team works just as well for protecting the hires you already made.

How it changes by stage

Seed and early Series A. Nobody owns onboarding, because nobody owns anything that is not product or sales. The founders are the onboarding, and the risk is that they are too busy to do it. The fix is small: a one-page 30/60/90 for every hire, written by the founder who made the hire, and one named partner. At this stage each hire is a large fraction of the company, so a failed hire costs proportionally more. Early hires are often generalists who have to define their own scope, and the shift from generalists to specialists makes onboarding harder as roles narrow.

Series B. The company is hiring fast, often doubling in a year, and onboarding is where that growth breaks. New managers are onboarding new hires while still learning their own jobs. This is the stage to build a standard: templates for the 30/60/90, a partner program, an access checklist owned by IT, and a short review of every hire at ninety days. The review should include the question “what would have made your first three months better?”, asked of the hire and taken seriously. The way teams and structures change through this growth is the subject of how teams, pitches and capital structures evolve together.

Later stage. Formal onboarding programs exist and handle the general material well. The risk is that the program replaces the manager’s part rather than supporting it. Company-wide onboarding cannot tell a new director which three stakeholders will decide whether they succeed. Only their manager can. Keep the 30/60/90 and the first win as manager responsibilities, whatever the program covers.

Across all stages, the principle is the same one that applies to building a culture of trust: people trust what they experience, not what they are told. The first ninety days are when a new hire learns whether the company does what it said it would during the interviews.

For your next leadership meeting: take the last three senior hires. Did each one have a written plan for their first ninety days, a first win chosen in advance and a named partner? If not, what would you change before the next one starts?

Sign up for Newsletter