Onboarding a Remote Hire: The First Ten Days in Detail
The previous four remote hires each took between six and eight weeks to make their first independent contribution. The fifth took twelve days, after the first ten days were rewritten as a schedule rather than a folder of links.
The company had 55 employees and hired two or three people a quarter, always remotely. Onboarding had been a document, a laptop and good intentions.
What the old onboarding contained
A 34-page document, 41 links to other documents, and a first-week calendar with nine introductory calls. New hires described it afterwards as overwhelming and vague, in that order.
The links were the main problem. Of the 41, eleven were out of date and four led to pages requiring permissions the new hire did not yet have.
The ten-day schedule
The rewrite reduced the document to two pages and replaced the calendar with a schedule of ten days, each with one thing to learn and one thing to produce. Day one: find out who does what, and post a short note describing your own understanding of the product.
Producing something on day one sounds harsh. It produced a written artefact the new hire could return to, and it gave the team a view of what had been misunderstood while it was still cheap to fix.
Days one to three
The first three days were informational and included four calls of 30 minutes, each with a named purpose. The new hire wrote a running note that was shared with the team from day one, which removed the impression of being assessed in private.
Two hires said the shared note made it acceptable to ask obvious questions in writing, which is the behaviour the format was designed to encourage.
Days four to seven
The middle days moved to doing: a small task with a named reviewer, deliberately chosen to touch three systems. The task was real work and was allowed to ship, which mattered more than its size.
Permission problems surfaced here, which was the point. Two of the four new hires needed a database read role that nobody had thought to grant, and the schedule made the gap visible on day five rather than day thirty.
Days eight to ten
The last three days covered the part most onboarding skips: how decisions get made and who to ask when the document does not answer. This was a single conversation with a different person each day, chosen from outside the immediate team.
The new hire then wrote a page explaining what they had learned, which was reviewed and, in three of four cases, added to the onboarding document.
What it cost the team
About 11 hours of team time per hire, mostly in the four calls and the task review. The previous process consumed about six hours and produced a hire who asked the same questions for two months.
The extra five hours are paid once. The repeated questions were paid weekly.
What was cut
Nine introductory calls became four. The 34-page document became two pages plus a schedule. The 41 links were reduced to seven, each checked the week before the hire started, which is a small recurring job nobody enjoys.
The link check is the only part of the process that decays if left alone, and it is now on a monthly reminder.
Three hires later
Time to first independent contribution fell from six to eight weeks, to a range of twelve to nineteen days. Two of the three hires said the schedule was the reason they stopped feeling like a guest in week two.
Six to eight weeks once passed before a new hire contributed alone. Twelve days now, and the change came from writing ten days down rather than from hiring differently.
