we use the group chat the same way as texts. There is an understanding that there is no requirement to respond instantly (or at all!). It is an announcement platform with implicit understanding it is not work related. You want to discuss something work related, you use email.
>You want to discuss something work related, you use email.
This pattern is the inverse of what I see as best practice: _email_ is the announcement (notification) tool, and then when discourse is needed move to "pro chat," something with logging, powerful search, so forth.
An email thread locks knowledge in the thread and it's hidden from the team (at least until someone in the thread fwds it on).
Comments
we use the group chat the same way as texts. There is an understanding that there is no requirement to respond instantly (or at all!). It is an announcement platform with implicit understanding it is not work related. You want to discuss something work related, you use email.
This pattern is the inverse of what I see as best practice: _email_ is the announcement (notification) tool, and then when discourse is needed move to "pro chat," something with logging, powerful search, so forth.
An email thread locks knowledge in the thread and it's hidden from the team (at least until someone in the thread fwds it on).