Holloway
Remote Work

You’re reading an excerpt of The Holloway Guide to Remote Work, a book by Katie Wilde, Juan Pablo Buriticá, and over 50 other contributors. It is the most comprehensive resource on building, managing, and adapting to working with distributed teams. Purchase the book to support the author and the ad-free Holloway reading experience. You get instant digital access, 800 links and references, a library of tools for remote-friendly work, commentary and future updates, and a high-quality PDF download.

Remote Work≫Part I: Foundations≫Practices of Successful Remote Teams≫

  • Asynchronously available. Ideally, your practices will make it abundantly clear to all members of the team where they can find information, regardless of the specific tooling that is selected by the company.

Anita Umesh
This and the point below this are such important points. But what about knowing which document is current/relevant/not obsolete -- especially for those documents that don't require regular updating, i.e., for those documents that may have been written/updated months or years beforehand but are still relevant? How to address those?
Kathleen Vignos
Reducing the number of tools used for documentation is a good idea. Larger companies sometimes scatter documentation across many tools like wikis, Google docs, Dropbox, and github. Simplicity and consistency of tools across teams is best.
Kathleen Vignos
Regularly updated - but also regularly pruned. Stale docs with superseded information should be deleted or marked as "deadwood." This doesn't tend to happen naturally (for example, people leave companies and old content gets left behind). It creates a lot of confusion and needs to be actively managed.
Your comments and feedback help improve this resource. Comments are reviewed by editors and may be published for all readers or incorporated into future updates.
Share this discussion