Slack Thread Cost

Quantifying time wasted on work chat apps

I've been using Slack pretty much every day since like 2016 when I was first introduced to it at an agency I was working at. It's a powerful tool and has continued to evolve over the past few years especially.

One of my favorite recent features is the "huddles" button where you can do quick voice chats. Did you know if you stay on long enough after someone leaves a huddle some light jazz starts to play? It's awesome.

Anyways, seeing Twitter's recent experiments with showing view count and other metrics on a Tweet detail page got me thinking about how the construct of showing views might get implemented into other apps.

So what if Slack showed a threads view count, average time spent reading, and did a rough estimate of the effective cost any given thread created for the company in terms of billable hours?

My hypothesis is that the number might be a) wildly inaccurate and b) alarmingly large. I know from personal experience notification management and the context switching caused by Slack can be harmful to your productivity if you aren't able to manage it well.

However, I doubt this would ever get implemented as it might lead to companies ditching Slack in lieu of something less time-consuming.

Well hi there! My name is Soren. I make satirical app designs daily.

Follow along by clicking the subscribe button below.

 

Reply

or to participate.