We're hosting Mattermost (on-premise Slack alternative) privately so it rarely goes down. On those rare occassions we take a coffee break until everything is fixed.
We use it at our company too. In my opinion it is awesome! We also have our own gitlab instance. Both work very well together (mattermost login with gitlab account, notifications for CI pipelines and so on).
My favorite feature is the "Sidebar buttons" feature which shows the counts of your requested reviews, unread messages, assignments and open merge requests. You can click on any of the categories and it will navigate you to the appropriate view in Gitlab.
I don't remember the last time I used the phone for the actual phone functionality :D
Seriously speaking: I'm sure it's a possible last emergency but I think it's best to have a secondary chat tool, possibly hosted by a different cloud provider, when you have a distributed team :)
All you need is a policy and a company wide email that says: "Slack is not working, let's regroup in tool Y in 15 minutes"
Oh yeah don't get me wrong, multiple channels are important :P It just surprises me how it seems so few people use email or phones. I've never worked remotely to be fair, or worked with remote staff, so everyone's always been in the office. But even at my current agency, where there are 60-70 staff on site, we still just email or telephone.
I used to work for one that abused emails to the point that it was basically impossible to follow them because some PMs used to CC every possible person that remotely had anything to do with the product on them and anyone had stuff to say. Basically a broken chat :D
Regarding phones calls, I don't know, I guess it's also subjective. I'm not a huge fan personally (but I'm talking in general, not just for work) but it's not that different from having an audio call on any videoconferencing software, is it?
I think the most important thing is to have a plan B when your main tool of communication stops working, whatever that is.
Everything becomes the correct tool if it accomplishes that :)
Our internal comms tool is also the internal comms tool for a significant portion of the NHS in the UK.
It runs the same technology used in battlefields by armed forces around the world. Also the same technology used in battlefields of a different kind, like Fortnite, and Eve Online. The same technology is used for the Belgian ambulance app, too.
Both the technology and our deployment are designed to handle the kinds of "adverse network conditions" that would cause Slack and friends to stop working entirely - they didn't build hospitals for good WiFi, it seems, and the armed forces run over seriously low and laggy networks, too.
If we're running into performance issues, we all stop what we're doing and fix it - the fact our communication is down is the least of our concerns. But thankfully, we've never had problems worse than a few slow operations. I really hope that continues. :-)
Oh, the technology? XMPP. Open standard, open source, and yes, you can run your own server.
Since Slack was down, I just turned around to talk to the one I was messaging. But he was messaging a guy off-site and our PA was as well so the off-site guy just drove in (apparently the PA was emailing and texting him, too, since Slack was down, so it sounds like he needed to talk to her in person anyway as that was not efficient).
When slack goes down after our daily, we already know what to work on, so we'll continue and communicate via PR. Otherwise we'll use the time to inform ourselves on new developments (frameworks, libraries, typescript updates, new ES2019 features, stuff like that).
I am stuck here at a maximum of 30Kbps internet speed today and all I've done today is drink Tea 5 times and walk around looking at people's screens trying to connect to YouTube the entire day. Everybody else is doing the same I guess!
I like it! It's easy to keep everything in one place. We've gotten into a good organizational flow now - the first few months was a little bumpy - but we've been using it for about two years. We're totally remote, and Basecamp has been a game changer from our prior mix of Trello/Google/Flowdock/prayer.
Basecamp's support ranks up there pretty high for me, too.
There are some things I think Notion does a better job of, but overall, Basecamp is much better for company/business organization.
One of the things I do really love about Basecamp is the Google Drive integration - you can keep links to any Google Drive item in the corresponding project. It's been a gamechanger for project organization.
If we talk about productivity problems in such situation, one of the ways to prevent them is - not to teach the team to be under control.
In the Aspose (the company I work on) we all work independently and with the feeling of self-responsibility and freedom.
We do not depend on the communication channels and each others that much.
So the answer is - we just continue doing what we do. 😊
I'm a quality hero, customer champion. Experienced software tester and newbie developer.
Okay, so I've actually been dabbling in code for a long time. I've just not gone very deep in any language .
Data wrangler, software engineer, systems programmer, cyclist. Unix (mostly Solaris) for aeons. I talk C, Python, SQL, Performance, Java, Kafka and Makefiles.
Location
Brisbane, Australia
Education
BA (Mathematics, Modern History), University of Queensland
We're hosting Mattermost (on-premise Slack alternative) privately so it rarely goes down. On those rare occassions we take a coffee break until everything is fixed.
How does Mattermost stack up as a product, are you generally happy with it?
We use it at our company too. In my opinion it is awesome! We also have our own gitlab instance. Both work very well together (mattermost login with gitlab account, notifications for CI pipelines and so on).
Mattermost is releasing a gitlab plugin with its new release!
Disclaimer: I work for Mattermost
That's awesome to hear! What are the features to expect in the upcoming plugin?
Here is the repo, where installation and features are explained: github.com/mattermost/mattermost-p...
My favorite feature is the "Sidebar buttons" feature which shows the counts of your requested reviews, unread messages, assignments and open merge requests. You can click on any of the categories and it will navigate you to the appropriate view in Gitlab.
The Github plugin has similar functionality: github.com/mattermost/mattermost-p...
Go for a walk.
No official backup plan, but we do email or... gasp... phone calls. If Slack is down Zoom chat, or if Zoom is down Slack chat.
I may invest in carrier pigeons at this rate though. Feels like quite a few outages and issues recently.
Talk to each other? :)
that doesn't work when you're a remote team :D
Are telephones not a thing in your country? :p
I don't remember the last time I used the phone for the actual phone functionality :D
Seriously speaking: I'm sure it's a possible last emergency but I think it's best to have a secondary chat tool, possibly hosted by a different cloud provider, when you have a distributed team :)
All you need is a policy and a company wide email that says: "Slack is not working, let's regroup in tool Y in 15 minutes"
Oh yeah don't get me wrong, multiple channels are important :P It just surprises me how it seems so few people use email or phones. I've never worked remotely to be fair, or worked with remote staff, so everyone's always been in the office. But even at my current agency, where there are 60-70 staff on site, we still just email or telephone.
Whatever works best for a company...
I used to work for one that abused emails to the point that it was basically impossible to follow them because some PMs used to CC every possible person that remotely had anything to do with the product on them and anyone had stuff to say. Basically a broken chat :D
Regarding phones calls, I don't know, I guess it's also subjective. I'm not a huge fan personally (but I'm talking in general, not just for work) but it's not that different from having an audio call on any videoconferencing software, is it?
I think the most important thing is to have a plan B when your main tool of communication stops working, whatever that is.
Everything becomes the correct tool if it accomplishes that :)
Our internal comms tool is also the internal comms tool for a significant portion of the NHS in the UK.
It runs the same technology used in battlefields by armed forces around the world. Also the same technology used in battlefields of a different kind, like Fortnite, and Eve Online. The same technology is used for the Belgian ambulance app, too.
Both the technology and our deployment are designed to handle the kinds of "adverse network conditions" that would cause Slack and friends to stop working entirely - they didn't build hospitals for good WiFi, it seems, and the armed forces run over seriously low and laggy networks, too.
If we're running into performance issues, we all stop what we're doing and fix it - the fact our communication is down is the least of our concerns. But thankfully, we've never had problems worse than a few slow operations. I really hope that continues. :-)
Oh, the technology? XMPP. Open standard, open source, and yes, you can run your own server.
Since Slack was down, I just turned around to talk to the one I was messaging. But he was messaging a guy off-site and our PA was as well so the off-site guy just drove in (apparently the PA was emailing and texting him, too, since Slack was down, so it sounds like he needed to talk to her in person anyway as that was not efficient).
When slack goes down after our daily, we already know what to work on, so we'll continue and communicate via PR. Otherwise we'll use the time to inform ourselves on new developments (frameworks, libraries, typescript updates, new ES2019 features, stuff like that).
I am stuck here at a maximum of 30Kbps internet speed today and all I've done today is drink Tea 5 times and walk around looking at people's screens trying to connect to YouTube the entire day. Everybody else is doing the same I guess!
We use Slack, but the few times it's gone down, we use Basecamp's campfire feature in our main Basecamp project.
This is off-topic to the original thread, but how do you like Basecamp overall?
I like it! It's easy to keep everything in one place. We've gotten into a good organizational flow now - the first few months was a little bumpy - but we've been using it for about two years. We're totally remote, and Basecamp has been a game changer from our prior mix of Trello/Google/Flowdock/prayer.
Basecamp's support ranks up there pretty high for me, too.
There are some things I think Notion does a better job of, but overall, Basecamp is much better for company/business organization.
Thanks for the reply! Having good support (which oftentimes means having a tight product improvement loop) is such a great sign.
I've been a big fan of Notion for things like Team Knowledge Repos and keeping meeting notes, but there are definitely some pain points.
For collaborating on a document, I still haven't seen anything that comes close to Google Docs.
Appreciate the insight about Basecamp!
One of the things I do really love about Basecamp is the Google Drive integration - you can keep links to any Google Drive item in the corresponding project. It's been a gamechanger for project organization.
We use Discord and never had any down time.
But we do our best to have an open workspace so we can all communicate.
If there is any points to enlighten we favor a quick call. Or chat in the WhatsApp group chat or via email.
If we talk about productivity problems in such situation, one of the ways to prevent them is - not to teach the team to be under control.
In the Aspose (the company I work on) we all work independently and with the feeling of self-responsibility and freedom.
We do not depend on the communication channels and each others that much.
So the answer is - we just continue doing what we do. 😊
In a previous role, it meant more meetings >.>
It's hilarious because people start actually talking to each other. It's pretty cool.
Are you by any chance affected by Slack services being slow/down ?
Us, definitely. So far, we rely on emails. But the mobile app is working okay.
If its short I will get a coffee and take a break otherwise, I just email and text.
Go home, take lunch, have free-form idea session.
We go home and hope for a better tomorrow.
I read a book for 15 minutes today. So I guess more generally, I just "give up" until they're back :)
Google Hangouts for those who are remote and just straight up talking to each other for those in the office!
we carefully pat on each others shoulders to get attention but not scare the people with headphones on
Seems like Twitter and FB are the go to chat comms.
I work in telco, when communication channels go down, we panic in a predefined way :P we try all incidents to be resolved within 15 minutes.
I switched temporary from Slack to Team's today.. I'm not sure that reflects anyone else in my team.
play with nerf guns xD
We actually talk to each other. Really nice people, who would have known? (just kidding, all hell breaks loose)
We use emails or just Call on mobile if something urgent.
Panic :-)
If Teams should be down we fallback to mails, phone calls, or we just go to each others desks.
It never happened. We host our own mattermost & Gitlab instance and our own cloud services.
I just shout people's names to get their attention before talking to them.
Remote workers?
I JUST SHOUT LOUDER