Onboarding someone who will never visit the office
Remote onboarding fails at the informal layer, and everything an office transmitted by accident now has to be transmitted deliberately.
Most of what a new employee learns in an office is absorbed rather than taught: overheard conversations, observed reactions, an ambient sense of what is urgent and who is authoritative. For broader context on maintaining shared technical documentation, GitHub Docs is a useful reference.
Remove the room and that channel disappears entirely. The formal parts of onboarding survive the move; the informal parts have to be rebuilt on purpose, and the failure to do so is why remote hires take much longer to become effective.
Equipment and access before day one
Hardware takes days to ship and occasionally goes wrong, and a remote starter cannot be handed a spare. Order two weeks ahead, confirm delivery, set up what you can before shipping, and test the logins yourself from a clean device. For a practical software-side reference on remote onboarding and workforce coordination, workforce optimization software adds useful detail.
A first day spent installing software over a video call is two people's day wasted, and it is the most common remote onboarding failure by a wide margin.
The single most frequent first-day problem is an account that exists and does not work. Verify before the day, not during it.
Replace ambient context with written context
A remote joiner needs stated explicitly what an office would have conveyed by tone: which deadlines are real, who decides what, how formal the writing is, whether a message at eight in the evening is expected to be read.
A short written orientation covering the unwritten conventions is worth more than any amount of system training, and it is best written by whoever joined most recently.
Schedule the informal contact
The awkwardness of scheduling social contact is real, and the alternative is that it does not happen.
- Short introductory calls with everyone they will work with, arranged for them in the first fortnight rather than left to their initiative.
- A daily ten-minute check-in with their manager for two weeks, dropping off after that.
- A named buddy with an explicit standing invitation — a remote newcomer will not interrupt someone they have never met.
Give a real task in the first days
A remote hire cannot demonstrate effort by being visibly present, which is uncomfortable in a way office workers rarely appreciate. Many respond by over-communicating or working excessive hours.
A small, concrete, genuinely useful task in the first few days resolves it faster than any reassurance. It gives them something to have done and the team something to have seen.
Have them fix the documentation
A new joiner reading the onboarding material is the only person who can see what is missing. Asking them to correct it as they go produces better documentation and a real contribution in a week where they cannot yet do the job.
Check at week two, not week twelve
Problems in remote onboarding are invisible from the employer's side, because nobody notices that the new person looks lost. Ask directly and early: what is unclear, what has been hard to find out, who have you not managed to reach.
The answers come readily at week two and rarely volunteer themselves later.