I thought it was a third party thing we had installed but that doesn't seem to be the case. Is it an acquisition perhaps? Or what could possibly be the logic there?
Knockoff aside, the idea is a place where you can come and go without the formality of explicitly managing a group call. I've used it a few times with my team and it's basically "everyone just work on whatever they were working on, and if a question arises go ahead and ask, we're all here and we will answer". It's not a core part of our daily workflow, but I know some all remote teams who do "everyone on huddle between 1-3pm every day". They say they really like it.
Oh god this is my nightmare. I can't imagine trying to get any focused work done like this.
95% of the time, the chat is silence, as everyone is doing their job. 4% of the time, it's the users talking to each other to coordinate something they're doing; i can mostly tune this out because it doesn't directly involve me, but it's good for the developers to maintain some vague awareness of it, because it might be something we can help with, or suggest a way to improve the software. The other 1% of the time, it's developers talking about something urgent, that's worth interrupting me for.
We also have regular meetings, separate to the chat, where we have deep conversations. And we have a couple of Slack channels (one for the four developers, and one for all six of us), which we use for conversations which aren't worth taking to chat.
A key fact, i think, is that the channel is mostly silent. If it was full of developers getting into deep technical conversations all day, it would be a productivity destroyer.
It leaves the rest of your time in the day to be focussed. Unfortunately, our new manager didn't quite like it and scheduled meetings over top of it, so if you really wanted to talk to somebody about something, you'd end up waiting extra days, or just scheduling a meeting instead.
"That's interesting, let's bring it up in work chat tmw" was a great way to stay focused throughout the day
- You have a group chat and collaboration product that supports multi-way audio and video calls between individuals, as well as channel calls (calls visible to a channel that channel members can join).
- Somehow this is not enough, so you invent a new word for group calls: "huddle". Unfortunately, you then also implement it.
- "Huddle" has different UI. Starting a huddle, joining and leaving are different, but it's exactly like group call.
- "Huddle" doesn't honor "call" preferences like "start with microphone muted".
- This is not bungled up enough, so then you change the "Start a call" button on a channel to bring up a pop up menu whose first element is "Start a huddle". Starting a call is the second item, whose menu label is ... the product name rather than "Start a call".
- So now users expected to start a group call are accidentally starting huddles, which some team members don't notice because they are looking for a call notification.