Background: SkySQL is a distributed company. Nearly all of us work from home. To be productive, we need to emulate the best aspects of collaborating as if we were working next to one another. Given that nearly all of us had worked under similar distributed conditions at MySQL AB, we knew what we were getting into when we were founded. Obviously, we wanted to learn from our past experiences when making our choices for tools and processes. In my last blog entry related to our lessons on collaboration and communication, I went discussed some email configuration issues. This time, I turn to document sharing.
Our top learnings from two years of Google Docs?
- Google Docs relieves a lot of the pain from sharing attachments. It's worth using.
- Colleagues working on the same GDoc during a meeting cuts a lot of review cycles short. It's a great relief.
- Native Google Docs do not consume space from your storage quota, while any other format does. So if you have legacy documents it is wise to take the time to convert or at least decide how important they are.
- Naming conventions for GDocs require re-education of old habits.
- Document lists and searches of Google Docs are incomplete and hence buggy, which creates frustrations.
- A Google Sites intranet page by topic, with index pointers to relevant Google documents, makes it easier for everyone to find what they're looking for. Such index pages centralise the maintenance of document lists and work around Google Groups bugs.