![]() ![]() Sooner or later, it will leak that some people talk about a project in direct messages - others will fell left out of the conversation. Whatever happens in direct/private messages is not visible to others in the team. The main thing is the problem with transparent communication. No direct/private messages related to work, use channels- Andrzej Krzywda AugWhy is this a problem? ![]() There are other types of conversations which might be fine keeping secret and hidden from others, if really required. In this post, I’m focusing mostly on project-related communication - where I believe all the team should be up to date. I believe it’s mostly about not being aware of the consequences. My criticism towards direct messages doesn’t assume bad intents from the initiatiors of such conversation. ![]() I talk about it from the perspective of a remote/async/distributed team, but I suppose some problems are similar to in-office teams. I thought it would be nice to describe the problem and find some solutions. At Arkency, we avoid them at all costs, but we also see how hard is to change our client teams habits, sometimes. There’s something about using direct messages (project related) that developers find uncomfortable. Use channels, not direct messages - 9 tips ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |