Your First 90 Days on a Distributed Team
In an office, a new joiner absorbs an enormous amount by accident: who actually decides things, which projects are in trouble, what the unwritten rules are. None of that transfers by accident remotely.
The consequence is that remote onboarding is not slower, it is different. What works is deliberate: small visible deliveries early, actively hunting for context nobody thought to give you, and building relationships that have no corridor to form in.
Why remote onboarding fails differently
Because the informal channel disappears. In an office, context arrives through overheard conversations and hallway questions. Remotely, if it was not written down or explicitly told to you, it does not reach you, and nobody realises you are missing it.
The second difference is visibility. In an office, being present reads as contributing. Remotely, only output is visible, which is harsher early on when you are still learning and have little output to show.
| What you get in an office | What replaces it remotely |
|---|---|
| Overheard context | Reading the written record deliberately |
| Hallway questions | Asking explicitly, in public channels |
| Visible presence | Small, early, visible deliveries |
| Informal relationships | Scheduled one-to-ones with no agenda |
In shortNothing arrives by accident. Everything you would have absorbed, you now have to go and get.
Month one: context and one small delivery
The goal is not impact, it is orientation plus proof of life. Read the written record systematically, meet people individually, and ship one small, visible thing. That first delivery matters less for what it is than for establishing that you produce.
- Read the last three months of decisions in the documentation, not just the onboarding pages.
- Book a thirty-minute call with everyone you will work with, with no agenda beyond understanding what they do and what frustrates them.
- Write down every question you could not answer from the record. That list is genuinely useful to whoever maintains it.
- Ship one small visible thing in the first three weeks, even if trivial.
- Ask your manager explicitly what success looks like at ninety days, and write down the answer.
Ask questions in public channels rather than direct messages. It feels more exposed and it is far better: the answer becomes searchable and you stop being a private drain on one person's time.
In shortOne small shipped thing in three weeks buys you months of patience.
Month two: from doing to owning
The shift is from completing assigned tasks to owning an area, however small. Owning means noticing problems before being told, proposing rather than asking, and being the person others route a category of question to.
- Pick something nobody owns and start maintaining it. Unowned things are everywhere and taking one is the fastest route to being useful.
- Move from «what should I do?» to «I plan to do X unless you disagree». It is the async default-action habit applied to your own work.
- Start writing decisions down as you make them, even small ones. It builds the record and makes your thinking visible.
- Give feedback on something. New joiners see the things everyone else stopped noticing, and that window closes.
That last point has a short shelf life. The fresh-eyes observations you can make in month two are invisible to you by month six, so it is worth writing them down even if you do nothing with them yet.
In shortOwning one small unowned thing does more for your standing than completing ten assigned ones.
Relationships without a corridor
They have to be deliberate, because there is no accidental contact. The mechanism that works is regular one-to-ones with no agenda, across teams rather than only within yours, accepting that some will feel awkward before they feel natural.
People often resist this as forced. It is forced, and it is also the only version available. The alternative is knowing only the people your work routes you through, which in a distributed company is a very small number.
- Keep a rolling list of people you have not spoken to and work through it.
- Cross-team conversations pay off most: they are where you learn what is actually happening.
- Turn the camera on early in the relationship and stop worrying about it later.
- Notice who answers questions in public channels. Those are usually the people worth knowing.
In shortDeliberate and slightly awkward beats organic and nonexistent.
The mistakes that quietly set your reputation
Waiting to be given context, staying silent to avoid looking inexperienced, disappearing into a long project with nothing visible for weeks, and matching your hours to a time zone that is not yours because nobody told you not to.
- Asking in public and building the searchable record.
- Small visible deliveries while you learn.
- Writing down what confused you, which helps the next joiner.
- Setting your working hours explicitly in the first week.
- Waiting for onboarding to be done to you.
- Silence to avoid looking new, which reads as disengagement.
- Six weeks on something invisible.
- Drifting into permanent evening hours without ever deciding to.
Remotely, nobody sees you working. They see what you finish and what you write.
In shortSilence and invisibility are the two failure modes. Both are avoidable in week one.
Frequently asked questions
How is remote onboarding different from in-office?
The informal channel disappears. Context that would arrive through overheard conversations and hallway questions has to be actively sought, and nobody notices when you are missing it.
What should I deliver in the first month?
Something small and visible within about three weeks. Its value is not the work itself but establishing that you produce, which buys patience while you learn.
Should I ask questions publicly or privately?
Publicly, in shared channels. It feels more exposed but the answer becomes searchable for the next person and you stop consuming one colleague's time privately.
How do I build relationships without an office?
Deliberately: regular one-to-ones with no agenda, prioritising people outside your immediate team. It feels forced because it is, and it is the only version available.
How do I know if I am doing well?
Ask your manager in the first month what success looks like at ninety days, and write the answer down. Without that, both of you are guessing.
What if the documentation is bad?
Write down every question you could not answer from it. That list is valuable to whoever maintains the record and it makes your gap-finding visible rather than looking like slowness.
Should I turn my camera on?
Early in a relationship, yes. It accelerates familiarity considerably. Once people know you, it matters much less and can be relaxed.
How do I avoid working other people's hours?
Set and state your working hours in the first week, before habits form. Drifting into permanent evening availability happens gradually and is very hard to reverse later.
What if I am not given enough work?
Find something unowned and start maintaining it. Unowned things exist in every team and taking one is the fastest path from new joiner to useful colleague.
When should I start giving feedback?
In month two, while your fresh perspective still exists. The things you notice as a newcomer become invisible to you within a few months, so write them down even if you act later.