Onboarding someone who will not be in the room
Remote onboarding fails at the informal layer. Everything the office transmitted by accident now has to be transmitted on purpose.
Most of what a new employee learns in an office is not taught. It is absorbed — overheard conversations, observed reactions, the ambient sense of what is urgent and who is authoritative and how things are really decided.
Remove the room and that channel disappears. The formal parts of onboarding survive the move to remote largely intact; the informal parts have to be rebuilt deliberately, and the failure to do so is why remote hires in small companies often take twice as long to feel established.
Equipment has a longer lead time
Shipping hardware takes days and occasionally goes wrong, and a remote hire cannot be handed a spare from the cupboard. Order at least two weeks ahead, confirm delivery before the start date, and have a fallback that lets someone work on day one if the laptop is delayed. For broader independent guidance on this point, consult CISA Secure Our World.
Set up whatever you can before shipping. A remote first day spent installing software over a video call with whoever is technical is a poor use of two people.
Replace ambient context with scheduled context
The office transmits context continuously. Remote work transmits it only when someone decides to.
The substitutes are unglamorous and effective: a written summary of what each part of the business is currently working on; recorded rather than live explanations, so they can be rewatched; explicit statements of things an office would convey by tone, such as which deadlines are real.
Schedule the informal contact
The most-missed thing is not information but incidental human contact, and the honest position is that scheduling it is awkward and still better than the alternative.
- Short introductory calls with everyone the person will work with, in the first fortnight, arranged for them rather than left to their initiative.
- A daily check-in with the manager for the first two weeks — ten minutes, not a status meeting — dropping to less frequent after that.
- A named buddy with an explicit standing invitation, because a remote newcomer will not interrupt someone they have never met.
A remote new hire sits on a question for hours because interrupting requires a deliberate act. Say explicitly what the acceptable interruption channel is and how quickly it is normal to use it.
Write down what was previously understood
Working conventions that an office communicates implicitly have to be stated: core hours, expected response times, whether cameras are expected, what gets decided in writing versus in a call, and whether a message sent at eight in the evening is expected to be read.
The last one matters disproportionately. Without an explicit norm, new remote employees assume the most demanding interpretation and either burn out or quietly resent it. For a product-level comparison in this area, review remote employee monitoring software.
Give the first task early and make it visible
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 by working excessive hours.
A concrete, achievable first task delivered in the first few days resolves this faster than any reassurance. It gives them something to have done, and it gives the team something to have seen.
Check at week two, not week twelve
Problems in remote onboarding are less visible from the employer's side, because there is no one noticing that the new person looks lost. By the time it surfaces in a formal review it has been running for weeks.
Ask directly and early: what is unclear, what has been hard to find out, who have you not been able to reach. The answers arrive readily at week two and rarely volunteer themselves later.