Yeah 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.