Remote work does not remove collaboration. It removes the shortcuts that made collaboration feel automatic.
The office used to do part of the work for us
Before COVID-19, it was more or less normal for a team to work together in the same physical location. When a difficult problem appeared, people could gather around a whiteboard, sketch an idea, challenge an assumption and continue the discussion over coffee. Information travelled through formal meetings, but also through overheard conversations, quick questions and the simple fact that colleagues could see when someone was stuck.
That environment could make collaboration highly effective. It lowered the cost of asking a small question, created shared context almost by accident and helped relationships form through repeated contact. Yet proximity was never the same as teamwork. A group could sit in one room and still be divided by functional silos, unclear ownership or a culture in which people avoided difficult conversations.
The world has changed, and our ideas about work have changed with it. Remote and hybrid work are no longer temporary substitutes for the “real” office. They are normal ways of organising knowledge work. The useful question is therefore not whether remote work can reproduce every office interaction. It is what effective teams actually need, and how we can provide those conditions deliberately when people are not always in the same room.
Distance is not the only distance that matters
Research on distributed software development offers an important correction to the idea that physical separation automatically reduces quality. A Microsoft Research case study of Windows Vista found that differences in software quality between distributed and co-located development were statistically negligible. In a related survey, engineers often preferred to contact someone in their own organisation thousands of miles away rather than someone nearby in a different organisation. Organisational cohesion mattered more than geographical distance.
This is a useful lens for remote teams. The real barriers are often not kilometres but boundaries: separate goals, competing priorities, unclear decision rights, hidden dependencies and weak relationships. Putting everyone in one building does not remove those barriers. A well-designed remote team can sometimes collaborate more effectively than a co-located group whose structure works against it.
Communication structure becomes delivery structure
Conway’s Law states that organisations tend to design systems that mirror their communication structures. For software teams, this means team design is also architecture design. If work must repeatedly cross functional silos, the system and the delivery process are likely to inherit the same handovers and dependencies.
Remote work makes these weaknesses more visible because informal workarounds are less available. That can feel like a disadvantage, but it is also valuable feedback. If delivery depends on knowing whom to message privately, attending a particular meeting or relying on one person’s memory, the operating model was fragile already. Remote work simply exposes the fragility.
The answer is not to copy an organisational framework mechanically. Team Topologies and the reverse Conway manoeuvre can be useful ways to think about flow and ownership, but clean boxes on an organisation chart can also create new walls. The goal is not perfect separation. It is clear ownership combined with easy collaboration across boundaries.
Five practices that make remote teams effective
1. Make the work visible
Shared context must move from the room into durable, accessible places. Record decisions, owners, assumptions and open questions. Use a shared document or work item as the source of truth, rather than treating chat as organisational memory. Good written communication is not bureaucracy; it is infrastructure for inclusion and continuity.
2. Choose synchronous time deliberately
A meeting earns its place when people need rapid interaction: resolving ambiguity, making a difficult decision, exploring a problem or building shared understanding. Status sharing, routine updates and material that people mainly consume are usually better asynchronously. Protect synchronous time for the moments where conversation genuinely changes the outcome.
3. Create psychological safety on purpose
In a room, leaders can notice hesitation and invite someone into the conversation. Online, silence is easier to miss. Leaders need to ask directly, “What are we missing?” and make disagreement safe. Psychological safety is not about being nice or lowering standards. It means people can raise risks, admit mistakes and challenge an idea without fear of punishment, while the team still maintains high accountability.
4. Lead through trust, clarity and coaching
Remote leadership cannot depend on visibility or walking around. Set clear outcomes and constraints, then give people room to decide how to deliver. Be available without becoming a bottleneck. Coach rather than monitor, and judge progress through results, learning and collaboration rather than online presence.
5. Invest in cohesion before you need it
Trust is hard to create during an incident or a deadline. Build it through predictable habits: thoughtful onboarding, regular one-to-ones, retrospectives, pairing, demos and occasional social contact. Make space for informal conversation, but do not force artificial intimacy. The aim is familiarity, reliability and mutual understanding.
Remote-first does not mean remote-only
Physical gatherings still have value. Whiteboard sessions, workshops and team days can accelerate discovery and strengthen relationships, especially when a team is forming or tackling an ambiguous problem. The mistake is to treat the office as the default solution to every collaboration problem.
A strong hybrid model gives each mode a purpose. Use physical presence for high-bandwidth interaction and relationship building. Use synchronous online work for focused discussion across locations. Use asynchronous work for reflection, documentation and participation across schedules. When important knowledge remains available only to those who were in the room, the team is not hybrid; it has created two classes of participant.
The new advantage is intentionality
Before the pandemic, many teams benefited from proximity without having to describe why. Today, effective teams must be more explicit about how they communicate, make decisions, share knowledge and respond to failure. That extra intentionality can feel like effort, but it also creates a more resilient and inclusive way of working.
The measure of a remote team is not how closely it imitates an office. It is whether people can understand the goal, find the information they need, speak honestly, make decisions and deliver together. When those conditions are designed well, distance becomes a constraint to manage rather than an obstacle to performance.