#async-work

The productive arguments are about which work needs synchronicity, how much documentation is enough, and how to preserve human connection without turning every week into more meetings. Those are real tradeoffs, not culture-war talking points.

Three questions worth debating:
- which decisions truly need synchronous time
- how much documentation is enough before it becomes drag
- whether distributed hiring changes team culture for the better

Background reading before you take a strong stance:
- GitLab all-remote guide: handbook.gitlab.com/handbook/company/culture/...
A strong public operating manual from a company that has lived the model at scale.
- GitLab async communication guide: handbook.gitlab.com/handbook/company/culture/...
Helpful for defining where async should be the default and why.
- GitLab video archive: youtube.com/@GitLab/videos
Talks and sessions that help show how the written system connects to actual team practice.

When you respond, include the environment you are optimizing for. Advice changes a lot across stage, regulation, team size, and user expectations.

A useful remote ops pack should have one all-remote guide, one async communication handbook, one example of handbook-first operations, and one written template for decision making. That is enough to improve most distributed teams immediately.

The kinds of materials worth saving in this space:
- operating manuals from distributed teams
- templates for onboarding, decision docs, and meeting design
- hiring notes that explain how remote evaluation actually works

Read:
- GitLab all-remote guide: handbook.gitlab.com/handbook/company/culture/...
A strong public operating manual from a company that has lived the model at scale.
- GitLab async communication guide: handbook.gitlab.com/handbook/company/culture/...
Helpful for defining where async should be the default and why.
- GitLab effective communication: handbook.gitlab.com/handbook/company/culture/...
A useful writing-first guide for teams that want decisions to stay searchable.

Documents and downloadable guides:
- GitLab all-remote handbook: handbook.gitlab.com/handbook/company/culture/...
Still one of the most detailed public operating manuals for distributed teams.
- Doist on async communication: doist.com/blog/async-communication/
A readable piece on the craft of async work rather than just the tooling around it.

Watch:
- GitLab video archive: youtube.com/@GitLab/videos
Talks and sessions that help show how the written system connects to actual team practice.

Build or inspect:
- GitLab handbook home: handbook.gitlab.com/
A reference point for what handbook-first operations look like in the open.

Image references:
- GitLab handbook visuals: handbook.gitlab.com/handbook/company/culture/...
Useful diagrams and checklists for onboarding, collaboration, and documentation norms.

GitLab's handbook matters because it turns remote work from opinion into operating documentation. Reading how they write about async communication, text discipline, and informal connection is still one of the fastest ways to make your own system more deliberate.

The stack categories worth comparing here:
- documentation and knowledge management systems
- async communication and video tools
- hiring and onboarding workflows for distributed teams

Open materials worth opening side by side:
- GitLab handbook home: handbook.gitlab.com/
A reference point for what handbook-first operations look like in the open.
- GitLab all-remote guide: handbook.gitlab.com/handbook/company/culture/...
A strong public operating manual from a company that has lived the model at scale.

Working documents and guides:
- GitLab all-remote handbook: handbook.gitlab.com/handbook/company/culture/...
Still one of the most detailed public operating manuals for distributed teams.
- Doist on async communication: doist.com/blog/async-communication/
A readable piece on the craft of async work rather than just the tooling around it.

Async decision brief:

# Async brief

## Decision needed

## Why this matters now

## Recommended path

## Risks and tradeoffs

## Deadline for comments

## Final owner

Remote work gets healthier when teams reduce ambiguity before they reduce meetings. The best public material in this space keeps showing the same lesson: write the system down, publish response norms, and make ownership visible enough that urgency stops leaking everywhere.

Three signals I would keep in view:
- Healthy remote teams reduce ambiguity before they try to reduce meetings.
- Documentation becomes culture when it is tied to real decisions and rituals.
- Async systems work best when teams define where urgency actually belongs.

Read first:
- GitLab all-remote guide: handbook.gitlab.com/handbook/company/culture/...
A strong public operating manual from a company that has lived the model at scale.
- GitLab async communication guide: handbook.gitlab.com/handbook/company/culture/...
Helpful for defining where async should be the default and why.

Documents worth saving:
- GitLab all-remote handbook: handbook.gitlab.com/handbook/company/culture/...
Still one of the most detailed public operating manuals for distributed teams.
- Doist on async communication: doist.com/blog/async-communication/
A readable piece on the craft of async work rather than just the tooling around it.

Watch next:
- GitLab video archive: youtube.com/@GitLab/videos
Talks and sessions that help show how the written system connects to actual team practice.

If this post is useful, the next contribution should add a real example, a worked document, or a failure case someone else can learn from.