Dr. Neil's Notes
General > People
Lead the Room You Are Not In
Introduction
The most consequential leadership moments in a distributed team are the ones the leader is not present for. The ambiguous situation that arises at 11pm in one time zone. The difficult conversation between two team members that no one flagged until it had already gone wrong. The decision made under time pressure by someone who was not sure they had the authority to make it.
A leader cannot be present for all of these. The question is whether the team has been prepared for them.
Building Leadership at Every Level
Empowerment is not a gift delivered once from the top. It is a capability built over time at every level of the team. The informal leaders, the person people turn to when they have a problem, the one who keeps the team focused when things get unclear, often hold more day-to-day influence than the formal structure suggests. Identifying those people and developing them deliberately is one of the highest-leverage investments a leader can make.
This is not about creating a management layer. It is about ensuring that good judgement is distributed throughout the team, so that when a difficult situation arises without warning, someone is equipped to handle it well.
Sharing Your Reasoning
When a leader shares only their conclusions, the team can follow instructions. When a leader shares the reasoning behind a decision, what was weighed, what was prioritised, what was treated as a constraint, the team begins to internalise the decision-making model. Over time, they can apply it to new situations without needing to consult anyone.
This is one of the most practical things I have found for building autonomous teams. People who understand why you decided something are vastly better positioned to make the next related decision well than people who only know what you decided.
Checking In on the Whole Person
Isolation is a genuine risk in distributed work. It is not always visible from a distance. Someone who is struggling with the loneliness of working alone, or who has quietly disengaged from the team, can appear to be functioning normally in a task-tracking tool or in the brief window of a weekly call.
Regular check-ins that go beyond work output, that create space for someone to say things are hard, or that they are not sure they belong in the team, or that something is not working, are part of the infrastructure of a well-functioning distributed team. A leader who notices early and responds with genuine care earns a kind of trust that no process or policy can replicate.
Designing for Informal Connection
Informal interaction is disproportionately valuable for new joiners and early-career team members. In a co-located setting, a lot of contextual knowledge is absorbed simply by being in the environment, overhearing conversations, picking up on how decisions get made informally, understanding the culture through observation. In a distributed setting, none of that happens by accident.
Leaders building distributed teams need to design for informal interaction deliberately. Periodic and optional in-person time, unstructured virtual social sessions, cross-regional pairing on work, these are not nice-to-haves. They are maintenance on the relational infrastructure that everything else depends on.