Key takeaways
- The first week is the strongest signal anybody will ever get about what it is like to work here. Most organisations spend it on policy modules.
- Onboarding research names four jobs: compliance, clarification, culture and connection. Nearly all of them do the first one, because it is the only one a completion report can see.
- Nobody should spend their first five days at a computer. The work is learned in the work, and belonging is built at a table.
- Build it as a recipe. What happens before day one, on day one, in week one, across the first month, then at 30, 60 and 90 days.
- Every ingredient has to do a job. If you cannot say which job, take it out.
Here is how most inductions get made. Somebody takes the induction manual, converts it to slides, adds a quiz at the end, and loads it into the LMS. The content is accurate. The branding is correct. A new starter clicks through it on their first morning and the system records a completion.
That is a filing cabinet with a play button.
An induction is the one learning experience where the emotional job outranks the informational one. Somebody has just resigned from a job, told their family, and turned up hoping they made the right call. What you do in that first week decides whether they relax into the place or start quietly reading job ads again.
What an induction is for
Talya Bauer’s work for the SHRM Foundation names four jobs an induction has to do. It is the most useful frame we have found for designing one.
- Compliance. The rules, the paperwork, the things that are legally or operationally non-negotiable.
- Clarification. What the job is, what good looks like, and by when.
- Culture. How things work here in practice, including what people do when it gets hard.
- Connection. The humans. Who to ask, who to trust, where you fit.
Nearly every induction we are asked to fix does the first job thoroughly and the other three by accident. That is not laziness, it is measurement. Compliance is the only one of the four that an LMS can prove, so it is the only one that gets built.
The design consequence is the whole article: each of the four jobs needs a different kind of experience. You cannot build connection through a module, and you cannot build compliance through a coffee.
The first five days are not for a computer
The most common induction we see is eleven modules in week one. Code of conduct, privacy, safety, systems, values, cyber, harassment, records, quality, procurement, and one on the induction itself.
Think about what that asks of somebody. They are in a new building, with new names, a new commute, a new manager and a new laptop they cannot log into. Working memory is already at its ceiling before anybody presses play. Load forty minutes of policy on top and little of it lands, so it gets loaded again next year, and the year after.
It also says something. Left alone at a desk, in a room where everybody else knows each other, is a message about how much you were expected.
The fix is not less compliance. It is compliance in its right place: short, spaced across the first month, and delivered close to the moment it matters. Manual handling lands the week somebody starts lifting.
The ingredients
Think of induction as a pantry rather than a course. Six kinds of ingredient, and each one carries the reason it earns its place.
People. A human first hour, because the first impression is social and a portal cannot make somebody feel expected. Lunch with the team, because belonging is built at a table and it is the cheapest ingredient here. A buddy with an actual script, because “look after them” is not an instruction, and three named things to do beats goodwill. Three people to find in week one, because a named task makes networking possible for somebody who finds it hard.
The work. An on-the-job guide their supervisor teaches from, because the work is learned in the work. A field guide also turns a good operator into a consistent teacher. Practise the real task, watched and then unwatched, because demonstration is the only honest evidence somebody can do the job. A sandbox with real tasks in it, because clicking through a system demo teaches the interface while doing a real task teaches the job.
Clarity. What to expect on day one, sent before day one, because uncertainty is the first thing you can remove for free. A one-page job aid for the first fortnight, because new starters ask the same nine questions and you can answer them on paper. A picture of what good looks like at 30, 60 and 90 days, because nobody can aim at a target that was never described.
Culture. The story of why the place exists, told by somebody who lives it rather than a slide with three values on it. What we do when it gets hard, in real examples, because that is what culture is. Then ask the new starter what confused them, because your newest people are the only ones who can still see your induction clearly.
Compliance. Only what cannot wait, short and spaced. Everything else moves to the month, and the safety induction happens where the hazards are, not in a room with a projector.
The manager. A conversation on day one, in week two, and at each of the 30, 60 and 90 day marks. Write the prompts for them. Week two is when the first doubts arrive, and it is the cheapest retention move available to you.
The recipe
Ingredients do not make a meal. This is the order we build them in.
| When | What happens | Why it is there |
|---|---|---|
| Before day one | A welcome from a person, what to expect, paperwork done online | Removes uncertainty and clears day one for people |
| Day one | First hour with a human, a walk around the place, lunch with the team, the why of the organisation, and a real conversation with their manager | First impressions are social. Expectations get set now, or by rumour |
| Week one | The on-the-job guide, a buddy working to a brief, three people to meet, a one-page job aid, only the compliance that cannot wait | The work is learned in the work, with just enough scaffolding to be useful |
| Weeks two to four | Practise watched then unwatched, a sandbox with real tasks, short retrieval check-ins, the week-two manager conversation | Practice and spacing are what make week one survive |
| Day 30, 60 and 90 | A capability conversation against the job, a demonstration signed off by somebody who can judge it, ask what was confusing, name the first win | Competence is observed, and recognition in the first ninety days is what makes somebody decide they belong |
Two things about that table. The online component is the smallest column, not the largest. And the manager appears in four of the five rows, which is why the manager prompts are usually the highest-yield thing we build.
Build your own recipe
Below is the recipe, as a tool. It starts with four buttons and five empty steps. Add a job and its ingredients land where they belong, coloured to match. Add all four and the recipe is complete, which is the fastest way to see what one job on its own leaves out.
Build your own
The induction recipe builder
An induction has four jobs to do. Add each one and watch the ingredients land where they belong. All four, and the recipe is complete.
No jobs added yet
Start anywhere. Connection is the one most inductions forget.
The icing on top
Once the recipe works, a few things make it memorable rather than merely competent.
A welcome kit somebody would keep, rather than branded tat. A first win, named out loud in front of other people, in the first fortnight. A wall, physical or digital, of what people here have done. An hour with somebody senior, where the new starter brings the question. A hand-written note at day ninety. A graduation moment, so the induction has an ending rather than fading out.
None of that is decoration. Distinctive moments are what a memory hangs on. How somebody feels at the end of an experience is most of what they will say about it later. Design the ending, or the ending will be the day their access finally worked.
What we would not do
- Eleven modules in week one.
- A values slide, in place of somebody explaining a hard call they made.
- A quiz as evidence of competence, when the job can be demonstrated.
- A buddy with no brief, no time allocated and no follow-up.
- An induction that ends on day five, when the doubts arrive in week two.
What this takes to build
Less than people expect, and in a different shape. The on-the-job guide and the manager prompts are usually the cheapest artefacts in the program, and the ones that move the most. They change what happens in the room rather than what sits on a server. The online component almost always gets smaller.
We have built inductions and onboarding programs for utilities, aid organisations, local government, insurance, construction and schools. So we have inherited plenty of filing cabinets. The pattern is consistent: the content is rarely the problem, and the sequence almost always is.
Talk to us about your induction
Send us your induction and the first-week schedule that goes with it. We will tell you which of the four jobs it does and which it misses. Then what we would move out of the LMS and into the room.
Talk to us, or read how we build learning campaigns that run past day five.
Frequently asked questions
Not by completions. Time to first independent task. A demonstration signed off at 30 and 90 days. The manager’s answer to “can they do the job yet”. And what your last three starters say confused them. All four are cheap to collect and all four tell you something a completion report cannot.
Sources
- Bauer, T. N. Onboarding New Employees: Maximizing Success. SHRM Foundation. The four Cs: compliance, clarification, culture and connection.
- Cepeda, N. J. and colleagues. Distributed practice in verbal recall tasks: a review and quantitative synthesis. On spacing.
- Roediger, H. L. and Karpicke, J. D. On retrieval practice, and why being asked to recall beats re-reading.
- Sweller, J. On cognitive load, and why a new starter’s working memory is full before you press play.
