Historically, people in the workplace have relied on accessing the knowledge of others via questions in order to continue working.
When you are asking a colleague a question, you are essentially requesting a service of them. As we all know, services are inherently less scalable than products as it takes time to provide a service and time is a finite resource.
This started as face-to-face interactions, which was somewhat sustainable. We then moved to telephone, then to email and now chat. At each stage the frequency of communication has increased exponentially to the point that most of us now face a near-continuous stream of messages from colleagues throughout the day (Slackosis, I call it).
This is a killer for productivity in all companies but particularly remote organisations due to the added barriers to synchronous communication e.g. timezones, scheduling calls etc.
Enter: the ugly duckling, documentation.
Doubling down on documentation is no small feat. It can be tedious, particularly while you and your team are forming the habit of documenting everything, but it is the only way to create a scalable environment of knowledge transfer to allow your remote team to function autonomously.
Building the framework for teams to start generating structured documentation that is engaging for the reader is one of the main things I work on with clients. If you feel like this is something you need help with, feel free to get in touch.