4 ms·
> Is there a product for slow-thinking updates where I can share teams news and align my +40 people team? Email. Email is perfect for this. If you use GSuit
by jedberg 8y ago
> Is there a product for slow-thinking updates where I can share teams news and align my +40 people team?
Email. Email is perfect for this. If you use GSuite, groups with the email gateway is ideal for this. You can have threaded discussions with a long history.
Stripe was(maybe still is?) really good at this. They made a policy very early on that every email had to CC a mailing list (unless it was truly a personal one on one communication). The lists has a structure were some were designated as archival only. Even if no one read the list, at least the archive was there for the new employees. Or for an employee who was on vacation to read and catch up when they came back.
> How can you be sure people don't actually miss things in the noise of Slack/Email?
For Slack, make sure it's truly just for real time discussion. If something looks like it's going to be a long discussion, move it to email.
For email, if you're using groups/lists for everything, then there shouldn't be a lot of noise. You should be able to just go to the groups interface or filter on the group the message was sent to.
- codemac 8y agoEmail is great, along with keeping a google doc of all previous updates sent in reverse order. Then author the email in the google doc, paste it into gmail and send - along with a link at the bottom to previous notes.
- james_at_plaid 8y agoBecause I want to encourage comments/questions, I do almost what you describe, except that the email ONLY contains a link to the doc. So in effect, the email is just a notification that the doc has been updated.
- codemac 8y agoI don't do that because then you're just giving the reader more work to do. Is there an unseen advantage to not including the actual text in the email?
- twunde 8y agoThis is super-important, especially for when someone is on vacation or when new hires come onboard and want context. We use Confluence this way and have engineering/team updates in there going back since the company was less than 10 people. It's super-useful when someone is trying to find the original reasoning about why a company does something one way vs another. I will say that this should be in whatever internal documentation system you use, whether that's a wiki, Google Docs, etc. The main thing is that it should be searchable and easily found.
- chadwittman 8y agoI like this concept, but man that's expecting a lot from an entire organization.
- tootie 8y agoInteresting. My first job in like 2000 or so used Outlook groups for this. It was basically a private usenet sort of thing. Worked fantastically well.