It starts with a culture where I'm not sweating the fact that I haven't checked my Slack notifications in a while.
Slack is used like a kitchen sink in the two places I've used it - there is no easy way to determine what is urgent vs what can wait. One literally has to comb through all the red dots to filter them. If you believe channels solve this because you can create dedicated channels for the important stuff, very soon someone starts abusing the responsiveness on this channel to their selfish ends, first seeking an exception, and very soon making it a habit.
To top this, the Slack UX is literally designed to maximize the time one spends with it. I often find myself on Slack intending to either -
1. Check one of the important channels or
2. Recollect something someone shared that I now need to use
And before I know it, I'm responding to something that I didn't need to at this time. I often also forget why I came here in the first place.
Yes, email and ticketing are also pervaded by spam, but Slack is essentially a corporate sponsored, culturally accepted medium for noise and distraction with no easy way to apply controls.
You typically need strong leadership to define the constraints through culture, because the tool by itself isn't designed for this.
The main reason you would want to pick such a proprietary library is to achieve a homogeneous look and feel (often behavioral UX as well) when your app must work within another product - this product/organization is usually the one that also provides the library in question, and more often than not, uses the same design system if not the library itself.
We built https://github.com/freshworks/crayons for the same reason - apps published to the Freshworks Marketplace can be built using Crayons. We also ended up building our own user facing SaaS applications using Crayons.
Slack is used like a kitchen sink in the two places I've used it - there is no easy way to determine what is urgent vs what can wait. One literally has to comb through all the red dots to filter them. If you believe channels solve this because you can create dedicated channels for the important stuff, very soon someone starts abusing the responsiveness on this channel to their selfish ends, first seeking an exception, and very soon making it a habit.
To top this, the Slack UX is literally designed to maximize the time one spends with it. I often find myself on Slack intending to either - 1. Check one of the important channels or 2. Recollect something someone shared that I now need to use
And before I know it, I'm responding to something that I didn't need to at this time. I often also forget why I came here in the first place.
Yes, email and ticketing are also pervaded by spam, but Slack is essentially a corporate sponsored, culturally accepted medium for noise and distraction with no easy way to apply controls.
You typically need strong leadership to define the constraints through culture, because the tool by itself isn't designed for this.