4 ms·
Slack is a bullshit product. Same goes for the rest of its ilk. Work doesn’t happen in Slack. Something I started doing with $JOB-1 was to write a “Working wi
by rufius 4y ago
Slack is a bullshit product. Same goes for the rest of its ilk.
Work doesn’t happen in Slack.
Something I started doing with $JOB-1 was to write a “Working with rufius” document and share it with the broader org (in slack profile or intranet profile). One of the things I provide is an SLA on responding to communication. It roughly looks like:
- phone call - synchronous
- email - if I am directly on to-line, response by end of next business day
- slack/teams - hours to never
I basically only answer slack if I’m paying attention to it for whatever reason. My typical work schedule has me open it 3 times a day - once in the morning, once after lunch, and once about 30 mins before I end my work day.
The other thing I note is I don’t make decisions in slack. Decisions happen in documents or worst case, email. Something durable.
That “Working with” doc has done wonders for setting expectations with coworkers. I’ve gotten a lot of feedback from coworkers as well that they appreciate it and have created their own.
- LocalPCGuy 4y agoWork can absolutely happen is Slack if that is how your team uses it. Decisions can be made (and are then documented and can be referenced later, as long as your org pays for it, which they should if they expect it to be used for business/work and not just for random conversations. It's plenty durable if paid, but if it wasn't paid, I'd seriously consider one of the alternatives, even if slightly worse in some ways, of it keeps full history. My "working with" would be almost the exact opposite of what you list (I like that idea though!). I tell people emails may get checked daily at best. We don't have a phone culture, we use huddles or video calls for synchronous conversations, but they do suffer from lack of documentation or note sometimes.