MM4M365 - "Change management/IT-Tech monitoring" competency

[KevinStocky]

Article suggestion

Regarding the Maturity Model for Microsoft 365 practitioners, I’ve been reflecting on some thoughts after our recent MM4M365 practitioners call on Tuesday, February 20, 2024. During the call, we had an excellent presentation on Service Change Management by Michael Blumenthal. After some contemplation, a few key points have stuck with me:

1. General Perspective on “Change Management”:

• How do we effectively manage changes in the technology, services, and products that our organization currently uses?
• How can we stay informed about new technologies and services emerging in the market, especially disruptive ones like AI?

Taking it maybe further:

• Beyond the basics, let’s explore more advanced aspects:
• How do we monitor organizational changes that impact the technologies, services, and products deployed across our entire organization? How do we stay attuned to business and market changes that might affect our infrastructure?

2.The Core Idea:

• Essentially, any mature system should continuously monitor its context (both internal and external) for changes. Once identified, we assess the consequences and take appropriate action.
• Michael’s comprehensive approach aligns well with this principle, can it be made more generic?

3. Competency Considerations Shouldn't "Change management" be in the scope of the Infrastructure competency ? There an organization basically defines what and how IT tech/products/services are used to address business needs. But at the age of Cloud, XaaS and disruptive innovations, this definition is even more iterative and cycles are becoming shorter. So shouldn't the model give clear(er) recommendations on how/when to manage this ? Core objectives be: Equiping IT pros with guidelines to do it, while encouraging management to allocate time/budget to these activities as well.

Apologies if I Missed Anything: If this topic has already been addressed in the current content, I apologize for any redundancy!

Thanks for the work done, lovin' it!!

[sympmarc]

@KevinStocky - Thanks so much for your thoughts here. I'm passing the link along to the rest of the team, so expect some more dialog soon!

[SimonJHudson]

@KevinStocky this is good stuff. I'll see if Michael can incorporate your thoughts into the Practical Scenarios he wrote.

For the broader question of "Shouldn't 'Change management' be in the scope of the Infrastructure competency?" I think that's a great point. Do you feel up to suggesting some appropriate characteristics at each level? You can edit the competency directly via GitHub, or send them to me if you prefer.

[KevinStocky]

Hi Simon, Thanks for responding back. I'll give it a go and if I find any difficulty editing in GitHub I'll give you a shout !

I am away today so saddly cannot attend the monthly call, but hope you guys have a nice one! Regards,