Apply Distributed Team Practices

---
name: apply-distributed-team-practices
description: Use when managing a team where members work in different locations, time zones, or on hybrid schedules — to adapt management practices so remote members have equal access to information, relationships, and advancement opportunities as in-office members.
source: GitLab "The Remote Work Playbook" (about.gitlab.com/company/culture/all-remote/); Automattic remote work culture documentation; Microsoft WorkLab "The New Future of Work" research (2022); Lencioni "The Five Dysfunctions of a Team" adapted for remote
tags: [remote-work, distributed-team, hybrid, async, remote-management, inclusion, communication, documentation]
---

# Apply Distributed Team Practices

Adapt your management approach for distributed or hybrid teams — making information accessible asynchronously, relationships intentional, and participation equitable regardless of location.

## Why This Is Best Practice

**Adopted by:** GitLab (1,500+ employees, fully remote since 2011) publishes the most comprehensive remote work playbook in the industry; Automattic (WordPress parent, fully remote since 2005) has a documented no-office culture; Shopify, Airbnb, and Spotify operate distributed models; Microsoft WorkLab's "The New Future of Work" (2022, 20k+ participants) is the largest ongoing research program on hybrid work effectiveness
**Impact:** Microsoft WorkLab (2022) found that in hybrid teams without deliberate inclusion practices, remote employees are 22% less likely to be included in meetings, 26% less likely to receive real-time feedback, and have 2× the risk of "proximity bias" — being passed over for promotions in favor of visible in-office peers; GitLab's internal research shows async-first teams complete projects 40% faster than teams relying on synchronous-only communication, primarily by eliminating scheduling friction; Stanford research (Bloom, 2022) found remote workers are 13–18% more productive on individual tasks but 30% less productive on collaboration without deliberate structure
**Why best:** Managing a distributed team with in-office management practices produces two failure modes: (1) information asymmetry — remote members miss hallway conversations, social context, and informal decisions; (2) proximity bias — in-office members are more visible, more likely to be recognized, and more likely to be promoted; applying distributed practices deliberately counteracts both without requiring everyone to be co-located

Sources: GitLab "The Remote Playbook" (about.gitlab.com/handbook/); Microsoft WorkLab "The New Future of Work" (2022); Bloom "How Working From Home Works Out" (Stanford, 2022); Larson et al. "A Primer on Making Hybrid Work" (McKinsey, 2021)

## Steps

### 1. Shift to async-first communication

Async-first does not mean async-only. It means that the default mode for most communication is asynchronous, and synchronous time is reserved for work that genuinely requires it.

**Synchronous (video/in-person) is appropriate for:**
- High-stakes decisions requiring real-time debate
- Conflict resolution
- Relationship-building (team social events)
- Complex ambiguous problems requiring collaborative exploration

**Async is appropriate for:**
- Status updates and project progress
- Non-urgent questions and discussions
- Feedback on documents and code
- Decisions with clear information available

For every recurring meeting: ask "could this be a written update instead?" If yes, replace it. Unnecessary synchronous meetings penalize people in incompatible time zones and drain focused work time.

### 2. Document decisions and context, not just outcomes

In co-located environments, context travels through hallway conversations, overheard discussions, and visible body language. None of these channels exist for remote members.

**Documentation discipline:**
- Every decision of consequence gets a written record: what was decided, why, and who was involved
- Meeting notes are shared within 24 hours of the meeting, accessible to everyone on the team
- "Context documents" explain the background behind ongoing initiatives — not just the current state

GitLab's rule: if it's not written down, it didn't happen. Applied to management: if a remote member could not have known this from written sources, the process failed them.

```
After every significant meeting or decision:
"[Decision summary] — on [date], we decided [what] because [why]. 
[Name] owns the next steps. Full discussion context in [link]."
```

### 3. Create equitable meeting participation

In hybrid meetings (some in-room, some remote), the default dynamic is that in-room participants dominate and remote participants go silent.

**Structural fixes:**
- **One device per person, always**: if anyone is remote, everyone uses their own device — no conference room "speaker blob" — this equalizes audio and visual presence
- **Chat-first for questions**: use meeting chat for questions; designate someone to monitor and surface chat questions verbally
- **Equal turn-taking**: the facilitator explicitly calls on remote participants: "Before we move on, let me hear from [remote member] — what's your take?"
- **Camera norms**: set explicit team norms (cameras on when presenting, discretionary otherwise) — inconsistent norms create inequality

For fully asynchronous participation: record key meetings, share the link and the decision made, and create a time-limited window for async comment before the decision is final.

### 4. Build relationships deliberately

Spontaneous relationship-building does not happen remotely. It requires deliberate structure:

**One-on-ones**: increase frequency slightly for remote reports (30 min weekly minimum); include non-work connection at the start of each; this partially compensates for the missing social texture of co-location.

**Virtual coffee / informal pairing**: optional, time-limited (15–20 min) informal calls with no agenda. Make it genuinely optional — forced fun is worse than no fun.

**Team rituals**: recurring lightweight touchpoints that build team identity: a weekly async prompt ("share what you're working on or something non-work"), a shared team channel for non-work content, a team retrospective that includes a social element.

**In-person time**: even fully remote teams benefit from 1–2 annual in-person gatherings for relationship depth that video cannot replicate. Focus in-person time on relationship-building and complex collaboration, not status updates.

### 5. Actively counteract proximity bias

Proximity bias is the systematic tendency to evaluate and promote those who are physically visible more favorably than those who are not. It is unconscious and pervasive in hybrid environments.

**Counteractions:**
- In performance reviews: for each assessment, ask "how much of this is performance evidence vs visibility?" Require evidence that is equally accessible to remote and in-office members (written deliverables, project outcomes, documented contributions)
- In recognition: remote workers are less likely to be recognized spontaneously; build a habit of explicitly recognizing async and remote contributions (see `give-employee-recognition`)
- In promotion decisions: calibrate for the bias explicitly — ask "would we assess this person the same if they were in the office 5 days a week?"
- In meeting facilitation: track who speaks in meetings; if in-office members dominate, adjust facilitation

### 6. Set explicit working norms

Distributed teams need explicit agreements that co-located teams develop implicitly:

```
Working agreement (example):
- Core overlap hours: 10am–2pm [primary time zone]
- Response time expectation for async messages: within 4 business hours
- Calendar: keep calendars up to date; indicate focus blocks and offline time
- Camera: cameras on for all-hands and team meetings; discretionary for 1:1s
- Documentation: decisions documented in [shared tool] within 24h
- Emergency contact: for urgent issues outside working hours, [channel/method]
```

Review and update these agreements quarterly; what works at team size 5 breaks at team size 20.

## Rules

- Async-first by default — synchronous time is a scarce resource reserved for high-bandwidth needs; do not schedule a meeting for information that can be written
- If it's not documented, remote members don't have it — every decision, context, and social norm that travels verbally in person must travel in writing for remote teams
- One device per person in hybrid meetings — conference room blobs create first- and second-class participants; equalize the experience
- Actively counteract proximity bias in performance and recognition — it will occur by default without deliberate correction
- Remote members are not working from home as a privilege; they are working remotely as a team condition that requires deliberate management

## Common Mistakes

- **Running in-person management practices with remote participants added**: brief at the start of meetings, no async follow-up, no documentation — remote members get 40% of the information in-office members have.
- **Treating async as slow**: async communication feels slow because you're used to instant responses; the actual speed gain is in parallel work — while you're sleeping, work is moving forward.
- **Over-scheduling video calls to compensate for distance**: 8 hours of Zoom per day is not proximity; it is exhaustion; reduce meeting load, invest in better async tools.
- **Ignoring time zone asymmetry**: scheduling all recurring meetings in the same slot permanently disadvantages someone; rotate the burden, or replace meetings with async equivalents.
- **Proximity bias in "high potential" identification**: the employees most likely to be identified as high potential are those most visible to leadership; in hybrid environments this is almost always the in-office employees.

## When NOT to Use

- For teams working on genuinely synchronous collaborative work (live surgery, physical manufacturing, real-time trading) — some work requires co-presence; distributed practices cannot substitute for physical coordination.
- As a substitute for addressing a fundamental trust deficit between manager and team — if the underlying issue is that the manager doesn't trust remote employees to work, distributed practices will not fix the relationship; that requires direct conversation.