Ask a management team what a hire costs and the answer usually starts with the recruitment fee and the salary. Both matter. Neither captures the largest and least visible line: the months before a new starter produces the output the role was created for. That interval is time-to-productivity, and in many growing businesses it is measured informally, if at all. Payroll records the salary from day one. The management report records the headcount. The cost of a role that is only half-performed is absorbed quietly by colleagues, customers and delayed work.

For a business that hires to add capacity, the gap between headcount and output is a direct constraint on growth. Onboarding is the process that closes it. Treated as a designed sequence of work, it shortens the ramp, reduces early attrition and gives the business a measurable return on each appointment. Treated as an improvised welcome, it leaves the most expensive part of the hire to chance.

The cost that sits between headcount and output

The conventional cost of a hire combines recruitment spend with salary. A fuller calculation includes the salary paid before full output, the manager time consumed in supervision and correction, the time colleagues spend answering questions that documentation should have answered, and the productivity lost while work waits for the new person to become useful.

Some of that cost is unavoidable. Every role has a learning curve, and a period of observation, questions and supervised work is how a new starter learns how the business actually operates. The distinction that matters is between productive ramp and unproductive delay. Productive ramp builds capability. Unproductive delay is time spent waiting for access, unclear priorities, missing information or work that has not been prepared. The first is an investment. The second is a design failure.

Reframing the cost this way changes the question a manager asks. Instead of asking only whether the hire was good, the business asks how quickly it allowed a good hire to become effective. That is a question about the operating system around the role, not about the individual's ability.

Why ramps run long

Slow ramps tend to share a small number of causes. The first is that the workflow lives in one person's head. The role exists, but the inputs, decisions, handoffs and standards that make it work have never been written down. The new hire spends the first weeks reconstructing a process that colleagues already know, asking questions at the pace the team can absorb them.

The second is that no one owns onboarding. Human resources may cover contracts, payroll and compliance, while the manager assumes the team will handle the rest. In practice, the new starter is left to assemble a picture of the role from meetings, old documents and informal conversations. Nobody is accountable for the first ninety days as a whole.

The third is that the first weeks are filled with orientation rather than real work. Introductions, reading and shadowing feel useful because they are busy. But a month of observation with no defined output leaves the hire without evidence of progress and without the feedback that comes from doing the job. The transition from watching to owning work then arrives abruptly, often with little support.

A vague mandate makes all three worse. If the role is described only in broad terms, the new starter cannot tell which tasks matter most or what a good result looks like. Managers who are themselves stretched may postpone check-ins, and the absence of early feedback allows small misunderstandings to harden into habits.

Document the work before the role is filled

A job description usually describes the person the business hopes to find. It rarely describes the work the person will do. Before recruiting, a manager should be able to set out the core workflow: what comes in, what decisions are made, who receives the output, which tools are used and what standard applies. A one-page process map and a short list of decision rights are often enough. The exercise also tests whether the role is properly defined.

If no one can explain the workflow, the hire will spend months discovering it. Documenting the work first gives the new starter a defined shape of work to inherit rather than a vague mandate to figure it out. It also exposes dependencies on a single experienced person, which is useful information for the business regardless of the hire.

A 30/60/90 plan with visible deliverables

A useful onboarding plan is not a calendar of introductions. It is a sequence of stages, each with a concrete output and a named person responsible for support. The plan should be written before the start date and reviewed with the new starter in the first week.

  • First 30 days: learn the core workflow, complete a small piece of real work, meet the people the role depends on and identify where the process creates friction.
  • Days 30 to 60: own routine tasks end to end, deliver a defined output and make decisions within agreed limits.
  • Days 60 to 90: operate across the full scope of the role, be measured against the outcomes the role exists to produce and propose at least one improvement to the workflow.

Each stage needs a named buddy for day-to-day questions and a manager checkpoint at the end of it. The checkpoint should ask what has been delivered, what is blocked and what support is needed. Progress becomes visible rather than assumed, and the plan can be adjusted without waiting for a formal review.

Track ramp time and first-year retention

Time-to-productivity should be defined by role and agreed in advance. In general terms, it is the elapsed time between the start date and the point at which the hire meets the agreed output standard without close supervision. That definition will differ between functions, but it can still be recorded consistently and reviewed at the end of the first ninety days and again after six months.

First-year retention belongs beside it. Early attrition is expensive because it repeats the recruitment cost and the ramp cost, and it frequently signals an unstructured first ninety days rather than a poor hiring decision. Tracking departures in the first year, and the reasons behind them, gives managers evidence about whether the problem sits in selection or in the environment the new starter entered.

These measures should be reviewed alongside recruitment cost, not in isolation. A low recruitment fee followed by a long ramp and an early exit is not a cheap hire. A higher initial spend that produces a productive starter and a settled team member may be the better return. Managers remain accountable for their hires, but they should be supported by a standard process rather than left to invent one.

Onboarding is not an administrative event or a welcome. It is the process by which a business converts a salary cost into capacity. The businesses that get a return on hiring treat it as designed, owned and measured. The gap is rarely a verdict on the new hire. It is a gap in the operating system around the role, and closing it requires clear work, named ownership, staged deliverables and metrics that make the ramp visible.

← PreviousBack to Articles