3 ms·

I realize that Slack is more complex then it appears, and able to do more things then it may seem. But by looking at those whiteboards and reading parts of the

I realize that Slack is more complex then it appears, and able to do more things then it may seem. But by looking at those whiteboards and reading parts of the description, the amount of effort, people and time involved in a redesign was just a bit more than I was expecting. Looking at the images of the resulting whiteboards alone had me wondering "what could all of this possibly be about?". Details within details about ... something. And then I went to check if I was even using the redesigned version, which it seems I am ... I just never noticed. I use it everyday, for chats intermixed with an occasional huddle. Those work as one expects them to, and that's about it. So in my mind it's difficult to mix "chat and huddle app" to the level of effort needed to redesign it. It seems my minimal usage pattern may not typical. I assume it boils down to there are being many customers, doing many things, it is essentially what Slack the company is, and it has to be done right. Anyway, the chat and huddle thing works fine, and I'll move on from this topic.

dkyc 3y ago
If they hadn't spent so much time, you would have noticed. That's the point. Adding features and capabilities to a without making it more complicated for users who only use a fraction of them ("chat and huddle app"), is part of why this is so complicated.
- EMM_386 3y ago
  > If they hadn't spent so much time, you would have noticed. That's the point. I get that idea ... been a software engineer for quite some time now. Users will quickly let you know how much they don't like it when you change things. It also means I should easily be able to answer all of my own questions, and shouldn't be surprised by the level of effort required. I guess it comes down to the basic cost/benefit analysis, and if the answer is "redesign", doing what needs to be done while trying limit any downside. That would include your users asking why everything just changed. I don't enjoy reading messages written in all capital letters either, where it seems those 10 exclamation marks are required to clarify how much you dislike it. Anyway, from here, based on that alone ... seems successful. Back to work and Slack messages.

dkyc 3y ago

If they hadn't spent so much time, you would have noticed. That's the point. Adding features and capabilities to a without making it more complicated for users who only use a fraction of them ("chat and huddle app"), is part of why this is so complicated.

EMM_386 3y ago
> If they hadn't spent so much time, you would have noticed. That's the point. I get that idea ... been a software engineer for quite some time now. Users will quickly let you know how much they don't like it when you change things. It also means I should easily be able to answer all of my own questions, and shouldn't be surprised by the level of effort required. I guess it comes down to the basic cost/benefit analysis, and if the answer is "redesign", doing what needs to be done while trying limit any downside. That would include your users asking why everything just changed. I don't enjoy reading messages written in all capital letters either, where it seems those 10 exclamation marks are required to clarify how much you dislike it. Anyway, from here, based on that alone ... seems successful. Back to work and Slack messages.