4 ms·
> A lot of work has disappeared into Slack DMs instof channels, visibility lost there. We announce DM stats in our monthly company meeting. Our goal is everyth
by matwood 7y ago
> A lot of work has disappeared into Slack DMs instof channels, visibility lost there.
We announce DM stats in our monthly company meeting. Our goal is everything in a public channel unless it absolutely is a private matter.
> something you get for free when you are all physically in the same place.
But did you really? Were all those conversations documented? What I realized is that many conversations end up being around what was talked about and what was the decision made X months ago. Many other conversations were around communicating said decision to someone else or someone new. All these telephone game style conversations go away if you can forward someone an email chain.
- moorhosj 7y agoI’ve never run into a colleague from another department on an email chain. It happens frequently in our office kitchen. I don’t that that, or the ability to simply walk over to someone’s desk should be discounted.
- wolco 7y agoWorking in a bigger place you may not have the same physical access. The smaller the place the more opportunity for cross department chatter remote or in person.
- deleted 7y ago[deleted]
- patagonia 7y agoYeah really. That’s called documentation. Some of my ideas are dumb and a waste of time. They don’t need to be documented to suggest to some future person they need to waste their time reading through to get to the point. If anything productive comes out of the conversation it should be documented. Including how decisions were made in some instances. But I don’t want to read through banter and try to decipher what someone meant out of context years later because all I have is a Slack convo that was a “conversation” not “documentation”. In conversation I have certain expectations of the known context and background the person I’m speaking with is aware of. When writing documentation those details are different. Conversation logs are not documentation. I would argue an email forwarded to me out of context has a higher risk of telephone game style error introduction than properly written documentation. Also in person there is a lot of non verbal, non explicit communication. That is mostly lost.