Absence of Policy – The absence of policy often surfaces in the planning/envisioning phase of any adoption engagement, but this is the most common reason for delays in a Teams project. Implementing governance policies requires discussion and inclusion of stakeholders in a variety of roles – which means meetings, more discussions and then ‘hopefully’ decisions. We’ve seen several organizations decide to skip planning for governance and policy and as a result, are experiencing significant struggles in trying to reign in the chaos that has ensued. There are few things more important that building the policy and governance foundation for Teams. Teams governance and policy drives every decision – from how the tool is configured to how it is deployed, communicated, trained and ultimately drives the end user experience.
Thankfully, this mistake is easily overcome in the early planning phases of a Teams deployment. Consider this… When we think about governance and policies, it’s much broader than just ‘do we toggle on or off?’. Governance and policy decisions often require an investment in the decision-making process from more than just the technology team, typically legal, compliance and human resources should also be included in this process.
Let’s talk through the risk of leaving governance and policy planning out of the deployment process. Technically speaking, you can just ‘toggle’ Teams ‘on.’ Organizations that are doing this and giving ‘free for all’ access frequently experience regret as team creation becomes the Wild Wild West. Consider this very small scale, single portrayal of the potential pandemonium
In the scenario above, we have the potential for overlap in members of each team, information being worked on and stored in each team and serious confusion about which team should be used for what. To drive this message home, consider the number of departments in your organization, how many users are in each and how many of them can/should create a Team.
This is only one example of a policy decision and is the first step in promoting the use of Teams, based on your organizational vison. The second step is educating users on how to search for existing Teams, when it makes sense to create a new team, as well as how to name that Team for easy discovery and use while ensuring compliance from a policy perspective. Consider the streamlined and consistent approach you see below, when a policy is in place:
Planning for this and other important policy decisions related to groups, meetings, calls and guests will make the transition to Teams much less painful and ensure the appropriate level of governance is in place to organize and secure your Teams environment.
Stay tuned for the 5th most common mistake for Teams deployments.