Organizing Distributed Teams: Agreements, Tools, Availability

What changes when the team no longer sits in one place?

Even small companies today rarely have everyone working in the same room. Installers and field sales are on the road anyway, office staff work from home on certain days, and some companies have a second location or an employee in another city. A team whose members mostly work in different places is called a distributed team.

What gets lost becomes apparent only after a few weeks. The quick question across the desk, overhearing a phone call, the glance at the pile growing on the neighboring desk. In their place come messages in three channels, questions nobody answers, and meetings meant to clear up everything at once. This leads to the guiding question of this article: What agreements does a distributed team in a small company need so that information arrives, decisions get made, and nobody has to be available around the clock?

To answer it, we first introduce a thinking model that explains which channel suits which kind of communication. Then we assess what studies show about performance and strain in distributed work. At the end there is a channel map, rules on availability, and a guide to the first team agreement.

A distributed team rarely fails because of distance, but because nobody knows where which question belongs.

Conveying or converging? The thinking model of media synchronicity

For a long time, research followed the rule of thumb that rich channels such as face-to-face conversation suit difficult topics and lean channels such as email suit simple ones. Dennis, Fuller, and Valacich (2008) consider this view too coarse and proposed a more precise one with media synchronicity theory. Synchronicity here means how well a channel allows people to work on the same thing at the same time in a coordinated way.

The core of the theory: almost every task involving several people consists of two kinds of communication. In conveyance, information is passed on that the recipient must read, check, and process at their own pace. In convergence, people agree on a shared interpretation, for example in a decision or a conflict. Channels with low synchronicity are better for conveyance, because messages can be formulated calmly and read repeatedly. Channels with high synchronicity are better for convergence, because quick back-and-forth is possible.

From this, the authors derive two conclusions that are directly useful for a company. First, communication works best when several channels are used in sequence: first the documents by email, then the conversation for the decision. Second, the need for high synchronicity decreases the better those involved know each other, the task, and the tool. A well-established team can manage with more in writing than a newly formed one.

A survey of business buyers supports the model. Anders, Coleman, and Castleberry (2020) compared three theories of channel choice. Media synchronicity theory best explained respondents’ preferences: they wanted first messages from new salespeople by email, while for conflict resolution, negotiations, and relationship building in existing relationships they preferred phone and voicemail.

Does distributed work harm performance? Two perspectives

Two perspectives face each other in the debate about distributed work. One says: cohesion, onboarding, and performance require presence; whoever is not on site works less and learns less. The other says: flexibility retains employees and costs nothing, as long as the work is well organized.

The most informative study so far comes from Bloom, Han, and Liang (2024). At a technology company in China, 1,612 employees were randomly assigned to two groups for six months: one continued to work fully in the office, the other worked from home two days a week. The quit rate fell by one third in the second group, especially among non-managers, women, and people with long commutes. In performance reviews over the following two years and in promotions, the authors found no difference. Before the experiment, the 395 managers involved had expected a productivity loss of 2.6 percent; afterward they estimated a gain of 1.0 percent.

That does not refute the first perspective, however. Standaert, Ulm, Castro, and a further author (2025) analyzed survey data from 1,137 employees. Compared with hybrid work, exhaustion was higher when working exclusively from home, and engagement was lower when working exclusively on site.

I read the findings this way: it is not the location that determines performance but the form. According to the experiment by Bloom and colleagues, two days of distributed work in a well-organized team do no harm; fully distributed work without agreements is a strain. The experiment concerns a large company with office jobs, and installers or field sales work in a distributed way anyway. The lesson for small companies therefore lies less in the question of how many days of remote work are allowed than in how communication is organized.

The channel map: which channel for what?

The most important tool for a distributed team is not software but a single page, called the channel map here. For each channel, it defines what it is used for, how quickly a response is expected, and what it is explicitly not meant for. The following example shows a channel map for a trade business with 20 employees, eight of whom regularly work on job sites and two partly from home.

The map puts media synchronicity theory into practice. What is conveyed belongs in channels where it remains readable: email, task tool, repository. What requires convergence belongs in conversation. The most common mistake of distributed teams is the reverse: decisions are negotiated in long chat threads, and figures are read out over the phone.

For the repository, the filing charter from the article on digital filing applies: one place, three levels, one valid version. For the tools themselves, the guiding rule from the article on how to reduce tool sprawl applies: one piece of information, one place. Whoever is still looking for a task tool will find the criteria in the project management tools comparison.

How do you regulate availability without everyone always being available?

With distributed teams comes a silent expectation: whoever has a chat is available. Without an agreement, the most conscientious end up answering messages in the evening, and the others take their cue from them. The survey by Standaert and colleagues (2025) links working exclusively from home with more exhaustion. Clear rules on availability are therefore not a concession but a precondition for distributed work to hold up over time.

• Core hours: A fixed period, for example 9 a.m. to 3 p.m., during which everyone on office or remote duty responds to chat and phone.
• Response times per channel: as defined in the channel map. Whoever needs an answer faster calls.
• Absences visible: Customer appointments, job sites, focused work time, and vacation are in the shared calendar.
• No expectation outside working hours: Messages in the evening are allowed; answers are expected only on the next working day.
• Emergency route: For real emergencies there is a single route, usually the phone, and one person who handles it.

The last point takes the pressure off the other rules. If everyone knows that a real emergency comes by phone, nobody has to check the chat in the evening. For installers and field staff, an additional agreement is worthwhile: fixed time windows, for example in the morning before departure and at midday, in which they read messages and answer questions.

Which meetings does a distributed team need?

Distributed teams tend toward two extremes: too many video calls, because every question gets a meeting, or too few, because everyone works on their own. According to media synchronicity theory, a meeting with everyone is needed only for what requires convergence. All conveying happens in writing beforehand.

1. Weekly meeting (30 minutes, video)

   Priorities for the week, open decisions, obstacles. Figures and statuses are updated beforehand in the task tool and not read aloud.

2. Short daily check-in (10 minutes, only if needed)

   For teams with many dependencies, such as dispatch and installers: who is where, what is stuck?

3. Monthly in-person meeting

   At least once a month the team meets in person. Exchange, onboarding, and conflict resolution that fall short in video calls have room here.

4. One-on-one (monthly, 30 minutes)

   Every manager talks to every employee individually. In distributed teams, overload and dissatisfaction are otherwise noticed later.

For the design of individual meetings, the rules from the article on fewer meetings, better decisions apply, and for the weekly meeting the agenda from the article on weekly team planning. Media synchronicity theory predicts that teams who know each other well need less synchronicity. But that familiarity does not develop in chat.

What distributed work means for small companies

For small companies, distributed work is not only a question of organization but also one of attracting and retaining employees. The experiment by Bloom and colleagues (2024) shows that even two flexible days can significantly reduce quits, especially among people with long commutes. Whoever is competing for skilled workers will find further approaches in the article on the skills shortage in sales, and the article on keeping good people describes what retention in small companies depends on.

At the same time, there are limits. Not every job can be distributed, and the studies on remote work concern mainly office jobs. In a company where part of the team stands in the workshop and another part works from home, inequality can arise and should be addressed openly. A simple rule helps here: flexibility depends on the job, not the person, and the rules are equally visible to everyone.

Conclusion: which agreements a distributed team needs

We began by asking
agreements a distributed team in a small company needs so that information arrives, decisions get made, and nobody has to be available around the clock. The answer: a channel map that sets purpose and response time for each channel, regulated availability with core hours and an emergency route, and a few fixed meetings in which the team converges, while all conveying happens in writing beforehand.

As shown, in a well-studied experiment distributed work does not harm performance and reduces quits, while fully distributed work is associated in surveys with more exhaustion. Media synchronicity theory explains why: what matters is placing conveyance and convergence in the right channels. Distance is the smaller hurdle. The bigger one is a team that does not know where which question belongs.

First steps for this week

1. List all the channels your team communicates through today and remove the ones nobody would miss.
2. Draft a channel map with purpose, response time, and “not for” for each channel.
3. Set core hours and an emergency route.
4. Discuss the map and rules in a 60-minute team meeting and adjust them together.
5. After four weeks, check: which question ended up in the wrong channel, and what needs to change on the map?

The channel map belongs in the same place as the filing charter, and every new employee gets both on the first day.