- 18F / TTS : https://github.com/18F/handbook and https://handbook.tts.gsa.gov
- BaseCamp: https://github.com/basecamp/handbook
- CivicActions: http://handbook.civicactions.com
- GitLab: https://about.gitlab.com/handbook/
- Loomly: https://www.slideshare.net/thibaudclement/loomly-culture-code-2019-137054962
- Truss: https://guide.truss.works/#practice-distributed-first
Most companies have some form of an employee handbook. These are usually handed out to newhires during onboarding/orientation, put on a shelf and rarely looked at again. Later, when the handbook is updated, new hires get the updated handbook and sometimes pre-existing employees are told about these updates in separate emails. This quickly means that different humans have different understandings of how to get things done. You know this is happening in your organization when people rely on folklore to figure out how to get things done, asking nearby coworkers with longer tenure, unaware that those well-intentioned coworkers may actually be answering with out-of-date information.
For physically distributed organizations, this approach simply will not work. Instead, these employee handbooks have to be accurate, concretely actionable with the latest version available to all employees all the same time in a well known location.
These “employee handbooks” or “playbooks” are the SingleSourceOfTruth for how to get things done within the organization. Learning your way around this handbook is an essential part of onboarding – but once you know your way around the handbook, you can find answers to questions yourself, and can easily propose updates/fixes as needed to keep it accurate as business operations change.
Posted in a well-documented location, these are equally visible to all employees all the time, so new hires and pre-existing employees all see the same identical document. They are full-text-searchable for speedy answers to questions. They are posted in a format that allows for anyone to suggest edits/changes, and for specific humans to review/approve those proposed changes – this process reduces the maintenance work of keeping the document uptodate, and helps ensure that the document is written in language that all humans understand. Some companies take this one step further and publish the document so it is visible even to those outside the company.
I’ve gathered these publicly-visible handbooks here into one list, in case it is helpful to anyone starting a distributed organization. These playbooks were intentionally made public so you can copy and adjust to your own specific needs. Of course, give credit back to where due!
Finally, if you know of any other playbooks that you think I should add here, let me know and I’ll update this list.