Managing Distributed Teams

Async-First Is a Discipline

Async-first does not mean "no meetings." It means meetings are the exception for synchronous decisions, not the default communication channel. Every decision that can be made in a document, RFC, or Linear comment should be made there. This creates a written record, includes people across time zones, and forces clearer thinking than a rapid-fire Slack debate.

GitLab runs a 2,000+ person company almost entirely async. Their handbook is public and contains thousands of pages. You don't need to go that far, but the principle holds: if it's not written down, it didn't happen.

The Golden Window

When your team spans US Pacific and Central European time, you get roughly four hours of overlap (roughly 9am-1pm CET / 12am-4am PT, or more practically 5pm-7pm CET / 8am-10am PT depending on flexibility). This window is precious. Use it for pairing sessions, design discussions, and 1:1s. Never waste it on status meetings that could be a Loom video or a written update.

Block the overlap window on team calendars. Make it explicit that this is when synchronous collaboration happens. Everything else should work async.

Documentation as Default

In distributed teams, documentation quality directly determines team velocity. Every project needs a one-pager before work starts. Every architecture decision needs an ADR. Every process needs a runbook.

Use Notion or Confluence as the source of truth, not Slack. Slack is for conversation. Documents are for decisions. When someone asks a question in Slack that requires more than two sentences to answer, the answer should go in a document with a link posted back to the channel.

Onboarding documentation is the canary in the coal mine. If new hires struggle to get productive in their first two weeks, your documentation has gaps. Track time-to-first-PR as a metric.

Building Trust Remotely

Trust in distributed teams comes from three things: reliability (doing what you said you'd do), transparency (sharing context proactively), and presence (being available during agreed hours). You cannot manufacture trust through virtual happy hours or icebreaker games.

Invest in annual or bi-annual in-person offsites. Two to three days together, focused on relationship building and strategic planning, creates enough social capital to sustain months of remote work. Budget $2K-$4K per person per offsite. It's the highest-ROI spend in your team budget.

Avoiding Second-Class Syndrome

The moment someone in the office turns to a colleague and makes a decision that affects the remote team, you've created a two-tier system. Prevent this by establishing a rule: if one person is remote, everyone joins from their laptop. No conference room hybrids where remote participants stare at a blurry whiteboard.

Tools matter. Linear for project tracking. Notion for documentation. Loom for async video updates. Slack with disciplined channel usage. Figma for design collaboration. Pick tools that are remote-native, not tools designed for co-located teams with a remote bolt-on.