[notmainacct]

The main think is making sure that this communication is a priority, and that the people responsible for writing documentation understand the importance and write with empathy for the reader.

The other important part of information sharing is the form factor. If you have a bunch of micro-services and command line apps that drive your company, I like writing this info into the Readme, and manual pages for the programs. Then the access to information is tied to the places where they are relevant, and you can build a sense of where information 'belongs' within the team.

I've seen confluence and google docs used for these things as well, and aside from things like 'company policies and hr' and 'setting up your computer for new devs' external documentation often becomes out of date with the software faster.

Aside from long-term information sharing like this, I think that email and irc are a pretty optimal setup for 'faster' communication. Email is good for sharing something with groups in a quick time-frame, and irc is good for immediate communication. I personally do not like Slack because it straddles many different time frames for communication, and many of the fun features lead to productivity killing noise. Scrolling back to find a months old message on slack when it could have been a searchable email is not fun. I feel like IRC and the limitations keep people from both jumping on every notification, while also preventing messages from being sent/recieved if a party is offline creates a logical switch from a quick message to an email. I've found that people don't fail to respond to old emails in the same way that a direct message might get lost in the noise of slack.