Microsoft Teams

It’s not about the technology. It’s about the use case

This week, I participated in a REgarding 365 debate about use of org-wide Microsoft Teams. Not surprisingly, the Microsoft Teams versus Yammer question was raised multiple times. Here’s the thing–there are uses for Microsoft Teams (including org-wide teams) and there are uses for Yammer. In the end, it’s not about which tool myself or the other REgarding 365 panelists prefer. The valid questions are:

  • What are your organizational use cases and content needs?
  • What is your company culture?
  • Which technologies best fit your use cases and culture?

rawpixel-315193-unsplash.jpg

Use cases are practical business needs (aka requirements) that need to be met. Examples of use cases include:

  • Sharing organization-wide HR policy changes
  • Sharing strategy and content updates from the company’s CEO
  • Providing newly-onboarded employees with a resource center for frequently asked questions
  • Enabling employees to instant message, chat, and screen share with their peers
  • Enabling employees to quickly engage with other employees and members of IT on technology support questions

As collaboration strategists, our first job is identifying and documenting the unique use cases for our organization. Next, we need to assess our organizational culture, including: company values and norms; technology adeptness (aka how well our users adopt new technologies); and readiness for change (e.g. do our users welcome change or do they fear it?).

When we view our use cases alongside our company culture, we’ll be able to determine which technologies are best-suited to meet our needs. There is no one-size-fits-all model or one Microsoft 365 capability that wins the day. Let’s look at our organizational use cases and culture and determine what tool works best for our specific needs.

REgarding 365 debate #4: Org-wide Microsoft teams

Microsoft Teams will now support creation of organization-wide teams for small-to-medium sized companies. Org-wide teams can be created by Office 365 global administrators, but are limited to organizations with no more than 1,000 users. The org-wide public team will automatically incorporate all company users, pulling Active Directory information for everyone who joins or leaves the organization.

brainstorming-collaborate-collaboration-1204649.jpg

This new capability is generating some interesting discussions about how to best facilitate org-wide dialogue. Is Microsoft Teams best suited to host this type of open communication? And how would this new feature impact use of the All Company group in Yammer? The REgarding 365 team has assembled some thoughts on these questions. Check out our latest video:

We’ll be taking this discussion to the next level as we debate the merits of org-wide Microsoft teams. Tune in on October 25, 2018 at 4pm Central time to hear the debate live