Week one is the point of maximum cognitive load in someone's entire time at a company. They're learning names, tools, processes, norms, and where the coffee is, while trying to appear competent.
Introducing a training portal into that week is a strange choice, and it's worth asking what it's actually buying you.
The provisioning gap
There's a practical problem before the experience problem: LMS access frequently isn't ready on day one.
The laptop arrives, the email account works, Slack is set up — and the LMS account is waiting on someone in IT or HR to create it, which happens on day three. So onboarding, the thing most sensitive to timing, is the last system to become available.
That gap is invisible in the process documentation and completely obvious to the new hire, who spends their first days without the material that was supposed to orient them.
Chat access is nearly always the first thing provisioned, often before hardware. Delivering onboarding there removes the gap entirely.
One more thing to learn
Every system a new hire touches in week one has a learning cost — where things are, how navigation works, what the icons mean.
For tools they'll use daily, that cost is worth paying. For a training portal they'll visit during onboarding and then perhaps twice more that year, it's pure overhead. They'll learn it, use it briefly, and have forgotten it by the time the annual compliance module arrives.
Delivering training in a tool they're already learning for other reasons means the interface cost is paid once, for something they'll use constantly anyway.
What the portal was actually for
Worth being fair: portals exist for real reasons, and if you need them, you need them.
- A catalogue, so people can browse and self-enrol. Genuinely useful for optional development, irrelevant for mandatory onboarding.
- SCORM content, if you've purchased course libraries.
- External audiences — contractors, customers, partners — who can't be reached in your workspace.
- A permanent record the individual can access themselves.
If onboarding is your use case specifically, the first three usually don't apply. Onboarding is assigned rather than browsed, usually written in-house rather than purchased, and delivered to employees.
What it looks like without one
The sequence arrives as direct messages over the first two or three weeks, in a deliberate order — orientation first, tools and process next, policies after, role-specific depth last.
Each module is short enough to finish between other things, which matters enormously in a week when nothing has a predictable shape. Completion is recorded as it happens, so nobody has to report on their own progress.
Assignment targets everyone who joins from a date forward rather than a list of names, so a new hire gets the sequence whether or not anyone remembered to enrol them — which removes the most common onboarding failure entirely.
Keep the human parts
Content is the easy half. The parts that actually determine whether onboarding worked are a buddy, a manager check-in at the end of week one, introductions to the people they'll depend on, and permission to ask obvious questions.
Automating the material is worth doing because it frees attention for those, not because it replaces them.
Setting it up
If you already have an onboarding document, most of the work exists.
Poplearn turns it into the sequence. /courses new splits the document into modules and writes the quizzes; /assign #general sends it to a channel or to every new hire from that point forward, with reminders; /progress gives live completion by team.
Everything arrives as Slack direct messages, so a new hire needs nothing beyond the access they already have on day one. Free under 20 seats, installs in about a minute.
