Training programmes designed for an office lean on support nobody accounted for. Distributed teams lose all of it at once, which is why programmes that seemed fine before a company went remote often quietly stop working after.
What the office was doing
A colleague mentions they've done the training. Someone complains about it at lunch. A manager notices people clicking through it and mentions it in standup. There's a poster by the printer.
None of that was designed, and all of it created awareness that the training existed and was currently a thing. Remote teams have none of it — a course in a portal is socially invisible.
The practical consequence is that remote training has to carry its own visibility rather than borrowing it from the environment.
Chat is the only shared surface
Distributed teams have exactly one place everyone reliably is. Coordination, announcements, questions, and social contact all happen there because there's nowhere else.
Training delivered as Slack direct messages inherits that. It arrives in the same stream as everything else that matters, at a time the person is actually working, in whatever timezone they're in. Training delivered to a portal has to compete with that stream from outside it.
Asynchronous by construction
Poplearn modules arrive one at a time, roughly six minutes each, and are completed in the message. There's no session to attend and no synchronous component to schedule.
That matters across timezones for an obvious reason: any live session privileges one region and produces a recording nobody in the others watches. A recording isn't an async artefact — it runs at the speed of speech, can't be skimmed, and assumes context from the room.
Modules that stand alone can be completed in whatever order someone's week allows. When generating a course, it's worth scanning for modules that open with "as described above" — someone who did the previous one last Tuesday won't have that fresh.
Onboarding is the hardest case
Remote onboarding compounds every problem. A new hire has no ambient awareness at all, doesn't yet know who to ask, and often can't tell whether they've missed something.
Assigning to everyone who joins from a date forward matters more here than anywhere else, because there's no manager glancing over to check the new person got set up. The sequence has to arrive on its own.
Chat access is also usually a remote new hire's first access — often before hardware arrives — which makes it the only delivery channel that works on day one.
Push visibility to regional leads
Chasing is worse remotely. Every follow-up round costs a day across timezones, so a two-round exchange takes a week.
/progress returns live completion by team, in Slack, so a lead in each region can see their own people and close gaps during their own overlap hours. That's considerably faster than a central function coordinating follow-up across regions, and it restores the informal awareness a manager would have had in person.
Timezone details that matter
Small things that have outsized effects:
- Reminders should land at plausible working hours for the recipient, not at a fixed server time.
- Deadlines that fall at end-of-day in one region are the middle of the night in another — pick them with that in mind.
- Nothing mandatory should require synchronous participation.
Keep a place for questions
The one genuine advantage of in-person training is that people ask things and everyone hears the answer. Async loses that by default.
Getting it back costs nothing: a channel where questions about the training go, with answers visible to everyone rather than sent privately. Over time that thread becomes more useful than the original material.
Add Poplearn to Slack — free under 20 seats, installs in about a minute.
