[titraprutr]

I don't think this will necessarily help. In my experience some people who use Slack consider responsiveness as getting an answer right away. This isn't that different from coming and asking directly - it still interrupts your current thinking process.

More important is to understand how async communication works. Otherwise, you have to create a physical boundary (remote work) to enforce this.

[dasmoth]

In my experience some people who use Slack consider responsiveness as getting an answer right away.

That's why I still fundamentally prefer e-mail (with a sensible set of mailing lists and an easily browsable archive) for serious decision making. IRC or Slack are great for building a community atmosphere but best reserved for more ephemeral things.

[briandear]

I fundamentally prefer Slack. I don't have threads of various conversations spread across multiple emails and replies, I also don't have to remember to add someone to a email thread, for example.

Also anyone that needs to be in a conversation is in the Slack already. File sharing, code sharing -- all that is much easier than email. With Threads -- conservations are more focused and organized. In-chat images are also super simple (as opposed to sharing actual images or links to images that require clicking as in email.)

I despise email and hate phone calls even more.

I think the 'problem' with Slack is how some people use it. The 'expectation' of a quick answer isn't Slack's fault.