The remote hire you onboarded by Slack

The laptop arrived before anyone had booked 30 minutes to talk to her. That was the onboarding plan. At one company I worked with, a senior marketing manager started remotely with a welcome message in #marketing-team, a Notion page holding 17 links, and a single 30-minute kickoff call with her manager in week 1. After that she was expected to get oriented from the documents and ask questions in Slack as needed.

Six weeks in, she was shipping work, but the work was off in ways her manager couldn't name. The Slack updates read confident. The deliverables landed on time. In a one-on-one in week 8, she admitted she still didn't know what the company expected of her role, wasn't sure which stakeholders mattered, and had been guessing at the norms. She hadn't asked, because the Slack messages she'd seen made it look like everyone else already knew, and she didn't want to be the new hire asking the obvious question.

Slack-only onboarding is the default at most distributed companies, and it produces this pattern on schedule. The new hire can't read the room from text. They can't calibrate tone, urgency, or hierarchy from messages. They can't tell a welcome question from one that exposes them as not-yet-competent. The medium rewards visible activity, quick replies, helpful answers, casual emoji, and it penalizes silence and uncertainty. So new hires perform confidence to fit in. The performance hides the confusion, and the confusion compounds for weeks.

The compounding is the expensive part. Every week the hire doesn't raise the obvious question, the question gets harder to raise. By week six, asking what does my role own stops being a normal new-hire question and becomes a confession that the previous six weeks were performed rather than understood. So the hire either pushes through and ships increasingly drifty work, or quietly starts looking for a job where they can be new again with a clean slate.

The correction isn't better documentation. The documents are the easy part. What's missing is synchronous time, built into the first sixty days, with named humans on the calendar. A buddy who isn't the manager, usually a peer, holds a weekly 30-minute block for the first ninety days. Four context-transfer calls get scheduled in the first three weeks with senior people across functions, each with a topic and something to produce. The manager's kickoff names what good looks like in the role, in three to five concrete examples. And the hire gets explicit permission to ask the obvious questions in private for the first sixty days, with no judgment attached.

The deeper issue is what remote work did to onboarding generally. In-office onboarding had failures too, but it carried a redundancy distributed work lacks: serendipity. The new hire overheard conversations, watched body language in meetings, ate lunch with people, saw how decisions got made. None of that exists in distributed work unless the company builds it on purpose.

So invert the assumption. The remote hire who isn't ramping is rarely the hire's failure. It's the missing synchronous infrastructure the company assumed Slack would cover. Slack doesn't cover it. Build the replacement deliberately, or watch the next remote hire fail at the same rate, on the same schedule, for the same reason.