Joining an Existing Remote Team as Its Manager

A new manager in an office spends the first weeks watching. Who defers to whom, who is overloaded, where the tension is, what people say when the meeting ends.

Remotely none of that is available, and the instinct to compensate by acting quickly is the main way new remote managers damage teams they have not yet understood.

The first two weeks: only listening

One-to-one with everyone, early. Not to assess — to listen. Same questions to each person, so you can compare:

What are you working on and why does it matter? What is working well here? What is frustrating? What would you change if you could? What do you need from me? What should I know that I have not asked about?

The last question produces the most.

Read everything. Decision records, project documents, recent threads in team channels. This is the closest available substitute for having been present, and it is more informative than people expect. A team's chat history reveals how decisions actually get made.

Ask about the previous manager carefully. You need to know what changed, and people will be guarded. Ask what they hope stays the same rather than what was wrong.

Change nothing. Almost every arrangement you find strange has a reason you have not learned yet. Note it and wait.

Weeks three to six: understanding the system

Map the work. What the team owns, what depends on it, what it depends on. In a distributed organisation this is frequently undocumented and partially known even to the team.

Find the load-bearing person. Every team has someone who is quietly the reason things work — the one who knows the history, unblocks people, answers everything. They are usually not the most senior. Identify them, because they are also your single point of failure.

Notice who is quiet. In an office the quiet person is visible. Remotely they are absent from your perception entirely. Look at who has not spoken in team channels, who has not raised anything in one-to-ones, who was not mentioned by colleagues.

Talk to adjacent teams. How does the team look from outside? The answer is frequently different from inside and always informative.

Weeks seven to twelve: changing things

By now you have earned a view. Change deliberately and few things.

Explain the reasoning, in writing. A remote team cannot read your intent from context. A change announced without reasoning is interpreted, usually less charitably than intended.

Start with something that removes work. A cancelled meeting, a simplified process, an unblocked dependency. It demonstrates that changes are for their benefit before you ask for anything.

Name what you are not changing. Explicit reassurance is worth a great deal to a team that has just had a manager replaced.

What new remote managers get wrong

Scheduling more meetings to compensate for not seeing the team. It reduces their working time and does not produce understanding.

Requiring camera-on as a proxy for engagement.

Restructuring in month one, before understanding why the current shape exists.

Being visible constantly as a demonstration of commitment. It reads as monitoring.

Relying on the loudest voices. In a distributed team the people who speak most in calls are not necessarily the people who know most, and the gap is wider than in a room.

The honest timeline

You will understand an office team in about a month and a distributed one in about three. Plan for the longer version rather than compensating for it with speed.