Induction tells; onboarding proves

Induction tells. Onboarding proves.

Why organisations confuse an event with an experience, and what the first ninety days are actually for Ask an organisation about its onboarding and watch what gets described.

Day one, usually in loving detail. The welcome session. The culture deck, possibly with the CEO video. The compliance modules, the systems access, the lanyard, the tour that ends at the good coffee machine. Sometimes a welcome pack with a branded water bottle in it.

Then ask what happens in week three. Or week seven. Or day sixty, when the new starter has stopped being new enough for anyone to check on and hasn’t yet been there long enough to have anyone to tell.

The answer, almost everywhere, is a slightly puzzled pause, followed by some version of:

“well, by then they’re settling in.”

That pause is this week’s perspective. Because what it reveals is a confusion so complete that most organisations no longer notice they’re making it: they have mistaken induction for onboarding, an event for an experience, and in doing so they’ve left the most decisive ninety days of the employment relationship almost entirely undesigned.

Two words, two different jobs Let me draw the line cleanly, because the words get used interchangeably and the interchangeability is where the problem hides.

Induction is an event. Its job is transmission: here is the organisation, here is what you must know, sign, and complete. It’s institutional, it’s largely one-directional, and it’s finished when the checklist is finished, usually within the first week. Induction is genuinely necessary. Some of it is legally necessary. Nothing in this essay argues against running an excellent one.

Onboarding is an experience. Its job is not transmission but verification: this is the period in which every promise made during the hiring process gets checked against reality by the one person in the building who still remembers exactly what was promised. It runs for roughly ninety days, it happens whether anyone designs it or not, and it is never “complete” in a system, because its outcome isn’t a checklist. Its outcome is a verdict.

The confusion between the two isn’t an accident of vocabulary. It happens because induction is legible in all the ways organisations like: it has an owner (usually HR or L&D), a budget, a schedule, and a completion metric. Onboarding, properly understood, has none of those things by default. So the legible thing absorbs the name, the reporting, and the attention, and the decisive thing gets a folk label: settling in.

Settling in is not a program. It’s an absence of one.

What the ninety days look like from the other side Regular readers will recognise the person walking through the door on day one, because we followed them here two essays ago: through the offer-to-start window, past the silence and the counter-offer, still holding the promise they signed for. The window was where they decided whether to believe you enough to arrive. The first ninety days are where they decide whether they were right.

And consider their evidentiary position. This person carries a complete, high-resolution record of everything that was said: the job ad’s version of the role, the interviewer’s version of the team, the hiring manager’s version of the support, the offer conversation’s version of the future. Nobody else in the organisation holds that record. Long-tenured people have long since blended what was promised with what turned out to be true. The new starter is the only person conducting a live, line-by-line audit of your promises, and they conduct it involuntarily, every day, with everything they see.

The laptop that arrives on day three isn’t an IT hiccup to this auditor. It’s an exhibit. The manager who was warm and attentive at interview and is now in back-to-back meetings until Thursday isn’t just busy. He’s evidence about which version of him was real. The “structured development pathway” that turns out to be a portal login. The “collaborative team” that turns out to eat lunch at their desks in silence. Each item small, each explainable, and each one landing in the same ledger, on one side or the other.

Two essays in this series meet here. The new starter is simultaneously running the culture fieldwork we covered in the fortnight essay (watching what happens to the first person who challenges something in a meeting) and the promise audit that began at the careers page.

The first fortnight teaches them how this place really works. The first ninety days teach them whether this place tells the truth. Culture answers the first question. Onboarding answers the second, and it’s the second one that decides whether they’re still here at month thirteen.

Because here’s the reframe that changes how the number reads: first-year turnover is not really a retention metric. It’s a promise metric. It counts the people who completed the audit, compared what was said with what was lived, and chose the evidence. When a first-year leaver is asked why, they’ll usually offer something polite about fit or opportunity. The real answer, far more often than exit data will ever show, is simpler: the ninety days returned a verdict, and the verdict was against you.

Who owns the proving If onboarding is the keeping of promises rather than the transmitting of information, then the question of ownership answers itself, and the answer indicts the standard model.

Induction can be owned centrally, and should be. But the promises being audited in the first ninety days were not made by HR. The role was described by a hiring manager. The team was characterised by the people in the interviews. The support was pledged by the person the new starter now reports to. The keeping of those promises can only happen where they were made: locally, in the team, by the manager.

Which means the standard handover, where recruitment closes the file and “onboarding”

becomes an HR workflow of scheduled emails, is a structural promise-break waiting to happen. The person who made the promises exits the process at the exact moment the promises come due. Next week’s essay is entirely about this channel problem, because it’s bigger than onboarding, but here’s the onboarding-sized version: the manager isn’t a stakeholder in onboarding. The manager is the onboarding. Everything else is logistics.

The best designed first-ninety-days I’ve seen share a short list of features, none of them expensive. The practical readiness is flawless, because day-one friction is the cheapest promise to keep and the most corrosive to break: the laptop works, the roster is right, someone is expecting them. The manager’s calendar is pre-cleared, not just for day one but with standing time across the whole ninety days, because attention is the promise underneath all the other promises. There’s a designed early win: a real contribution, scoped to be achievable inside the first month, because “you’ll do meaningful work here” is a promise too, and it’s provable. There’s a person who isn’t the manager (call them a buddy, though the label matters less than the permission) whose job is to answer the questions the new starter thinks are too small to ask. And somewhere around day thirty and day ninety, someone asks the audit question directly: “What’s been different from what you expected?”

Asked sincerely, that one question surfaces every gap while it’s still closable, and signals the rarest thing an organisation can signal: that it wants to know how its promises are landing.

Notice what’s absent from that list: content. No additional modules, no expanded deck. The ninety days aren’t a communication problem. They’re a delivery problem.

The counterargument: isn’t this overkill?

Here’s the pushback, and it has two respectable versions.

Version one: “People are adults. We hired capable professionals; they don’t need ninety days of choreography. Over-designed onboarding infantilises exactly the self-starters we want.” Version two, the operational one: “This is a resourcing fantasy. Our managers are stretched as it is; a frontline coordinator with a span of twenty can’t run bespoke ninety-day journeys.”

Both deserve straight answers.

To the first: agreed, and note what was actually proposed. Nothing above choreographs the new starter. Every element disciplines the organisation: keep the practical promises, protect the manager’s attention, provide a real piece of work, ask how it’s going. That’s not hand-holding. That’s the employer doing what it said it would do, which is the opposite of infantilising; it’s the baseline of a professional relationship. Capable people don’t resent kept promises. They resent being sold one workplace and delivered another, and capable people, having options, act on that resentment fastest.

To the second: the resourcing objection is real, and it’s pointing at the actual root cause rather than refuting the argument. If a manager’s span and load make ninety days of basic attention impossible, then the organisation has made a structural decision that its promises will be broken at scale, and no onboarding program, thick or thin, fixes a design choice.

That’s not a reason to abandon the ninety days. It’s the strongest reason to treat manager conditions as the true onboarding budget. More on that next week, because it’s the essay after this one in more ways than the calendar.

And if the cost still feels high, price the alternative. A first-year departure means the full acquisition cost written off, the vacancy re-run, the team re-strained, and one more trained auditor released into the market with a completed verdict and a review to write. Against that, pre-clearing a calendar and asking two sincere questions is not a program cost. It’s rounding error with a compounding return.

What to do with this on Monday

Separate the words in your own reporting. One line change: induction completion is a compliance metric; onboarding gets measured at day ninety, by the new starter’s answer to “did we match what we promised?” What gets named differently gets managed differently.

Run the expectation audit at day thirty. One question, asked by the manager, in person:

“What’s been different from what you expected?” Write the answers down across ten starters and you’ll have a ranked list of your most-broken promises, free.

Fix day-one friction permanently. Whatever failed for the last three starters (equipment, access, rosters, nobody expecting them), assign it an owner this week. It’s the cheapest promise in the building.

Pre-clear the manager’s first fortnight before the start date is confirmed. If the manager genuinely cannot make the time, the honest options are to change the start date or change the promise. Delivering absence while advertising support is choosing the gap.

Design one early win per role type. A real, scoped, month-one contribution. It converts “meaningful work” from a pillar into an experience, and it gives the day-ninety conversation its best possible exhibit.

The sentence to keep

Induction tells. Onboarding proves.

The deck says who you claim to be. The ninety days demonstrate it, to a full-time auditor with a perfect record of your promises and a decision still open. Most organisations put their effort into the telling and leave the proving to chance, then read the first-year turnover number as a mystery.

It was never a mystery. It was a verdict.

Next week, the channel all of this travels through, and the most consequential single fact in employee experience: people don’t experience your organisation. They experience their manager.

If you can still remember your own first ninety days somewhere, and the moment the audit returned its verdict, either way, I’d like to hear it. Reply or comment. The proving stories are always sharper than the telling ones.

Shehzad Bhanji writes The Promise Gap, a weekly perspective on the relationship between organisational promises and lived experiences. Across a 25-year international career spanning marketing, customer experience, employer brand, HR technology and people experience, he has worked across Australia, Asia, Europe, the Middle East and Africa.