Induction programme ideas for large intakes

Most large-intake inductions are built the same way: a room, a projector, a parade of directors explaining how excited they are, and a compliance block after lunch when the room is at its least alert. By Wednesday the cohort can recite the values and cannot name a single person they would ask for help.

Everything on the welcome deck is on the intranet by Friday anyway. What is not on the intranet is permission: to ask the obvious question, to say a process looks daft, to message someone three levels up without drafting it four times. Manufacturing that permission is the actual job, which is why the format of an induction matters more than its content.

What an induction programme has to do

Three jobs, and only three. Test every session in your agenda against them.

• Orientation. Not the org chart. The real route a piece of work takes, and who touches it on the way.
• Connection. Not the CEO. The eight people they will actually email in week two, and what each one is for.
• Permission. The first question asked out loud in a cohort sets the ceiling for the year. Engineer an early one that gets a straight answer. Psychological safety is built in the first hour or apologised for later.

If a session serves none of the three, it is filler. Cut it and give the time back as a longer lunch, which at least builds connection.

Eight induction activities that survive a big room

Each of these works from a cohort of roughly twenty upwards and scales by adding teams rather than by changing the activity. Every one ends with a question, because an activity without a debrief is entertainment with a training budget attached.

1. The real route map. Teams of six, forty minutes. Give each team one real thing your organisation does for a customer, from first request to delivery, and have them draw how it moves and who touches it. Then bring in someone who does that work daily and let them correct the map in front of everyone. Debrief question: which handover on your map had no name against it, and who is going to find out?
2. Question amnesty. In the first hour, everyone submits questions anonymously. At the end of day one someone senior answers the twenty most common, unedited, including the awkward ones about pay bands and the state of the tooling. Debrief question: which answer would you never have got by reading anything we sent you?
3. The failure archive. Someone senior tells three real things that went wrong, what each cost, and what changed afterwards. Then teams are given five decisions the company genuinely faced and vote on which one was taken. Twenty-five minutes. Nothing teaches a culture faster than what it forgives. Debrief question: based on what you just heard, what happens here if you make a mistake in week three?
4. Rotating tables, not an executive parade. Seven minutes a table, groups of eight, hosted by the people new joiners will depend on: payroll, IT, whoever approves expenses, the team they hand work to. Each host answers one question rather than presenting: what do people get wrong when they come to me? Debrief question: who will you contact first, and about what?
5. A cohort-wide game. One story, every team playing it at once on their own phones, with a facilitator controlling the pace from the front. This is the format we build most often, and the reason it works at 200 people is that it is hybrid: puzzles and decisions in the app, physical challenges run by facilitators away from the screen, and nothing unlocks until a team has actually solved something. Debrief question: what did your team do when it did not know the answer?
6. The scavenger hunt, done properly. The default version is a photo competition with a winner and no residue. Make every item require a named human: a document only one team can point you at, a machine only one person may touch. Teams of five, forty-five minutes. Debrief question: which item did you get by asking rather than searching, and what else did that person tell you?
7. One real small thing, finished. Day two afternoon, in pairs: a genuine ticket, a real customer complaint, a live spreadsheet that needs checking. Real work, small enough to finish, with someone available to unblock them. Nothing signals belonging like having shipped something in week one. Debrief question: what stopped you, and how long did it take to find someone who could help?
8. The thirty-day contract. Final session. Each joiner writes one page: what I will understand by day thirty, what I will own, what I need from my manager. Their manager countersigns it that week. The cheapest item here, and the one that most reliably survives contact with the following month. Pair it with a manager-side plan for the first ninety days.

Which one to run: a chooser

Ranking individuals on day two tells your quietest new joiners exactly where they stand before anyone knows their name. Score teams, or do not score at all.

What each mechanic actually rewards

If you are going to gamify an induction, be precise about what the mechanic pays people for. A cohort works that out inside ten minutes and optimises accordingly.

• Points for activity. Rewards completion. You will get completion, and no evidence that anybody thought about anything.
• Individual leaderboards. Reward the already-confident and the fast typist. On day two, in a cohort where half the room is still deciding whether it belongs, the bottom half of a public ranking is an expensive way to make people quiet.
• Countdown timers. Reward speed over judgment. Useful when the skill genuinely is speed. Corrosive when you have just told everyone to ask before assuming.
• Badges and streaks. Reward attendance and punish annual leave. Harmless, forgettable, mildly patronising to senior hires.
• Quiz accuracy. Checks recall. Fine for facts you must evidence, such as fire drills and data handling. It tells you nothing about whether someone will escalate a problem.
• Team scoring on reasoning. Rewards the thing you actually want, and produces something a facilitator can use in the debrief. It costs more, because a human or a well-built rubric has to judge the reasoning rather than tick an answer.
• Unlock by solving. Rewards persistence and forces genuine collaboration, because nothing progresses until the group cracks it. Our own induction games use this in place of timers: solve the puzzle, earn the passcode, unlock the next level.

The mechanics are not the design. They are the last decision, made after you know what behaviour you want to see. That order is the whole argument behind bespoke gamified learning apps: the objective picks the mechanic, never the other way round.

When gamifying an induction makes it worse

We build these for a living and still talk clients out of them. Five cases where a game is the wrong instrument:

1. The content is compliance. If you need evidence that 200 people read a policy, you need a record, not a narrative. Gamifying it adds cost and a legal argument you do not want.
2. Nobody will facilitate it. A game with no facilitator and no debrief is a quiz with better graphics. The activity generates the evidence; the conversation afterwards is where behaviour changes.
3. The cohort is very mixed. A group spanning graduates and senior lateral hires, or several first languages, will not be measured fairly by any scoring system you can build in a fortnight. Use team formats and drop the ranking.
4. The story flatters the company. New joiners are excellent detectors of a game whose plot is that the organisation is wonderful. A reveal only lands if the middle was honest.
5. The intake is under a dozen. Below that, a good facilitator with a whiteboard and three real questions beats software every time, and costs nothing.

A two-day shape that holds up

1. Day one, morning. Fifteen minutes of logistics, question amnesty opens, then straight into the real route map. Work before welcome.
2. Day one, late morning. Rotating tables. Names and faces attached to problems, while people still have the energy to talk to strangers.
3. Day one, afternoon. The cohort-wide game, or the failure archive if the budget is thin. This is the piece they describe to their friends.
4. Day one, close. The amnesty answers, live and unedited. Ending on straight answers is the single strongest signal you can send on day one.
5. Day two, morning. Compliance, in one honest block, clearly labelled as the boring necessary part. Do not disguise it as a game.
6. Day two, afternoon. One real small thing, finished, then the thirty-day contract. People leave having done work, not watched it.

Two things to cut on sight: the welcome video that no one has watched twice, and the icebreaker that asks people to disclose something personal to strangers on day one. If you want the room warm, use questions about work with a low cost of answering. Ours are here, and the generator will give you a fresh one in a second.

One last principle. An induction is not information transfer, it is the moment a person decides how this place works and how much of themselves to bring to it. Design it as an experience with a conversation at the end, and it survives the year. That is the whole of experiential learning, applied to the one week when everybody is paying attention.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning appsThe Weekly Challenge to see the method in ten minutes.