Induction usually means a day of policies and a stack of logins. The part that decides how quickly somebody becomes useful — how the work is actually done here — is the part left to osmosis.
Induction training is what a new person is taught in their first days: the organisation, the safety and compliance essentials, and the specifics of doing their job here. It sits alongside the administrative side of joining — accounts, equipment, paperwork — which is a checklist rather than training and is covered in employee onboarding checklist.
The distinction matters because the two get merged and then the training half loses. A first day spent on policy documents and account setup feels productive and teaches almost nothing about the work. The questions a new person actually has — how does a job get quoted here, who decides this, what happens when a customer complains — are answered over the following three months by interrupting colleagues.
Spread induction over weeks rather than concentrating it in one day. A single day of everything produces retention of almost nothing — the material has no context to attach to yet. The same content across the first month, with real work in between, is remembered because each piece answers a question the person has now actually encountered.
The single highest-return induction artefact for a small business is a short page describing how work actually flows through the business — not the org chart, the work. Who it comes from, what happens to it, who decides what, where it ends. It takes an afternoon to write, it is the thing every new person reconstructs slowly and expensively, and it is equally useful to the people who have been there five years, which is how you find out that two of them believed different things.
Ettex Docs holds the induction plan and the how-work-flows page where they can be edited as reality changes, with the procedures behind them in standard operating procedure. The record of what was covered belongs in Ettex Records, and the administrative checklist in employee onboarding checklist.
To be clear: no learning management system, no e-learning modules, no automated onboarding sequences. Induction at small scale is a written plan, a named buddy and somebody checking in — and the reason it usually fails is none of those three, not the absence of software.
Onboarding is the whole process of joining, including administration. Induction training is the teaching part — the organisation, the compliance essentials and how the job is done here.
Spread it across the first month rather than concentrating it in one day. A single day of everything is retained poorly because nothing has context yet.
How work actually flows through the business end to end, and who to ask about what. Both are learned slowly by interrupting colleagues if nobody teaches them.
Yes — something small and low-risk. Doing teaches faster than watching, and a week of observation demoralises more than it prepares.
Version control is not about keeping every draft. It is about there being exactly one current document, and everyone knowing which it is — which is why final_v3_REVISED is a symptom rather than a naming problem.
A document sent to five people for review comes back with five sets of contradictory notes and no decision. The fix is not better reviewers — it is saying what kind of review you want before sending.
Everyone agrees backups matter and almost nobody checks that theirs work. The gap between having a backup and being able to restore is where most data loss actually happens.