Managing a Remote Team

Async-First Communication Culture

The async-first rule has one concrete expression: before you ask a question in Slack, search Notion. If the answer exists in documentation, reading it takes two minutes and produces no interruption. If the answer doesn't exist, you ask the question, get the answer, and then write it in the documentation immediately — so the next person never has to ask. Without that second step, the team accumulates a Slack history that nobody can search effectively and a documentation system that everyone stops trusting.

The "written before meeting" principle follows from the same logic. Every meeting has a pre-shared agenda document, distributed at least 24 hours in advance. Attendees arrive having read it. The meeting itself is for decisions — not updates, not context-setting, not status reports. GitLab operationalises this at company scale: its entire remote handbook is public at gitlab.com/handbook and covers everything from how to run a 1:1 to how to handle a board meeting. It's the most detailed reference available for remote culture, and it's free to read.

Documentation Discipline

Documentation rot is the most common failure mode for remote teams. It starts when people update Slack threads instead of docs, and within six months, new hires spend their first week asking questions that have been answered fifteen times in conversations nobody can find. The fix is to treat documentation as a first-class engineering artifact: it has an owner, it gets reviewed, and it goes stale on a calendar schedule rather than silently.

Structure your documentation in three layers: process docs (how we do X), decision logs (why we chose X over Y), and reference docs (what X does). Confluence and Notion both support this structure, but the tool matters less than the habit. Every time a question is answered verbally in a meeting or async in Slack, the answer should be in documentation within 24 hours. Teams that enforce this for 90 days stop having the same conversations repeatedly.

Tool Stack

The minimum viable tool stack for a remote team of two to twenty people is four tools: Slack for synchronous-ish communication, Linear for task management, Notion for documentation, and Loom for async video explanations. Anything beyond this — Jira, Confluence, Monday.com, Asana, Microsoft Teams — adds coordination overhead without proportional benefit at early stage. The goal is for every team member to know where to find information without asking, and for there to be one canonical place for each category.

Loom deserves particular attention because it eliminates a category of meeting that wastes enormous time: the "let me walk you through this" session. A five-minute Loom recording of a new feature, a bug explanation, or a code review context can replace a 30-minute meeting and be watched at 1.5× speed by someone in a different timezone. For US plus Europe overlap, the workable synchronous window is approximately 14:00–17:00 UTC; block those hours for the rare real-time collaboration, and protect the rest of the day for deep work.

Goal Tracking Without OKR Overhead

OKRs work at scale; at ten people, the quarterly planning ceremony and grading rituals can consume more energy than the goals themselves. A lighter alternative: one shared document listing three to five company-level priorities per quarter, each with a single measurable outcome and a named owner. Update it weekly with a confidence score from 1 to 10 per priority. That's it — no key result grading rubric, no cross-functional alignment spreadsheet.

The 90-day check-in cadence helps remote managers build trust without micromanaging. For the first month with a new hire, run weekly 1:1s of 30 minutes each. In month two, move to bi-weekly. From month three onward, monthly is sufficient if the person is performing well. This cadence gives new employees the support they need during onboarding without signalling that you don't trust experienced contributors to manage their own time. The 1:1 agenda should always include one personal question and one career-development question, not just project status.

Frequently Asked Questions

How do you build culture in a fully remote team? Culture in remote teams comes from consistency of behaviour, not from offsites and Slack emoji. It's built through predictable communication norms, transparent decision-making, and genuine acknowledgment when someone does exceptional work. One high-quality annual in-person gathering can reinforce the culture, but it can't create it from scratch.

How do you handle timezones that don't overlap at all? For fully asynchronous teams with zero timezone overlap, every decision needs to be made in writing and documented before being communicated. Establish a 24-hour response window as the default expectation. For urgent decisions, designate a decision-maker rather than waiting for consensus. Basecamp has operated this way for over a decade and documented the approach in their book "It Doesn't Have to Be Crazy at Work."

What metrics should I track for remote team health? Track four things: cycle time per task (measures productivity), number of unplanned Slack pings per day (measures documentation quality), 1:1 satisfaction scores (measures manager effectiveness), and retention over rolling 12 months. None of these require a sophisticated HR system — a weekly survey with two questions per person is sufficient.

How do you onboard a new remote hire effectively? Prepare a written 30-60-90 day plan before the hire's first day. On day one, they should have access to all tools, a list of ten documents to read in order, and one small shipped task to complete by end of week one. Early momentum matters disproportionately in remote environments because there's no physical proximity to accelerate bonding.

When does a remote team need to meet in person? Annual full-team gatherings are the minimum. Beyond that, in-person time is most valuable during three moments: when starting a major new initiative, when a relationship is under friction (a conflict that's hard to resolve in text), and when recruiting a key hire. Spending $10,000 on a quarterly in-person meeting is cheaper than one bad hire made remotely.