Group onboarding: how to use a shared programme to bring 10 hires on together

Only 12% of employees strongly agree their organisation does a great job of onboarding new hires, according to Gallup. When a company hires four, six, or ten people in the same month, the usual response is to onboard each one in a private series of 1:1s — which repeats every conversation and hides who is falling behind. Running the intake as one cohort fixes both problems at once.

What is group onboarding, and when does it beat onboarding people one at a time?

Group onboarding is the practice of bringing everyone who joins in the same window through a shared programme, together, instead of running a private induction for each person.

The case for it is not softness — it is efficiency and visibility. A new starter's most common feeling in week one is "everyone else seems to know this and I don't", and that feeling is dissolved instantly by a peer three desks away who joined the same Monday and is just as unsure. A cohort also spreads the answering load: when one person asks where the expense policy lives, eight people get the answer, and the manager types it once. And it makes progress legible — five hires against the same 30/60/90 plan show you immediately which one has stopped moving.

Here is the position, and we will defend it: if hires start within a few weeks of each other, onboard them as a cohort, not as parallel 1:1s. The 1:1 model feels more personal but scales terribly — it multiplies the manager's time by the number of hires and gives each person a slightly different, slightly worse version of the same first fortnight. The exception is the genuine one-off: a single senior or solo hire with no peers starting near them, where a "cohort of one" adds ceremony with none of the peer benefit. Batch the starters you can; onboard the true singletons individually.

How do you structure a group onboarding programme?

Take a people lead called Tom at a 70-person fintech in Manchester who hires in monthly intakes of four to eight. His programme runs six weeks and has five moving parts.

1. One cohort per intake, with a pinned start-here plan. Everyone who joins in a given month goes into one space. The first thing they see is a pinned post: what the six weeks look like, who their buddy is, and the one thing to do today. No hunting through a wiki.
2. A 30/60/90-day goal per hire. Each person writes their own outcome for day 30, day 60, and day 90 — "ship a small fix to production", "run a customer call solo" — visible to them and to Tom, not to the whole cohort. This is the spine the rest hangs on.
3. A weekly check-in the whole group answers. Three questions, ninety seconds: what did you get done, what are you stuck on, what do you need from me. Tom reads them in one sitting and sees who is drifting before it becomes a problem.
4. Week-tied assignments, not a 40-tab document. Each week releases its own tasks — set up the dev environment, read the two docs that matter, pair with someone in support — as discrete items with a due date, rather than a monolithic onboarding doc nobody finishes.
5. A buddy and a private channel. Every hire is paired with someone outside their reporting line, and has a private 1:1 thread with Tom for the questions people won't ask in front of a group — about pay, about feeling behind, about whether the role is what they expected.

The structure is deliberately close to a coaching cohort, because a well-run onboarding is one. The same architecture we describe in structuring a coaching cohort from day one — a clear intake, week-one rituals, individual goals, a mid-programme review — maps almost directly onto a new-hire group.

How do you stop the cohort becoming a silent broadcast channel?

The failure mode of any group onboarding is a feed the manager posts into and nobody answers.

The fix is structure, not encouragement. A weekly check-in that expects a reply from each person turns the group from a noticeboard into a rhythm — and because each check-in is a specific, closed question rather than "how's it going?", people actually answer it. Keep individual progress private to the hire and the manager: a new starter will admit they are stuck on something basic in a 1:1 thread long before they will confess it to nine peers. The public part of the cohort should be for shared wins and shared questions; the honest, wobbly parts belong in private.

One more rule earns its place: give the cohort a finish. An onboarding group that never ends drifts into a general team chat and loses its shape. When the six weeks close, graduate the cohort out with a short review of each person's 30/60/90 progress, and let the next intake start clean.

How does Bitir run a new-hire cohort?

In Bitir, an intake is one private group with the whole programme built in.

The pinned "Start here" post sits at the top of the feed. Each hire's 30/60/90 goal lives in the goals widget, visible to them and their manager only. The weekly check-in recurs automatically and gives the manager a per-person view, so a hire who goes quiet surfaces within a week rather than at a probation review. Week-tied work goes out as assignments with due dates, and the private 1:1 channel handles everything a new starter won't say in public. A buddy can be added as a helper with a narrow set of extra rights through the role editor, without handing them manager-level control. Run one group per monthly intake, close it at six weeks, and the whole thing is repeatable rather than reinvented each time.

Related reading: how a London startup ran its new-hire cohorts as one coached group, and how a Bristol firm replaced monthly 360s with weekly check-ins for new managers.