Team Communication Guide: Channels, Async, Meetings, Docs
Team communication gets harder faster than the team grows, because every added person adds a link to every existing person. The number of possible one-to-one channels among n people is n(n-1)/2: 3 people have 3 channels, 6 have 15, 10 have 45 and 50 have 1,225. A team copes by deciding in advance which information goes through which channel, how fast an answer is expected, and where the final decision is written down.
Why communication cost grows faster than headcount
Each pair of people is a potential channel, so the count is the number of pairs: n × (n − 1) ÷ 2. Fred Brooks used this count in The Mythical Man-Month (Addison-Wesley, 1975; publisher’s page for the 1995 Anniversary Edition): if each part of a task must be coordinated separately with each other part, the effort grows as n(n-1)/2, so three workers need three times as much pairwise intercommunication as two, and four need six times as much. His point was that adding people to a late software project adds coordination work as well as capacity. The table applies the formula to common team sizes.
| Team size (n) | Possible channels, n(n-1)/2 | Added by the last person |
|---|---|---|
| 3 | 3 | 2 |
| 5 | 10 | 4 |
| 6 | 15 | 5 |
| 8 | 28 | 7 |
| 10 | 45 | 9 |
| 15 | 105 | 14 |
| 20 | 190 | 19 |
| 50 | 1,225 | 49 |
A six-person launch team that adds two people goes from 15 to 28 possible channels, an 87% increase in links for a 33% increase in people. Not every pair needs to talk, so the formula marks the upper bound of coordination complexity. Its use is as a reminder of why structure matters: a shared board, a decision log and a weekly update replace many pairwise conversations with one place everyone reads. Splitting a large group into small teams with defined interfaces does the same, because a 20-person group of four five-person teams has 4 × 10 = 40 internal channels instead of 190, plus whatever links the teams choose to keep.
Sync or async: a decision rule
Asynchronous communication moves work forward without requiring the other person to be available at the moment you send the message. GitLab’s handbook defines it as “communicating and moving projects forward without the need for additional stakeholders to be available at the same time your communique is sent.” Atlassian’s definition is broader: any communication that does not take place in real time, so email and page comments count, and so does a quick Slack exchange.
Neither mode is better in general. GitLab’s communication guidelines describe both as tools, each with a job, and name the failure of async-only work: a decision thread that takes “four days and seventeen replies to converge,” after which threads fork, context drifts and “no one knows who decided what.” Real-time conversation earns its cost when a disagreement is real, trust has to be built, or the context is not yet clear enough to write down.
| Situation | Better default | Reason |
|---|---|---|
| Status update, announcement, FYI | Async (board, chat, written update) | The reader needs no reply; a written copy stays |
| Question with one owner and no deadline today | Async, with context and a date | The owner answers inside focus time |
| Decision with a clear owner and written options | Async comments, then the owner decides | Gives people in other time zones a turn |
| Disagreement that has survived two rounds of comments | Short live call, outcome written in the log | Voice resolves what threads fork |
| Difficult feedback, conflict, a new colleague’s first weeks | Live (call or one-to-one) | Tone and trust matter more than a record |
| Production incident or blocking failure | Live, with a named incident contact | Latency is the cost |
| Explaining a process or walking through a design | Recording plus a written summary | Viewed at the viewer’s convenience, searchable if summarised |
Distributed teams already have evidence on how the mix shifts. A study in Nature Human Behaviour by Longqi Yang and colleagues used emails, calendars, instant messages, calls and workweek hours of 61,182 US Microsoft employees in the first six months of 2020. It found that firm-wide remote work “caused the collaboration network of workers to become more static and siloed, with fewer bridges between disparate parts,” and that “there was a decrease in synchronous communication and an increase in asynchronous communication.” The authors suggest these effects may make it harder to acquire and share new information across the network. The practical reading is that written channels need to be organised deliberately, because they do not create cross-team contact by themselves.
Rules that make async work
- Front-load context. A message states what happened, what the reader is asked to do, and by when. A date and time zone (“by 3 p.m. London time on Thursday”) is clearer than “urgent.”
- Agree response windows. Atlassian’s advice is to agree expected response times so people can protect personal time. A team might write: chat within one working day, email within two, incident channel immediately, and a named backup for absences.
- Do the pre-work. Send the agenda or gather written input before a live session, so the call is spent deciding rather than informing.
- Keep one place for comments. Input scattered across chat, email and a document leaves the decision owner without the full picture.
What published company handbooks do
GitLab publishes its internal handbook, which makes it one of the few places where a company’s communication rules can be read in full. Three practices are relevant to any project team.
Write first, then announce. The handbook-first page explains: “At GitLab, we write things down first, and communicate that (E.g. Document the solution first, then announce via Slack or email.). This way there is no need for documentation after the communication, a step that is frequently skipped.” The same page says discussions begin in GitLab Issues or Merge Requests, not in chat, so that whatever is merged has “a proper trail, full of context.”
Limit how long chat is kept. GitLab states that only 90 days of Slack activity is retained and describes the limit as a “forcing function”: if people can search chat history for project updates, they have little reason to put progress somewhere universally accessible. A smaller team need not delete anything, but the principle carries over: chat holds questions, the board and the decision log hold facts.
Treat the document as the single source of truth. GitLab argues that wikis do not scale when only a few people can edit them, because content goes stale and readers learn to distrust it until they confirm with a person. Its alternative is that anyone can propose an edit through version control. Project teams without that tooling can approximate it with a named owner per page and a visible “last reviewed” date.
GitLab is an all-remote software company, and its handbook records one company’s practice. The same rules fit a single project team of six less well than they fit a company spread over many time zones, and each rule has a cost in writing time.
What to write down
| Record | What it contains | Where it lives |
|---|---|---|
| Decision log | Decision, owner, date, options considered, reason | One shared page or tracker |
| Meeting notes | Outcomes and action items with owner and due date, link to any recording | Linked from the calendar invite |
| Procedures | Repeating tasks written once; see the SOP writing guide | Wiki or handbook |
| Project context | Goals, scope, constraints, stakeholders, for new members | Kickoff page; see the project kickoff checklist |
| Status | Progress against plan, risks, asks; see status reports | Board and a weekly written update |
Meetings: what the survey data says and how to run them
Meetings are the synchronous channel with the largest and most visible cost. The arithmetic is straightforward: a one-hour weekly meeting with eight people uses 8 person-hours a week, which over 48 working weeks is 384 person-hours a year before preparation and follow-up.
A widely cited survey of the problem comes from Leslie Perlow, Constance Noonan Hadley and Eunice Eun in Harvard Business Review’s July-August 2017 issue. Their wording: “We surveyed 182 senior managers in a range of industries: 65% said meetings keep them from completing their own work. 71% said meetings are unproductive and inefficient. 64% said meetings come at the expense of deep thinking. 62% said meetings miss opportunities to bring the team closer together.” In a survey the authors conducted with nearly 200 senior executives, “only 17% reported that their meetings are generally productive uses of group and individual time.” The respondents were senior managers and executives, and the authors also write that meetings “provide real benefits,” so the figures make the case for fewer, better-prepared meetings.
Microsoft’s 2022 Work Trend Index combined an external study of 31,000 people in 31 countries with an analysis of anonymised productivity signals in Microsoft 365, and its meeting figures come from that activity data. The full report gives the baseline: “Since February 2020, the average Teams user saw a 252% increase in their weekly meeting time and the number of weekly meetings has increased 153%.” The same report says the average Teams user sent 32% more chats each week in February 2022 than in March 2020. The figures describe one vendor’s product during the shift to remote and hybrid work, and they show how fast synchronous load can grow when nothing limits it.
GitLab’s meeting rules
GitLab’s all-remote meetings page sets rules that address the same complaints:
- Ask whether a meeting is needed. The handbook says to ask whether async methods could achieve the outcome before scheduling.
- No agenda, no attenda. Every work meeting has one live agenda document attached to the invite, shared at least 72 hours in advance where possible (24 hours minimum). It lists the title, attendees, background, the desired outcome and a place for questions.
- One agenda only. If a meeting turns out to have two, stop and clarify which is the source of truth.
- Cancel readily. The handbook says roughly 1% of GitLab meetings should end within the first minute because there is no known outcome, missing material or inadequate preparation, and that cancelling is “not a failure.”
- Make optional attendance real. Mark non-essential invitees optional, and record meetings so people can contribute afterwards.
- Leave gaps. Its calendar setting for 25- and 50-minute meetings leaves time between calls.
- Send actions to the tracker. Action items go directly to an issue, linked from the agenda.
The meeting agenda templates page has copyable agendas with timeboxes for several formats.
Cadence for framework teams
Teams using Scrum have fixed limits. The Scrum Guide (November 2020 version) describes the Daily Scrum as “a 15-minute event for the Developers of the Scrum Team,” and timeboxes Sprint Planning to a maximum of eight hours, the Sprint Review to four hours and the Sprint Retrospective to three hours for a one-month Sprint. Sprints are “fixed length events of one month or less,” and for each of those three longer events the guide adds: “For shorter Sprints, the event is usually shorter.” These are ceilings for that framework. A non-Scrum project can start with a weekly written update and a decision meeting only when needed.
A communication plan template
A communication plan is a table that answers what, to whom, how often, through which channel and by whom. Write it at kickoff and revisit it when the team or the stakeholder list changes. The rows below show a plan for a six-person launch team with two outside stakeholders.
| Information | Audience | Frequency | Channel | Owner | Response expectation |
|---|---|---|---|---|---|
| Work status | Whole team | Continuous | Project board | Each task owner | None; read before asking |
| Weekly written update | Team and sponsor | Weekly, Thursday | Email or doc | Project lead | Questions in one comment thread by Friday |
| Decisions | Team and affected stakeholders | As made | Decision log, link in chat | Decision owner | Objections within two working days |
| Short questions | Individuals | As needed | Chat thread with context and due date | Asker | Within one working day |
| Risks and blockers | Project lead and sponsor | Weekly; immediately if severe | Risk register, call if severe | Risk owner | Same day for blockers |
| Urgent service problems | Incident contact | As needed | Phone or call | Named on-call person, with a backup | Immediate |
| Design or planning discussion | Required attendees | Only when async comments have not settled it | Meeting with agenda | Facilitator | Notes within one working day |
| Stakeholder summary | Outside stakeholders | Monthly | Report or call | Project lead | As agreed at kickoff |
Check the plan after two weeks
After two weeks, find one decision that was delayed and one meeting that was unnecessary. Change the specific rule behind each (a missing owner, a response window nobody saw, an invite list that was too long), update the plan and note the change in the decision log. This keeps the plan a living agreement rather than a document nobody opens.
Common failures and fixes
| Failure | Result | Fix |
|---|---|---|
| Meeting for every question | Calendar full, solo work pushed to evenings | Ask whether a written update works; make attendance optional |
| Chat as the only record | Decisions buried in scroll-back | Copy decisions to the log at the time they are made |
| Decisions made in a call and not written | Different people remember different outcomes | Owner posts outcome and reason the same day |
| No response norms | Some people check constantly, others disappear | Agree windows in working hours and name a backup |
| Several competing documents | People edit and read different versions | One authoritative page; others link to it with an owner named |
| Recordings with no summary | Nobody has time to watch them | Attach a written summary and the linked document |
Sources
- Frederick P. Brooks Jr., The Mythical Man-Month (Addison-Wesley, 1975; Anniversary Edition 1995), publisher’s page
- Yang et al., “The effects of remote work on collaboration among information workers,” Nature Human Behaviour (2022)
- Perlow, Hadley and Eun, “Stop the Meeting Madness,” Harvard Business Review, July-August 2017
- GitLab Handbook: Effective and responsible communication guidelines
- GitLab Handbook: The importance of a handbook-first approach to communication
- GitLab Handbook: All-remote meetings
- Microsoft: 2022 Work Trend Index announcement, March 16, 2022
- Microsoft WorkLab: “Great Expectations: Making Hybrid Work Work,” 2022 Work Trend Index report
- Atlassian: Asynchronous communication for distributed teams
- The Scrum Guide (November 2020)