The Maturity Model for Microsoft 365 concentrates on defining a set of business competencies, that resonate with Microsoft 365 yet underpin real business activities. Taken together, the model allows organisations to figure out where they are in any function or department and what the notion of ‘better’ entails.
The Maturity Model for Microsoft 365 is not about features, nor is it just about IT either; it uses common language that all sorts of business roles can understand so that everyone can use the model.
The model consists of 5 ‘levels’ as follows:
Level 100 – initial
- Default, starting/exploratory state
- People driven processes, lacking documentation and discipline
- Many ways of doing the same thing (with variable results)
- Characterised by inefficient legacy approaches and pockets of un-managed innovation
Level 200 – managed
- Key processes defined but not standardised, uniformly or strongly applied
- Some ability to demonstrate consistent outcomes
- Limited buy-in from staff and management
- Widespread inconsistency and resistance
Level 300 – defined
- Defined and standardised
- Signed off, managed process
- Limited validation of effectiveness, doesn’t include edge cases
- Process users demonstrate familiarity
Level 400 – predictable
- Actively managed in accordance with agreed processes and has tracked metrics
- Effective achievement can be evidenced across a range of operational conditions
- Process has been tested and refined
- Process users demonstrate competence
Level 500 – optimising
- Deliberate and systematic process improvement/optimization
- Focus is on continually improving process performance
- Management of the processes are concerned with addressing statistical common causes of process variation and changing the process to improve process performance
“If we are going to manage information, we need to measure it and if we can’t measure it how can we manage it?”
You can’t manage what you can’t measure.
In this blog I’m going to examine and discuss some of the concepts related to one of the key building blocks that should underpin every organisation’s journey into the successful adoption of Microsoft M365. Their information management maturity (IMM) and specifically how the Microsoft Maturity Model can be leveraged to drive this journey.
WHAT MICROSOFT 365 MATURITY LOOKS LIKE
An organisation that has driven up its information management maturity to level 5 (optimised) will typically be using the core Microsoft 365 workloads in the following ways:
Microsoft Teams
Business transformation and process development; usage of >95%
SharePoint
External data is leveraged; multiple systems are integrated with SharePoint; usage >85%
OneDrive
All files and workloads are synchronised (local files do not exist) and integrated features are leveraged; usage >85%
Outlook
Email is ONLY used outside the organisation; all integrated features across M365 are leveraged.
This document may be a good reference for the above:
What is Envision IT’s Microsoft 365 Maturity Model?
If you would like assistance with assessing and improving your organisation’s information management maturity or implementing a Microsoft 365 solution, contact Insentra today. Our team of experts can help guide you through the process and ensure that your organisation is leveraging its use of information in the most efficient, effective, and productive way. Contact us now to learn more about how we can help you achieve your goals.
Related Articles
Microsoft 365 Tenant Migration Planning: Part 1
Microsoft 365 Tenant Migration Planning: Part 2 – Migration Workloads
Microsoft 365 Tenant Migration Planning: Part 3 – Completing the Migration
