Most onboarding doesn't fail dramatically. It just varies. Ask two people who joined a month apart what they were shown in their first week and you'll usually get two noticeably different answers — which means the process depends on who happened to be free rather than on any design.
Slack is a good place to fix that, for one unglamorous reason: it's the tool a new hire definitely has access to on day one, often before their laptop is fully set up and almost always before they have logins for anything else.
Why day-one front-loading fails
The standard shape of onboarding is a very heavy first day followed by nothing. It's the worst possible distribution.
On day one a new hire is meeting people, finding the bathroom, working out whether they've made a terrible mistake, and being handed a laptop. Almost nothing said to them is retained. Meanwhile everything they'll actually need in week three — the expense policy, the deployment process, how support escalations work — arrives when it's least useful and is gone by the time it matters.
Spreading the same material across the first two or three weeks costs nothing and works substantially better, because each piece arrives closer to when it becomes relevant.
Sequence it, don't dump it
The practical version is a sequence of short modules, one every day or two, in a deliberate order:
- Days 1–2: what the company does, how the team is organised, who to ask about what. Orientation, not detail.
- Days 3–5: the tools and processes they'll touch first. Just enough to be useful in week one.
- Week 2: policies — expenses, time off, security, code of conduct. These need to be recorded as completed, because some of them are compliance obligations.
- Week 3: the deeper role-specific material that would have been meaningless earlier.
Each module short enough to finish between other things. The point is that it arrives, rather than sitting in a portal waiting to be discovered.
Assign to future hires, not to people
This is the change that removes the variance, and it's the one most teams miss.
If onboarding is assigned by adding individuals to a course, someone has to remember to do it every time. That works until it's a busy week, and then a new hire silently gets nothing.
Assigning to everyone who joins from a date forward inverts it. The process runs whether or not anyone remembers, and a person who joins during a chaotic month gets the same onboarding as one who joins during a quiet one.
In Poplearn, /assign #general sends a course to a channel or to every new hire from that point on, with reminders included, so enrolment stops being a task anyone owns.
Track it without chasing
Chasing completion is unpleasant for everyone, and managers avoid it, which is why it doesn't happen.
The alternative is making the number visible rather than enforced. When a team lead can see that two of their five new hires haven't finished the security module, they'll usually handle it themselves — a quick message, no escalation, no HR involvement. That only works if the number is somewhere they already look rather than in a report.
/progress returns live completion by team and exports on demand, which also covers the compliance case: when someone asks whether a specific person completed a specific policy and when, you produce a record rather than a search.
Keep the human parts human
Worth saying plainly, because it's easy to over-automate: a sequence of modules is not onboarding on its own.
Introductions, a buddy or first-week partner, a manager check-in at the end of week one, and someone to ask stupid questions without embarrassment — none of that is replaceable by content, and all of it matters more than the modules do. Automating the material is valuable precisely because it frees up attention for the parts that need a person.
Getting started
If you already have an onboarding doc, most of the work is done. The gap is usually structural rather than editorial — the content is fine, it's just shaped for reading rather than for finishing.
Poplearn handles the reshaping. Paste in the document, and it splits the material into modules and writes the quizzes. Assign it to everyone who joins from here on, and it runs without anyone maintaining it. Free under 20 seats, installs in about a minute.
