Onboarding as a shared team campaign, not a checklist

There is nothing wrong with checklists. Account created, laptop shipped, benefits explained, first one-to-one booked. Those things must happen, and a list is the honest way to make sure they do.

But every item on that list points at the organization. The new joiner is the object of the process, not a participant in it. Belonging comes from the opposite motion: doing something alongside people, repeatedly, at low cost, until the group feels familiar.

A campaign is better shaped for that second job. It has a bounded duration, a shared number, and a reason for existing teammates to interact with a new person that is not another introduction call. In month one, both of those are worth more than a well-designed welcome deck.

The actions should be things a new joiner can genuinely do in week one, and things an existing teammate can do too, so participation is not a new-hire performance review. For example:

• Ask one question in a public channel: +10
• Have a coffee with someone outside your team: +15
• Read one internal doc and post what confused you: +10
• Thank a teammate in the channel: +2
• Take a walk away from the desk: +5

The second item in that list is the one people skip and the one that matters most. New joiners meet their own team easily and the rest of the company barely at all. A campaign that makes cross-team contact a counted action removes the awkwardness of asking a stranger for twenty minutes.

Having existing teammates log the same actions changes the texture. The new joiner is not completing an onboarding module, they are taking part in what the team is doing this month. That is the whole difference between a campaign and an induction checklist.

Thirty days is the right length. It covers the period when a new joiner is most unsure, it is short enough that a cohort can see the end, and it gives the whole team a reason to keep the channel warm through a month that otherwise drifts.

The goal should measure the team, not the cohort. If every new joiner is expected to add a set amount, the campaign becomes an assessment of them. If the target belongs to the group, a quiet week is a team problem and nobody has failed as an individual.

Assign no individual target and no individual report. This is the part that gets quietly reintroduced by well-meaning managers, and it undoes the design. The moment a new joiner learns their numbers are being looked at, the actions they log stop being honest.

Onboarding touches the most sensitive period in someone's time at a company. Track the campaign, not the person:

• No per-person report shared with managers or used in reviews.
• No productivity or response-time metrics attached to the campaign.
• No storing of message text or photos. Hepio keeps neither.
• No streak that resets and no penalty for a week of silence.
• No leaderboard, including a private one shown only to managers.

The last rule is the one that meets pushback, usually with good intentions: “we just want to know who is struggling.” A campaign is the wrong instrument for that. If someone is struggling, a channel where their name sits next to a low score is the last place they will say so. The right instrument is a manager conversation, which the campaign should not pretend to replace.

Opt-in applies to onboarding too, which surprises people. A new joiner is under pressure to accept everything, so the invitation has to be genuinely easy to decline, and someone who declines must not appear in any list afterwards.

None of this replaces the handbook, the access requests or the 30-60-90 plan. Those are documents with owners and deadlines, and a campaign is a bad document. Keep the checklist for the things that must be true and use the campaign for the things that must be felt.

In practice the two sit next to each other. The checklist lives where it already lives, in the onboarding doc or the HR system. The campaign lives in a channel the team already reads, with one shared goal for the cohort's first thirty days and a final message naming what the team did together.

The handover is worth designing. The last week of the campaign should point at what comes next, usually a normal team rhythm rather than a second campaign. One that ends cleanly teaches the team that shared goals are a temporary, low-cost thing you can repeat. One that fizzles teaches them to ignore the next invitation.