Underestimating the effort and complexity of a Microsoft Teams deployment is the #1 most common trend we encounter with organizations of all sizes, in all industries – and nothing could be more detrimental to the success of a Teams deployment. Here are some considerations that should be made as you begin socializing a Teams deployment.
- Educate IT on the features and functionality of Teams and the spiderweb of O365 connected tools and apps as a result creating a Team.
- Check on the status of your organizational Office 365 (2016), SharePoint and OneDrive for Business deployments. To create the optimal Teams user experience, with full features and functionality, you’ll want Office 365, SharePoint and OneDrive for Business.
- You can toggle that on/off switch for several configurable features in Teams, but collaboration isn’t one. Avoid deprioritizing and neglecting collaboration because voice has greater impact. Instead, consider a Level 100 and Level 200-type of graduated training. Level 100 provides voice and meeting training to prepare users for day 1 cut overs, while Level 200 collaboration training should follow within 7-10 days and showcase the collaboration features of Teams. Additionally, don’t ignore calling features just because you aren’t deploying Enterprise Voice as your users will still have peer-to-peer calling capabilities. Failure to educate users on any one of these features can lead to dissatisfaction and misconception of Teams as a solution.
- Know your vision for Teams. Will it replace Skype Meetings, WebEx Meetings, Skype Chat, etc – Consider the detrimental impact to end user adoption by providing two or more meeting tools and two or more chat tools. As a user, I’m going with the tool I’m comfortable with. Decommissioning use of these duplicate feature tools will significantly impact how motivated users are to adopt. Ask these same questions for places of collaboration today – Google, Slack, Shared Drives, etc. Ensure that the vision and the decommission process for tools is transparent
This is just the tip of the iceberg when you begin socializing the vision, impact and deployment of Teams, stay tuned for Mistake #2