![]() ![]() ![]() ![]() Once you start making Slack the center of communication, you stop making deliberate decisions about who is included in e-mails/meetings. Don't be afraid to schedule a synchronous communication session in whatever flavor you prefer. It's terrible for coordinating and making important decisions in a timely manner, though. Casual, asynchronous chat is great for low-importance conversations that aren't time sensitive. It's great for impromptu discussions with a lot of back-and-forth, but once it becomes a serious conversation with multiple parties you need to escalate to a call or meeting or e-mail. Slack shouldn't be replacing e-mail or meetings or phone calls. Email inboxes were more or less reserved for broadcasts from exec and HR along with JIRA spam. > For the next five years I operated in “Slack culture”, the communication paradigm that I suspect is in use by many companies these days. Which shows another interesting aspect of Slack-type culture. Are you a good team member if people are asking questions and you are not answering?įor contrast, I found out that many people I worked with are too lazy to write an email and will prefer to solve the problem themselves rather than write to me if I don't answer soon enough. Sure, you can pause notifications - but you know people are waiting. But when companies use Slack, they integrate it as a part of the culture. I'm not interested in engaging in a conversation at all unless there is something really extremely important that requires my undivided attention for a specific period of time. That is, after you "come back" from a meeting or being away, you can't just work in peace and when you want just send a reply: no, you are expected by design to engage in a conversation. Set and communicate your boundaries, and in a team that respects each other, it shouldn't be a problem.Īll the options you mention are designed in order to reduce the main problem: that it requires synchronous communication. Which also requires that you don't "check in" while you're on vacation, because if you do, then other people will feel like they're expected to as well. That includes not calling or pestering people that are on vacation. Part of being a professional is setting boundaries, communicating them, setting the expectations that the rest of your team will do the same, and of course, respecting those boundaries. Some people where I work book meetings with themselves to guarantee focused distraction-free time. to pause notifications for an hour or whateverĪll of that is just Slack itself, in addition to things like putting meetings and vacations and other appointments on the shared team calendar. that you're on a call or in a meeting etc. This doesn't really sound like a problem with Slack, but rather a personal or cultural problem with a lack of setting or respecting boundaries. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |