All week we have been talking about Teams being a journey, and as we talk about our Teams Success Criteria, you may be able to categorize it as project work. While we would argue each Success Criteria is additive and when combined gives you the roadmap to a successful Teams implementation, it is Management and Operations that helps you sustain your successful implementation.

Management and Operations. 

That is right, are you clear on the required "care and feeding" required to keep your Teams environment running smoothly? 

For example, have you thought about the following. 

• As part of the Office 365 suite, bi-annual updates to the suite will impact Teams
• Teams has near constant updates and the addition of new features and functionality. Who is deciding what to turn on or off and how do these impact other apps in your environment?
• How is your business evolving? What is the impact of new users? How is this impacting your position on governance or taxonomy?

If you haven't, no matter where you are in your journey, now is the perfect time to build these steps and more into your plan. As Benjamin Franklin once said: "An ounce of Management and Operational support, is worth a pound in happy end users and a smoothly running Teams environment." 

Ok, maybe that isn't exactly what he said, but we are pretty sure that is what he meant. While the level of effort after initial launch will likely decrease (unless you are working on initiatives to build on top of the platform, yay!), your Teams journey will continue indefinitely. 

Want to know more about Management and Operations requirements for Microsoft Teams? Check out the fourth and final video in our "Closer Look" series using the link below.