Employee Orientation

The words are used interchangeably and describe different work.

Onboarding is the administrative process of turning a hire into an employee: contract, identity and bank details, payroll setup, statutory registrations, equipment, access and accounts. It has a completion state, and it either happened or it did not.

Orientation is the process of a person coming to understand where they are: what the organisation does, how it works, who the people are, what their role actually involves, and what good performance looks like. It has no clean completion state and it happens whether or not anyone designs it.

Organisations conflate the two and then measure the one that is measurable. A joiner whose accounts were provisioned on day one and who spent the first week unsure what they were meant to be doing has been onboarded and not oriented, and the onboarding report will show green.

Keeping them separate in the design is what prevents that.

The first week is read as evidence about the organisation, and joiners are right to read it that way.

Someone arriving to find no desk, no equipment, a manager on leave and nothing scheduled learns something true: that their arrival was not planned for, and that this is a place where things are not planned for. That conclusion is formed quickly, is broadly accurate, and takes months of contrary evidence to revise.

The converse is equally strong. An arrival that was clearly prepared for, with the equipment ready, the first conversations scheduled and someone expecting them, communicates competence more convincingly than any statement about culture.

This is why the first week rewards attention out of proportion to its length. The cost is a few hours of preparation and the return is the joiner's baseline assumption about how the organisation operates.

It also has a direct effect on early attrition. A meaningful share of first-year departures are decided upon far earlier than they are acted on, and the first weeks are where the decision starts forming.

The standard design compresses everything into the first day or two: policies, systems, the organisation chart, the strategy, compliance training, benefits, and a sequence of introductions to people whose names are gone by lunchtime.

Very little of this is retained, for a straightforward reason. Information is retained when it attaches to something, and on day one there is nothing to attach it to. A policy about expense claims means nothing until there is an expense to claim, and an organisation chart means nothing until the names have faces and the teams have relevance.

Spacing the same content across the first weeks costs no more and works considerably better, because each piece arrives closer to the point at which it is needed.

Whatever else is arranged, the single largest factor in how a joiner settles is the attention of their direct manager in the first days.

This is the part most often delegated to HR, to a buddy or to a checklist, generally because the manager is busy. The delegation is understandable and it does not work, because the questions a joiner most needs answered are ones only the manager can answer: what am I actually here to do, what does good look like, what should I prioritise, and how will I know if I am doing it right.

A manager who spends unhurried time on those questions in the first week saves considerably more time later, and a manager who is absent for it will spend the following months correcting a direction that was never set.

The practical minimum is a proper conversation on the first day, a short check-in daily for the first week, and a longer one at the end of it. None of this is elaborate and all of it is regularly skipped.

A buddy or peer contact is a genuine complement to this, because there are questions people will ask a peer and not a manager, particularly the ones that feel too basic to raise. It is not a substitute.

Orientation is designed for external joiners and several other groups need it just as much.

• Internal movers, who know the organisation and not the role, and who are commonly assumed to need nothing. A substantial internal move is a new job with familiar surroundings.
• Returners from long absence, where the team, the systems and the priorities may all have changed.
• People acquired through an acquisition, who are joining an organisation that did not recruit them and may not have decided what it wants from them.
• Anyone whose manager changes, since much of what a joiner learns in orientation is specific to a manager rather than to a company.
• Contract and temporary staff, who are frequently given access and nothing else, then judged on output.

The first of these is the most consequential. Failed internal moves are expensive, damaging to the individual and usually attributed to the person rather than to the absence of any transition support. Treating an internal move as a joining event addresses most of it.

The test worth applying is whether the person knows what they are meant to be doing and how it will be judged. Where they do not, orientation has not happened, regardless of what was completed.