Onboarding Remote, in 90 Days

Remote onboarding fails for the same reason in-person onboarding fails: nobody knows what to do with someone who is technically present and practically invisible. The cure is not more meetings. The cure is four habits that move trust signals from body language to written output.

Habit 1: a weekly written status update, religiously

Three lines. Shipped, learned, blocked. Sent every Friday afternoon to the same channel or email thread. The exact format does not matter; the streak does. By week 6, your team will check the channel for your update before checking on the project.

If you stop sending the update, your manager assumes you are stuck. If you keep sending it, even when the week was ugly, you control the narrative. Honesty in week 4's update ("blocked on infra access for 3 days, no progress") is a hundred times more credible than vague positivity.

Habit 2: video for trust, async for everything else

Default to async messaging. Move to video for two specific things: introductions in the first 30 days, and confused conversations where the message thread has gone three rounds and nobody is converging. Sending a 3-minute Loom or jumping on a quick Meet beats threading for another hour.

Resist the manager who wants to schedule daily video standups for "alignment." That is anxiety theater dressed as process. Twice a week, 25 minutes, with a written agenda, is the maximum sustainable cadence for most remote teams.

Habit 3: name your timezone overlap on day one

Send your manager and team an explicit message: "I am in Pacific Time. My realistic overlap with EST is 9am-12pm my time. Outside that I am happy to async or do occasional early/late calls if there is a real need." This converts a vague worry into a stated boundary the team can plan around.

Renegotiate the boundary once, around day 60, after you know what overlap actually feels like. Most teams under-ask if you set the boundary clearly upfront, and over-ask if you do not.

Habit 4: ship visible artifacts to the wiki, not Slack

Slack is ephemeral. The team forgets your work the moment the channel scrolls. The wiki, the docs site, the design file, the PR description, those persist. By week 6, your goal is to have 3-4 wiki pages or docs in the team's permanent space with your name on them. The pages do not need to be ambitious. They need to be findable.

Practical version: write your week-1 setup notes as a doc, not a Slack message. Write your project spec as a doc, not a thread. Write your week-4 30-day note as a doc, not a DM to your manager. Same content, persistent surface, dramatically different long-term visibility.

What does not work remotely

Trying to compensate by being "always on." You will burn out by week 5 and the team will not notice your additional hours, only your eventual disappearance.

Long onboarding plans handed to you by HR. They are written for in-person, scaled to remote by adding "but on Zoom." Use them as input, not the system.

Camera anxiety leading to camera avoidance. By week 4, your team should know what you look like in normal light, with normal hair, on a normal day. The first month is when faces become trusted. Skip it and you stay an avatar all year.

The 90-day signal

By day 90 in a remote role, the question is not "are you working hard?" The question is "do I know what you are working on without asking?" If your manager and 2-3 close colleagues can answer that crisply, your remote onboarding worked. If they have to think for 5 seconds, the four habits above did not stick yet.