4 ms·
Almost agree, but email should also be treated as lossy. It drives me crazy when people send mass company emails with, for example, new policy or forms attache
by gregmac 8y ago
Almost agree, but email should also be treated as lossy.
It drives me crazy when people send mass company emails with, for example, new policy or forms attached, and don't post them elsewhere. New hires only see them if someone remembers they exist and forwards them, plus it's impossible to figure out current state without spending a bunch of time playing email archeologist.
- personjerry 8y agoEmail is generally regarded as the most reliable in my experience.
- rabidrat 8y agoTo the parent's point, how do you get a future employee to receive the information in an email that was sent before they started?
- fsiefken 8y agoExchange has so-called "Public Folders" you could also access through IMAP, but it was more convenient to use and search with Outlook. Conceivably you could make a similar 'public' maibox on a different mail platform, a poor man's newsgroup.
- personjerry 8y agoYou include it in their onboarding
- rabidrat 8y agoSo now you have to store each email that includes important information in a second place, so that you remember to include it in their onboarding. Why not just post it to the intranet in a well-known location in the first place?
- personjerry 8y agoOnboarding does not necessarily have to be email. However, let's not conflate onboarding with regular communication.
- addicted 8y agoIdeally the information goes where it’s supposed to in your permanent knowledge repo. This could be a wiki, a website, etc. The email is sent as a notification that the content has been added, updated or moved. Email should ideally serve as a notification system and a lossy communication system where things you want to retain need to be backed up somewhere else. The nice thing wth email is that being an open eco system there are a lot of integrations that are supported easily.
- rabidrat 8y agoRight. But too often, as gregmac said, "people send mass company emails with, for example, new policy or forms attached, and don't post them elsewhere". Email should be used for notification and ephemeral communication, and not for information dissemination. In that way it's the same as chat.
- u801e 8y agoAn internal NNTP server would work better in that aspect when compared to email.
- SnootyMonkey 8y agoShameless plug here, but this is exactly why we built Carrot ( OSS / SaaS https://carrot.io/ https://carrot.io/ ) We've been remote founders and employees in numerous distributed startups, and have always found the same issue, the noisy nature of chat/Slack and lossy nature of email necessitates a 3rd place to keep the important decisions, announcements and history of the company. Lots of companies use wikis and forum software for this, and those can work, but we're betting that a dedicated solution can work better.