Ever since Microsoft introduced Groups to Office 365, the customer reaction has largely been, “huh?” Customers would ask me, “what’s up with these Groups?” Then Microsoft bought Yammer, which seemed to make the confusion worse. And with the introduction of Teams, customer reaction has been even more confusion. Let’s see if we can sort things out. What’s the best tool to use in a given situation?
In the Beginning, There was Email
Let’s start with the one communication tool we all use the most: email. What are its benefits and drawbacks?
Some Email Benefits
- It’s easy to send a message to people—a lot of people, or just a few.
- It’s a permanent record (for those that tend to save their messages).
- It’s (relatively) easy to find what you want.
Some Email Drawbacks
- It’s hard to process the volume of email we get every day.
- It’s hard to separate the important messages from the urgent ones.
- Email is not well-suited for communicating in media other than text.
Email is the tool we love to hate. And when I’m working with customers on how to more effectively communicate and collaborate, communicating less is never a viable option. What we need are tools that are purpose-built for the kinds of collaborating we’re trying to accomplish.
Microsoft Groups get a brief mention here. But Groups are not a solution as much as they are a building block for tools I’ll describe below. The one positive thing about Groups is that they are not email distribution lists.
A Time for Teams
Teams are built on Groups. Think of Teams as the “above the waterline” part of Groups.
It might be easier to understand Teams if you add the word “small” in front of Teams. Teams is the vehicle for getting stuff done. Most of us work in a team every day. We might work in a team that is also our organizational “department,” like Finance. We might work in a team drawn together to accomplish a specific objective, such as planning an event.
The teams we work in are often internal to our organization, but this isn’t always the case. Sometimes our team includes a consultant, or a donor, or a grantee.
So, when should you choose Teams for collaborating? When you have a tangible objective to accomplish. We use Teams to get these weekly updates out. Teams are also a good choice for creating a sense of community in organizations that are smaller. If you have less than a hundred employees, Teams would be a good way to share content and collaborate. Employees that like to organize lunchtime bike rides could use Teams for this activity.
What About Yammer?
Some people would argue that Yammer can do everything Teams can do. They’re largely correct, but that misses the point.
Think of Yammer as the organization’s water cooler. You can (virtually) gather around to learn about people, events and activities. This is especially true for larger organizations. If there are a lot of employees, or several locations, or very large departments, it’s likely that you won’t know everyone in the organization. Here is where Yammer shines.
For instance, we have a large customer, the Asia Foundation, with many offices throughout Asia. They use Yammer to share news about what’s going on locally. They also use Yammer to create a sense of community for members of one department that are spread across multiple locations.
As well, Yammer is also useful for organizing long-lived conversations. For instance, if your organization is working on an initiative that will last all year, Yammer is a nice way of organizing the content, so you can go back and see how the thinking on a topic has evolved.
Finally, Yammer is also handy for organizing a large project team, especially one that includes participants from outside the organization. It’s easy to integrate them into the group and maintain good security. Microsoft uses Yammer to keep its partners up to date.
Pulling It All Together
Here’s the TL;DR version of the story.
- Email: Good for one:many communications
- Groups: Nothing to worry about here
- Teams: Good for specific projects, and for pulling the (smaller) organization together
- Yammer: Good for ongoing work, and for pulling the (large) organization together
Here’s a nice article on this from Tony Redmond.
And we’ve shown you a handy infographic from our friends at 365ForAll