Onboarding is where Poplearn fits most naturally, because the two things it does — converting existing documents and assigning to future joiners — map directly onto the two ways onboarding usually fails.
The two failures
Variance. Ask two people who joined a month apart what they were shown, and you'll usually get different answers. The process depends on who happened to be free rather than on any design.
The enrolment gap. If people are added to courses individually, someone has to remember every time. That works until a busy month, and then a new hire silently gets nothing — discovered months later, usually when someone asks about compliance coverage.
Setting it up
Convert what you have. /courses new takes your existing onboarding document — the handbook, the wiki page, the deck — and splits it into modules, writing the quizzes as it goes. You don't author anything.
If the document isn't in teaching order, reorder the modules after generation. Documents are often organised by topic or system; onboarding should be ordered by what someone needs first.
Assign to future joiners. This is the change that removes both failures at once. /assign targeting everyone who joins from that date forward means the sequence runs whether or not anyone noticed the person started, whether or not it was a busy week, and whether or not the person who normally handles onboarding is still at the company.
Let it deliver over time. Modules arrive as Slack direct messages one at a time rather than all at once, which matters more for onboarding than anywhere else.
Why day-one front-loading fails
The standard shape is a very heavy first day followed by nothing, which is the worst possible distribution.
On day one someone is meeting people, learning where things are, and working out whether they've made a mistake. Almost nothing said to them is retained. Meanwhile the expense policy and the deployment process — which they'll need in week three — arrive when they're least useful and are gone by the time they matter.
A workable sequence:
- Days 1–2: orientation. What the company does, how teams are organised, who to ask about what.
- Days 3–5: the tools and processes they'll touch first.
- Week 2: policies — expenses, time off, security, code of conduct. These usually carry compliance obligations, so the completion record matters.
- Week 3: role-specific depth that would have been noise earlier.
Why Slack specifically
Chat access is nearly always a new hire's first access — often before their laptop is fully set up, and almost always before an LMS account exists.
That provisioning gap is real and invisible in most process documentation. The LMS account gets created on day three, so onboarding, the thing most sensitive to timing, is the last system to become available.
Delivering in Slack removes it. There's also no new interface to learn during the week someone is already learning several.
Tracking without chasing
/progress returns live completion by team, exportable on demand.
For onboarding the useful view is per-person: a manager seeing that their new hire hasn't finished the security module will handle it with one message. Central chasing is slower and makes it a bigger deal than it is.
The export matters separately — several onboarding modules are usually compliance obligations, and that needs a timestamped per-person record rather than a percentage.
Keep the human parts
A sequence of modules is not onboarding on its own. Introductions, a buddy who isn't their manager, a manager check-in at the end of week one, and permission to ask obvious questions all matter more than the content does.
Automating the material is worth doing precisely because it frees attention for those.
Add Poplearn to Slack — free under 20 seats, installs in about a minute.
