SWOOP Microsoft Teams Benchmarking

Learn what ‘good’ looks like for Microsoft Teams

SWOOP has benchmarked more than 5,300 Teams across 15 organisations, 47,000+ people and more than a million Microsoft Teams interactions.

In this world-first benchmarking of Microsoft Teams, we’ll show you what high performing teams look like, show you worst practices in Teams and how to avoid them and share best practices from customer case studies.

Download the free report today.

You’re also welcome to sign up for a free trial of SWOOP to see how you compare with the best in the world.

By downloading the report you opt in to be added to our SWOOP Newsletter. You can unsubscribe at any time. Privacy Policy.

SWOOP’s Microsoft Teams benchmarking report will give you evidence-based answers to these questions and more:

  • What’s the most used function in Microsoft Teams?
  • How many teams have employees joined?
  • What’s the average number of interactions employees have on Teams each week?
  • How much is Microsoft Teams being used for really useful work and to get things done?
  • To what extent is Microsoft Teams being used as a “hub” for other O365 applications?
  • Is there a risk of becoming overloaded with messages in Microsoft Teams?
  • Do we still need Yammer?

Top 5 Emerging Worst Practices

Worst practiceWe have mischievously labelled a section in the report “Worst Practices”, as we felt it important at this early stage of Teams adoption to warn readers of practices our partners are observing that could cause real problems over time.

We’ve interviewed five of the world’s top Microsoft consultancy firms to find these emerging worst practices when rolling out Teams. At worst, they could derail the whole adoption process. At best, they could unnecessarily slow adoption. Warning: Avoid these practices!

Over-formalize and over-structure the Teams roll out
For example, looking to do incremental department by department roll outs; insisting all staff are formally trained before providing access to Teams; creating an “approval wall” for Teams creation, leaving no room for exploration and experimentation. A certain way for Teams to fail dismally is to spend months training every employee on how to use it, when to use it and what to use it for before rolling it out.
Allow the IT department to dictate how to use Teams, don’t let other aspects of the business have a say in how it should be used.
Allowing IT departments to force Teams on employees without engaging other aspects of the business, or taking into account employees’ experience, is a sure-fire way to ensure Teams adoption will fail.
Replicate the status quo in Teams. Transfer everything into Teams.
For example, creating a Team for each unit in the formal organisation chart; adding “just in case” members to Teams (Team “Bloat”); creating a Team for every Email list to just do the same function; or even worse, still keep the Email list as well.
Rely on senior executives to lead the change in favour of a viral grass roots approach
Imagine it, your CEO, COO, line managers have been invited into every team as a sign of leadership. They can’t cope with the notifications, they can’t navigate their way to see what’s really important and employees are wondering why their boss is there overseeing their day-to-day work.
Use Teams as an alternative to other tools like Yammer, SharePoint and One Note
You’d be surprised at how many organisations think there’s no need for Yammer or Sharepoint now Teams is up and running. Wrong! Some organisations are seeing Teams as an opportunity to rationalize their toolsets and simply use Teams for everything.

How does your organisation’s use of Microsoft Teams compare with others?

Our free benchmarking report allows you to compare the following indicators against other organisations. Example metrics include:

Team Size and Persona

What types of teams can we find on Microsoft Teams? What’s the average number members of a Team, and how many of these are active?

Interactions per Active User

A basic measure you can use to compare how actively engaged your employees are to similar organisations using Microsoft Teams

Key Player Risk

How much your social network relies on a select few individuals.

2 Way

Reciprocated relationships help us determine trust levels. High trust = high speed. How fast can you go?

Curiosity and Diversity

Are your users asking questions on Teams? Asking questions is a fundamental aspect of succesful collaboration. Are they actively contributing to a single Team or multiple Teams?

Response Rate

A high response rate shows people are engaging others in conversation. Compare your organisation’s response rate with others.

Participate in Benchmarking by SWOOP