Onboarding is knowledge transfer, not orientation

Policies can be read. How things actually work cannot.

Most onboarding covers what can be documented: policies, systems, structure, compliance modules. All of it is necessary and none of it is what a new person needs to become effective, which is the undocumented knowledge of how the organisation actually operates.

That knowledge is things like who to ask about what, which processes are enforced and which are nominal, what the unwritten priorities are, and which relationships matter. It transfers through working alongside people, which means onboarding is largely a scheduling problem rather than a content problem.

A useful structure is to name the ten people the new starter needs to know and arrange a short conversation with each in the first fortnight, with a stated purpose. That does more than any induction programme and it costs the organisation a few hours in total.

The other high-value item is a real task, early, with support. People calibrate their own competence by doing something, and a first month spent reading produces somebody who still does not know whether they can do the job.

The other transfer that matters is context about the role's history. A new person walking into a role that was vacant for months, or held by somebody who left badly, is inheriting a situation nobody has described to them, and they will read the resulting difficulty as a reflection of their own performance.