|
The implied expectations here are part of what bothers me so much about Slack. The people who really embrace it are putting too much of the burden of communication on all recipients instead of on themselves when they produce content. It is selfish and inefficient since every recipient has to do the same redundant work to sort it out. Careless mixing of realtime chatter, async memos, and reference documentation leads to a fear of missing out. You have to wade through a stream of junk to see if you missed something important. Eventually, people even expect you to know the whole stream whether you were present or not. How mad! If something important happened during your vacation, someone in your organization should tell you about it once you return. Otherwise, you should return to a clean slate, only tracking the chatter that happens while on duty. In the best recent office cultures I've seen, instant messaging is used without history. It's water-cooler banter or popping your head in the next office. Important but still transient things can go in email and be read a week or two later when you return, but there aren't so many of them. And stable things go in a wiki, not in email, i.e. if subsequent new hires are supposed to know about it too. Nobody should be onboarded by telling them to crawl through transcripts of previous work weeks, and a proper vacation lets you return as if you are onboarding. By the way, early in my career, these same types of careless people abused email the way they abuse Slack today. Busy people dealt with hundreds of emails in a day, not counting spam nor automated notification messages, which weren't so common then. Your inbox would be flooded with realtime chatter, async memos, and attached documents that should have been in a repository somewhere. Eventually, those with enough clout were driven to set auto-reply messages that they are on vacation and no email received during their absence would ever be read. |