Slack: Our biggest redesign yet came to be
slack.design
slack.design
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.
Hold up there, I can't drink that fast.
Software development feature entropy is the 4th law of thermodynamics.
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.
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
"Our telemetry says that the random stuff we're bolting onto the product (like a document system (?) to go inside our chat app) is making it less usable and less good for users. So instead of listening to that feedback and telling management that our projects weren't actually helping users, we decided a better way to get promoted was to do a redesign."
> Operationalize transparency to build alignment
"We spent a bunch of money on a huge all-company onsite/whiteboarding session, then we proceeded to ignore the feedback from everyone who wasn't middle management or higher."
As a fun and instructive exercise, read through this, then read through Slack's post-Salesforce-acquisition Glassdoor reviews[1].
[1] https://www.glassdoor.com/Reviews/Slack-Reviews-E950758.htm
Every time, more chrome, bigger fonts, more padding, more views that take over the whole viewport.
I guess when everybody had an 800x600 screen we had to make the most of them.
Maybe they could bring back the IRC bridge.
I think that could only happen if IRC added support for threading.
It allows me to easily have multiple different conversations in the same channel at the same time.
And, if I need to, in the future, share that conversation with someone, I can link them directly to that one thread.
What would I do otherwise, when I needed a team mate to get up-to speed on a convo that happened months ago... Hey go back to August 8th at 1PM and read everything while filtering out all the things that aren't relavent? Crazy talk!
Edit: I will say for this to work, a higher up at your company needs to slap people when they don't use threads. In my org. our CTO is very good about reminding people to use threads.
Engineers are generally ok and appreciate density but more mainstream users often don't.
I really hate this change too, on my laptop, slack has to be full screen to make sense whereas I can have four screens of terminals and email without issue otherwise. Wish they at least made the design adaptive
HN does this thing where it automatically strips out "how" from titles, presumably because someone once decided that the "how" is unnecessary or clickbait. The original title here is "Slack: How our..." The most interesting thing for me is that this error-prone moderation rule has made me realize how linguistically load-bearing the word "how" is in many sentences.
But now it's pretty atrocious. The Activity tab is uselessly cluttered. If someone is trying to get my attention in a thread and it's not a DM, I rarely ever see or notice it.
I like that DMs are pulled out from channel activity. But "Home" for me is such a hot mess of hundreds of channels with no easy way to discern important things from noise.
It really feels like the intended usage is to ignore white dots and focus on red, but then we really need a setting to remove all white dots who really can't proceed to real work until they're gone.
Such a stupid change. Just show me the workspaces by default gosh darnit.
whoa! is this as heavenly as it sounds, or does it just mean you're using Teams?
Ignoring all the negative feedback was hard, but we pulled it off!!!
And, notably, it's really bad at being a chat app, which is probably where Slack is headed if they keep going.
Also, so I can answer the question she keeps asking: did they in fact get rid of Huddles? If they didn't, she can't find them anymore.
I have no idea what kind of feedback they received, but Slack was not absolutely broken; it was not great, and the redesign made it worse, not better. If you already know that redesigns should be avoided at all costs, why did you still do it?
Also as a sidenote Slack's notification system is still hopelessly broken; I will regularly respond to a DM on my phone, get back to my laptop, click on a notification, only for it to bring me right back to the message I literally just responded to on my phone!
Discord handles this beautifully, the moment I look at a message on my phone it's marked as read on the desktop client. I can't believe a feature as core as notifications in a chat app can be this broken compared to Discord's beautiful implementation.
Somehow they did both. Kind of impressive tbh.
"When might we start bringing customers into the process?" Seems like this should be much earlier in the process, no? Sure relying on automated metrics to help guide your process was part of the path, but if you aren't really talking with customers and figuring out what your needs are, your designs are going to be more biased towards how Slack operates and the culture of Slack.
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.
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.
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.
The biggest issue of this redesign for me was getting rid of the "unread message badge" both on the desktop app icon and the browser tab. They used to have a badge with numbers for missed notifications (e.g. direct messages) and one (empty circle) for unread messages, but now a missed direct message and the 100th message on an HR channel thread show the same badge.
I found that Slack was nagging for more of my attention after the redesign (gotta get those engagement numbers up!). I ended up using a Chrome extension (Tab Modifier) to hide the Slack tab's badges.
Now, that status is only cleared after the client fully reloads the channel, which can take multiple seconds (yay, modern software). As someone with dozens of channels I don't read and can't organize, it's very tedious to clear them so I can focus on the channels I actually care about.
https://superuser.com/questions/1211975/slack-app-on-linux-h...
Annoying how some things moved, still not enough emphasis on channels that have unread messages (light text vs. normal for “bold” to call attention), and still no way to mute all but direct @ messages… so you can’t ever mute @channel or @here without muting the channel. The way Slack handles and automatically closes direct messages and private chats is annoying and I want to be able to turn that off… but I can’t. I have a group I check in with like once every two weeks and I have to rebuild the list or “star it” to save it. But stating it moves it to another area above group messages… not a fan.
Honestly Discord is better in almost every way still. Kinda wish they stole more from Discord.
Either way, it all sucks, and I totally sympathize. :(
According to https://slack.com/resources/using-slack/how-to-organize-your... that seems paid-only feature
5 years ago Slack was a very focussed chat tool, and it rang rings around the other solutions available at the time (our company was heavily invested in Skype for Business, aka Microsoft Lync, aka Microsoft Communicator).
Now it's a confusing forest of duelling messaging paradigms. Is the message I'm looking for in Connections or DMs? Is the channel in Connections or in Channels? Maybe it's in Threads? I know, I'll check the Activity panel, which doesn't know how threads work...
Look I'm all for improving UX/UI but at the end of the day your users need to be 1st priority. Seems like they're still in the denial phase.
Then I had to dig around and figure out how to de-WindowsVista-ize the theme: disable transparency and gradients, then used "Surprise me" for the theme colors until I got something not-too-loud.
https://slack.design/wp-content/uploads/sites/8/2023/10/imag...
I'm somewhat surprised that the design blog for the company has such a glaring design problem.
It also feels more intuitive to use on mobile, and this is coming from someone who typically hates app design changes