We tend to use prefixes to better define individual channels. Which leads us on nicely to the power of naming conventions. A bit like discussing something in the physical office, where everyone can hear what’s happening even if they don’t need, or want, to join in. By discussing topics relating to those departments publicly it reduces silos that private channels and groups can add. Instead, these Channels are our default for transparency. Each Channel is a place for topics within those areas to be discussed, but isn’t restricted to just the teams within those departments. How you “slice the pie” will depend on your company setup.Īt Countfire we tend to use business groups as the base for our channels, for example #marketing, #sales and #success.
Slack advises starting with “broad channels”, then refining Channels to become more specific over time. This is a bit like the signposts you might use in a traditional office for different floors or areas to help everyone easily navigate to where they need to go. As you grow, or if you’re starting at a fair size, you’ll need to get better at organising what information goes where inside Slack. With a very small team you may be able to get away with posting everything in your #General Channel in Slack. Set up different Channels for different topics The key is to have a backup and publicise this, so everyone knows where to turn when your remote office disappears. This makes the most of two other tools which are already familiar to Countfire’s team (Zoom and Notion) but you could achieve similar with Google Chat or a tool such as Discord. So that everyone in the company can quickly join and carry on chatting in real time to save us floundering around on email.
#SLACK STATUS EXAMPLES HOW TO#
Will set up a Channel inside Zoom ( guide on how to do that here) dedicated to Slack being down.
Saved in Notion, our Wiki tool of choice, is a backup plan for what to do if, or when, Slack goes down in future: The common thread? No service, however large or all powerful, is unbreakable.Īs a result, our Founder Will, prepared for a future outage.
#SLACK STATUS EXAMPLES SOFTWARE#
Create a back-up plan for when Slack (inevitably) goes downĪs a software company ourselves we felt a pang of sympathy when Slack suffered a global outage on 4th January this year, the first day back for millions of schools and workplaces that use it to communicate.Ī similar panic ensued when Google’s services went down just a few weeks earlier, and in September when Microsoft’s millions of users experienced over five hours of downtime. 8 tips on using Slack more effectively while working as a remote team 1. Here, we wanted to share a few tips on how we use Slack effectively while working as a fully remote team. But with any form of communication, we’ve always known that etiquette and boundaries are needed to stop it becoming a shouting match. It’s how we conduct most of our communication. Since going fully remote in 2020, Slack has become an even more crucial part of our infrastructure. Sometimes you need a tool that enables a queue of messages, that’s faster and less formal than email. Since WFH became the norm and not the exception, many companies have adopted tools to work effectively and facilitate the casual comments and conversation that in-office environments offer.Īt Countfire, Slack has always been a core system that we used even when we were all in the office, to allow us to quickly make decisions and prevent the interruption of deep work.
0 kommentar(er)
