Skip to main content

Business-Provider Maturity Model

In today’s business climate it is imperative that the IT Service Provider not only understand what the business strategy is, but be able to initiate and deliver services that not only support it, but help to shape it.  This can be successfully accomplished by ensuring that the service portfolio remain aligned to the business needs.  Over time these requirements and demand for services change and mature.  The Business / Provider Relationship is integral in keeping the demand and supply of these services and capabilities appropriately and continuously aligned.  One of the tools engaged for this task is the “Business-Provider Maturity Model”.

The Business-Provider Maturity Model is a way to help surface and understand the growth in maturity of business demand for Provider services and capabilities, and a Provider organization’s maturity of supply capabilities needed to both satisfy and shape that demand. Many maturity assessments are very IT centric assessing the ability of the Service Provider to satisfy demand from the business. The key difference here is that we also need to understand the businesses ability in being able to exploit the IT Service Providers capabilities to enhance the business strategy. It is a means of driving dialog about business demand and Provider maturity and how these elements continue to mature and grow. The model can be used for the entire enterprise or for a particular business unit or Provider capability.

In its simplest form, the model is an S-shaped learning curve—the business learning to exploit technology and the Provider organization learning to become efficient and effective in delivering services and, especially as maturity increases, shaping business demand.  Business executives find the model’s simplicity appealing. They can easily interpret the concepts behind business demand maturity and are able to use the model to analyze how their demand maturity is evolving over time. This enables them to engage in meaningful dialogue with Provider leadership about the business implications of both demand and supply maturity.  In most cases a basic three level model is utilized, however the number of levels is arbitrary. In some cases a 5-level model can be engaged, which can be useful because it represents a finer-grained approach.

To the left of the S-curve are the characteristics of business demand at each of 3 the levels. To the right are the corresponding goals of Provider supply.  It is important to understand this is a developmental model.  That means it is cumulative.  The demand at lower levels never goes away, the business always wants the lights kept on.  A Service Provider that fails to supply against this demand will lack credibility and the capability to move up the maturity curve.  As business demand matures to Level 2, Level 1 demand does not go away, it becomes a fundamental expectation.

Level 1 business demand is typically generated from functional and geographic silos which means it is often fragmented. This can be frustrating for the Service Provider, who are able to look across the enterprise and see many opportunities for cross functional processes and collaboration, but are often unable to communicate these concepts.

Level 1 demand is to provide basic services and solutions while ensuring stabilized operations and support, with an overarching goal of reducing the costs of doing business.

Level 2 demand, which continues to include Level 1 demand, focuses on enabling business partnerships, enterprise integration and consolidation of management information. Level 2 supply is focused on establishing common infrastructure and management information enterprise solutions. Level 2 supply also focuses on building credibility, improved service/ solution delivery, with attention to portfolio management, service management and getting faster at delivering solutions.

Level 3 demand, which now includes Level 1, 2 and 3 demand, addresses strategic and technology capabilities, which enable the convergence of business and IT capabilities which in turn enable business growth and innovation. It tends to be much more externally focused than Level 1 and 2, interested in business intelligence, rapid experimentation and collaboration with other business units, customers and suppliers.


Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem