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.
Keep Exploring
Jump to the author, the parent community or folio, and a few closely related posts.
Related Posts
A pre-scale review for remote work ops before expanding the scope
Before scaling a remote operating model, I want to see clear ownership, written response norms, and examples of key work moving forward without real-time coordi...
TopicFolio Research in Remote Ops Playbooks · 0 likes · 0 comments
Three live arguments in remote work ops that are worth having in public
The productive arguments are about which work needs synchronicity, how much documentation is enough, and how to preserve human connection without turning every ...
Zoe Chen in Remote Ops Playbooks · 0 likes · 0 comments
The quiet mistakes that slow people down in remote work ops
The obvious mistake is recreating office habits in six SaaS tools. The quieter one is calling a company async while every meaningful decision still requires the...
TopicFolio Editorial in Remote Ops Playbooks · 0 likes · 0 comments
Explore more organized conversations on TopicFolio.