{"id":7645,"date":"2019-07-10T11:38:40","date_gmt":"2019-07-10T10:38:40","guid":{"rendered":"https:\/\/acora2021arch.wpengine.com\/?p=7645"},"modified":"2024-05-24T14:53:44","modified_gmt":"2024-05-24T14:53:44","slug":"it-teams-need-to-adapt-to-proactively-support-the-waves-of-microsofts-updates","status":"publish","type":"post","link":"https:\/\/acora.s.nomatter.dev\/nltest\/news\/archive\/it-teams-need-to-adapt-to-proactively-support-the-waves-of-microsofts-updates\/","title":{"rendered":"IT teams need to adapt to support the waves of Microsoft\u2019s updates"},"content":{"rendered":"\n

There\u2019s no doubt that Microsoft has a lot of good products, a lot of quality development teams and a lot of marketing people. Mix that with evergreen subscription models and you get a lot of news on a regular basis reviewing the latest and greatest enhancements, tweaks, updates, tricks and suggestions about the service you are already using.

I read a blog yesterday and it talked about the Microsoft 365<\/a> updates for June. It was over 4 pages long and covered security, compliance, collaboration as well as more standard updates to the office suite.<\/p>\n\n\n\n

<\/span>From every couple of years to every couple of months<\/span><\/h2>\n\n\n\n

In the days of yore, after purchasing software, you would arrange some training or documentation on how to use it and try to get the best value from what you purchased. Over time you would figure that it\u2019s probably worth getting the updated version and then repeat the process. Then everyone would move forward with a wider functionality set, slowly.

This model sort of worked but there was always a danger that users stayed linked to a core set of the functionality available and rarely embraced the new elements.

So, in this new model with more frequent update options, what is the best process for managing updates that delivers the real engagement?

It is a serious question that covers everything from:<\/p>\n\n\n\n