Re:Slack's bait and switch
by dalbasal on Monday March 12, 2018 @02:55PM
(#16570435)
This comment is on the money.
"..just plain refuse (are unable?) to even see the difference between a chat like slack. ...the user experience will be a different one."
Underlying this is (unusually) a way some technical people think, and the way most bureaucracies think. Bureaucracies will often "checklist" requirements, see that it does all the things "users have identified as important," use cases they think these apply to and go on that information alone. They only consider stuff that is tangible & legible.
By that checklist method email, whatsapp, Twitter, slack are IRC and such are essentially the same. Some may tick a.minor box that the other does not, but basically they all get messages from A to B (sometimes to B, C & D).
It's even worse in this case, because slack is social software and the conventions people form as users are very impactful on the UX. This compounds differences.
"..just plain refuse (are unable?) to even see the difference between a chat like slack. ...the user experience will be a different one."
Underlying this is (unusually) a way some technical people think, and the way most bureaucracies think. Bureaucracies will often "checklist" requirements, see that it does all the things "users have identified as important," use cases they think these apply to and go on that information alone. They only consider stuff that is tangible & legible.
By that checklist method email, whatsapp, Twitter, slack are IRC and such are essentially the same. Some may tick a.minor box that the other does not, but basically they all get messages from A to B (sometimes to B, C & D).
It's even worse in this case, because slack is social software and the conventions people form as users are very impactful on the UX. This compounds differences.