Thanks for sharing your guidelines. > Review and edit messages before sending Part of the joy of Slack is that sending messages to your team is super low-fric

Thanks for sharing your guidelines. > Review and edit messages before sending Part of the joy of Slack is that sending messages to your team is super low-friction so more people are likely to contribute. The example use case is "I have this thought-through proposal I'd like to do. Is it okay with you." In this case it makes sense to review more thoroughly before sending in order to communicate the proposal more clearly. In other cases, you may want to engage in more back and forth as you debug something together or make a plan together. In these debugging/planning sessions, I think it’s valuable to have the full thought process of the team recorded in Slack. This unfiltered discussion might provide useful context to someone else later. I like to augment this frictionless back and forth with a summary at the end of the discussion. This makes it easier for someone other than those involved in the conversation to benefit from it. And then they can refer to the full conversation for more details. I'm one of the creators of a tool that's designed to make these summaries accessible (https://bytebase.io https://bytebase.io).