consejos de Slack

Advice for large teams on Slack

How hundreds, or thousands, can communicate better

Autor: Matt Haughey23 de junio de 2017Ilustración de Kelsey Wroten

So you work for a large organization that uses Slack. While a lot of the tips and tricks we write about here can be useful to anyone, a large-scale team has particular needs and challenges because your work, functions, and interactions can be very complex.

Here are a few things that admins and users on large teams can do to make working together in Slack just as simple and fruitful as it is with a team of any size.


There’s really no such thing as “too many channels”

Big teams that successfully use Slack have a large number of channels, even into the thousands. In the course of research interviews with half a dozen large organizations, we noticed total channels were often two to three times the number of employees.

More channels may sound like more to keep track of, but here’s why that’s a myth: With a greater number of topic- and project-specific channels, groups can focus their discussions among smaller numbers of people. Furthermore, each person can be in fewer channels, because only a handful of specific channels will be necessary for their daily work. More channels on a team doesn’t mean more work when they’re increasingly targeted and organized.

There’s actually danger in having too few channels on a large team. Say you’ve got 500 people using just 40 channels total — a single channel would then likely cover many topics and projects that cross several functional groups. Specific information will be harder to track down amid simultaneous conversations about concurrent projects.

Channel naming conventions are key

Large teams can have hundreds or thousands of projects and groups, so it’s important to be able to find what you’re looking for quickly. The best first step is to develop a set of channel naming conventions for your team. These can vary, but some common conventions for organizing channels include:

  • Team channels, where members of a specific organizational group can discuss schedules, summarize meetings, and talk to one another: #team-ios, #team-design, or #team-security
  • Project channels, where everything related to a project can be organized and discussed: #project-123MainSt , #project-2017conference, or #project-café-rebuild
  • Team subchannels, where further specialization on larger teams can be organized:
    #marketing-events, #marketing-partnerships, or #marketing-pr
  • Topic channels, for more general talk, from serious things like
    #finance and #press-mentions to non-serious: #running or #tv-worth-bingeing

With a channel naming policy in place, discoverability goes way up. If you ever need to find, say, the mobile design team to report a bug, predictable channel names should make finding them just a few keystrokes away.

Managing slow vs. fast information

Larger teams can potentially send millions of messages back and forth each year. While a lot of it is real-time interaction between employees, there will also be details of major decisions, policy documents, company-wide announcements, and other perpetual information and resources.

A good way to promote key information inside of Slack is using the pin function to attach any important messages or documents to channels where they originated. It’s also common to archive channels when projects are completed.

You can dedicate channels to important announcements and documents, so they’re all in one place. For example, a lot of large teams do this as one of their first steps: limit the default #general channel to only allow posting by select team members, change the name to #announcements, and keep posts to occasional company-wide information.

Set channel expectations

If you’re on a large team with a lot of channels, it’s important to be clear about what each of them is for. Set a descriptive channel topic and fill out the channel purpose, which gives more space to describe why the channel was created.

channel expectations

You can also use those features to communicate social norms, such as “This channel is for general Q&A about programming” or “We only post news of completed sales deals here, use a thread for questions or comments.”

Let channel information guide you

Don’t forget to check the channel info banner before posting messages in unfamiliar channels. If you see a channel has 25 specialists around a subject, it’s probably the best place to ask a related question. If the channel has 450 participants, you’ll want to search in-channel for relevant keywords to make sure your question hasn’t already been answered.

Let notifications work for you

Your notification settings are worth review no matter what size your team is, but particularly if it’s very large. Most people can break down their channels into three categories: urgent/vital, normal, and muted. You can set notification levels across all your channels, but you can also customize them channel by channel.

For my own Slack team, I have two team channels where I set every single message to notify me since they’re so important. My starred and normal channels follow my default settings to alert me only if people use my @username. For channels I only occasionally review, I keep them muted, meaning they never light up with unread activity, and I catch up on any new messages on my own schedule.

Make the most of profiles

On large teams where a lot of people don’t interact every day, it’s a good idea to use custom user profile fields. Add potential fields like office location (great for global firms) or fields for areas of expertise, and let employees indicate who their managers and direct reports are.

Sharing a team with thousands doesn’t have to be overwhelming. Got your own tips or questions? Tweet us at SlackHQ.

Want to know more about how the largest teams use Slack? Look into Slack Enterprise Grid.

HOME > Slack 日本語ブログTOP > コラボレーション > 大きな組織で Slack を活用するためのアドバイス

¿Ha sido útil esta nota?



¡Muchísimas gracias por tus comentarios!


Gracias por tus comentarios.

¡Uy! Estamos teniendo dificultades. Por favor, inténtalo de nuevo más tarde.

Seguir leyendo