Hacker News Reader

Comment by nevinera | Hacker News Reader

I'm sure there's a substantial population that this redesign was successful for, but it's nobody I've talked to.

I can no longer tell which of my slacks has pending messages at a glance, and my actually important channels' notifications are hidden in a sea of irrelevant ones when they used to be the only attention-attractors on the interface. I gather that you think the list of people and channels is just one aspect of your lovely platform, and we should use the other interfaces like "DMs" and "Reactions" too, but .. that list is the core of your interface, please stop hiding it every time I do anything.

View on HN

> Operationalize transparency to build alignment

Hold up there, I can't drink that fast.

What he means is that the turboencabulator rotospectrometer has reached a level of synergy unseen in 15 sigmas. The board is pleased.

The change in the mobile app where pulling down on the channel list focuses a search box and opens the keyboard is quite jarring too, especially when that UX generally means 'get me the lastest updates'

Holy insufferable change, Batman! Why?????

Because when you have 500 devs, they have to build _something_. It's why every single good software product bloats to become a slow, confusing, mess of features.

Software development feature entropy is the 4th law of thermodynamics.

> I'm sure there's a substantial population that this redesign was successful for, but it's nobody I've talked to.

I think the measurement of success in this case has less to do with the customer's feelings about the product and more about people understanding and using the full feature set of Slack. All the new features they've been adding in just kind of floated by and we never used them. Either they were embedded in the middle of a series of steps we already had habits around (so we just ignored them) or they were so subtle that we didn't see the point in trying them out.

In other words, the problem they were really trying to solve was around scaling the product with all the features they had. That's likely where measurement of success will take place.

In other words, the new features are not something the users were looking for.

Instead of admitting adding new features just for the sake of adding new features, they want to force them into the faces of users still not wanting to look for them

Reply on news.ycombinator.com