Seven Steps for Microsoft Teams Success
Organizations transitioning to Microsoft Teams from Skype for Business must maintain the high level of reliability, security, and performance for their voice communications as they have today, while they shift call control into the cloud, and provide new ways for contextual collaboration.
Join Ribbon Communications and Nemertes, a global research-based advisory and consulting firm that analyzes the business value of emerging technologies as together - we provide guidance on how IT leaders can ensure a successful transition to Microsoft Teams.
- Requirements for Microsoft Teams success
- PSTN connectivity options and best practices
- Integrating Microsoft Teams voice and SIP security into your overall security architecture
- How to leverage Microsoft Teams Direct Routing
- Migration of existing voice assets into Teams
- Strategies for performance management across wired and wireless networks
- Enhancing voice quality with Microsoft Media Bypass to optimize call flows
Vice President - Analyst
Vice President - SaaS Solutions Engineering
WEBINAR: Seven Steps for Microsoft Teams Success
Seven Steps for Microsoft Teams
Let's start with just a quick overview of some of our market data in showing where we see Microsoft teams within the context of the overall unified communications collaboration market and then we'll dive into the Seven Steps that we've defined for Microsoft Team Success. Before we get too far it's probably worth defining what Microsoft Teams is and what we're talking about within the context of today's webinar. Teams offer three primary capabilities features to the buying audience. The first is calling, Microsoft dispositioned Teams as a replacement for Skype for Business for the online customers and there are actively migrating those folks onto teams as their phone system. Even for the on-prem customers that are studied in Skype for Business on-prem, there is a shift or an emphasis now to push more towards Microsoft Teams as the calling mechanism. In the latest release of an on-premise server, they unveiled new capabilities that make that migration simpler. One of the core functions that gets people using Teams first is the messaging capabilities having a replacement for instant messaging that provides persistence that provides integration with other applications that allow you to integrate things like file storage, BOTS, and project management, and other third-party applications. This makes that Team workspace a core area where a team can go to do their work. Lastly, meetings are Team's workspace that launches web conferences, audio conferences, and video conferencing and so on to enable real-time sharing of information among team members.
So just sharing some of our data we conducted a study earlier this year based on about 625 end-user organizations and we looked at plans for the Team collaboration space. This wasn't just specific to Microsoft teams but the overall collaboration market that includes plenty of other companies. We found roughly a pretty big jump from 2017 to 2018 in terms of the plans to adopt these tools. So from year over year, we went from almost 20% that were using collaboration tools now up to about 27%. Of those, about a third are using Microsoft Teams and we're seeing now about half that is seeing the opportunity or the possibility of making that Team collaboration application a replacement for their phone system. This is a little bit of a newer trend given the emphasis by Microsoft and some of their competitors to position the team collaboration space as almost that next-generation softphone because it gives you that persistent chat, a work based workstream collaboration capability, and also includes telephony.
So where we also see that an interesting aspect has been around how people are deploying these applications. We saw some of the early adoption tools, like Slack, that was very much niche departmental level focused. When we talk to organizations about Microsoft team they kind of look at it as an enterprise-wide solution. About a third are using just one provider, about 20% that have multiple enterprise-wide providers, and about 20% that are using that one product for enterprise but also allowing individual business units lines of business and so on or workgroups to use the tool that they may find better for them. As you think about it, from the Microsoft team's perspective becoming an enterprise-wide communication collaboration platform it is well-positioned to replace the telephony environment. We expect to see more of a trend toward a single enterprise platform with the ability for individual workgroups to use tools that are appropriate for them.
What we have seen is the typical team's migration has been the company start with teams as a messaging app they shift from Skype for business for their instant messaging to start Teams. The thing that gets people to embrace it is it has been largely the ability to integrate context around that team conversation. So rather than just having a chat window, I have a chat window that exists in a workspace I have associated files, I have associated tools like project management apps or other kinds of applications, and I can invite people into that extending it beyond my organization. The next thing that people usually typically add is the meetings capability, so if I'm chatting with some of my co-workers in a workspace and I say, "You know what let's get on the phone let's talk live and let's go through this PowerPoint presentation or this architectural diagram and talk about it in real time." I can kick off that meeting from within the team space and more recently a lot of focus now on calling and moving to that calling model.