101–110 of 162 posts
Earlier quoted context omitted.
To the parent's point, how do you get a future employee to receive the information in an email that was sent before they started?
You include it in their onboarding
We use an internal forum in addition to chat. Anything substantive goes in the forum. We'll regularly reference 5 year old posts.
Earlier quoted context omitted.
You include it in their onboarding
So 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?
Doing everything in chat is pure insanity. It's great for the day-to-day collaborating on projects... but it's all short-term memory. Are you going to be referencing a chat from 3 years ago? We use an internal forum in addition to chat. Anything substantive goes in the forum. We'll regularly reference 5 year old posts.
Doing everything in chat is pure insanity. It's great for the day-to-day collaborating on projects... but it's all short-term memory. Are you going to be referencing a chat from 3 years ago? We use an internal forum in addition to chat. Anything substantive goes in the forum. We'll regularly reference 5 year old posts.
Earlier quoted context omitted.
You include it in their onboarding
So 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?
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.
I feel that many of these objections already have solutions within Slack. If you don't want to be disturbed by notifications, there is the Do Not Disturb option to snooze notifications. If you don't want to lose context, use Slack threads, which localize discussion around an issue to a single place. If you have a fear of missing out because you're piping everything to Slack - have you considered segregating your aler…
Doing everything in chat is pure insanity. It's great for the day-to-day collaborating on projects... but it's all short-term memory. Are you going to be referencing a chat from 3 years ago? We use an internal forum in addition to chat. Anything substantive goes in the forum. We'll regularly reference 5 year old posts.
If you can reference 5 year old forum posts why can't you reference 3 year old chat conversations?