Skip to main content

The Enterprise Service Catalog - Unifying IT Services for the Digital Age

Dennis Drogseth

While service catalogs are not new, they are becoming increasingly critical to enterprises seeking to optimize IT efficiencies, service delivery and business outcomes. They are also a way of supporting both enterprise and IT services, as well as optimizing IT for cost and value with critical metrics and insights. In this blog, we'll look at how and why service catalogs are becoming ever more important both to IT organizations and to the businesses and organizations they serve.

What's Cooking in General with Service Catalog Deployments?

Potentially, service catalogs can span everything from supporting internal IT professional needs to end-user needs for IT support, to end-user access to internally delivered software and applications, to support for third-party cloud services across the board, to actual support for enterprise (non-IT) services as managed through an integrated service desk.

Of course the game is changing, with added pressures to support cloud, mobile and enterprise (non-IT) services. But data and dialogs from last year show clear trends that reflect pushing the bar forward in all these areas from past years — with a striking diversity of options. Indeed, enhanced automation for self-service was and remains at the very top of the list for IT service management priorities going forward.

Interestingly enough, internal IT-to-IT provisioning (new servers, deployment requests, etc.) and support for IT professional services (as in project management capabilities) remain among the highest priorities for enterprise service catalogs. But close behind, are:

■ Support for cloud and non-cloud delivered applications

■ End-user access to production services/ applications

■ End-user device (PC, laptop and mobile) provisioning

■ End-user support (help and incident management)

Perhaps not surprisingly, true "appstore" type access for end-user self-service provisioning was far behind these priorities in mid-year 2015. But current EMA dialogs show a growing interest in providing a more complete and self-sufficient storefront approach.

A Few Critical Service Catalog Dimensions

The dimensions of how this is done can range drastically in scope, but ideally enterprise service catalogs will provide metrics for cost and usage, selective service level (service quality) guarantees as appropriate, strong support for secure and appropriate access based on end-user or IT professional roles, and integrated levels of automation to make service provisioning more dynamic, accessible and efficient. Oh, and yes, in the more advanced IT environments, service catalog integrations can handshake as well with service modeling and configuration management databases (CMDBs) to enable yet more advanced levels of automation This can be especially helpful when catalog services are tied to development and DevOps initiatives.

And finally, service catalog access should span not only desktop and laptop access, but increasingly mobile access as appropriate. For instance, nearly two-thirds of our respondents in last year's research were seeking to provide mobile access to corporate application services, and that percentage is steadily climbing higher, as mobile continues to redefine IT and consumer priorities.

Growing areas of interest for service catalog inclusions: cloud and enterprise services

Even last year support for cloud services in service catalogs was striking — at nearly 90%. And cloud priorities in type reflect a growing and rich diversity. These include:

■ Internal software-as-a-service (SaaS) applications

■ Internal infrastructure-as-a-service (IaaS) services

■ Software-as-a-service from public cloud

■ Infrastructure as a service from public cloud

■ Internal platform-as-a-service (PaaS) offerings

■ Platform-as-a-service from public cloud

The above list is in ranked order based on mid-year 2015, and subsequent dialog and research in 2016 would indicate a fair amount of consistency, but with a modestly growing preference for public cloud.

Just as striking as cloud in its impact on IT is the growth of including enterprise service support through integrated service desk and IT service management options. Indeed, a separate commentary on the coming together of business process automation (BPA) and IT process automation (ITPA) — (it isn't really quite there yet) — would probably warrant at least a blog, and maybe a book. But this coming together is reflective of the striking number of IT organizations that are making the leap. Indeed, even a year ago, only 11% had no plans to consolidate IT and non-IT customer service.

In terms of service catalog specifics, the following enterprise groups were shown to depend on service catalogs to support their services:

■ Vendor and contract management

■ Facilities management

■ Purchasing

■ Enterprise operations

■ Sales

■ Human Resources

■ Marketing

■ External customer facing catalog options

■ Corporate finance

■ Legal

What Makes for Success When It Comes to Service Catalog Adoption?

As many of my readers know by now, in most of my research I like to contrast those who view themselves as ‘extremely successful' with those who were only marginally so (the two extremes), which almost always produces meaningful patterns of difference. In this case, the following patterns arose:

Those ITSM teams who viewed themselves as extremely successful were:

■ 2X more likely to have a service catalog

■ 2X more likely to offer users access to corporate applications through mobile

■ Dramatically more likely to support cloud-related services in their catalogs. In fact they were 5X more likely to support SaaS from public cloud and 6X more likely to support PaaS from public cloud.

■ Considerably more likely to support enterprise services, including:
- 2X more likely to support human resources
- 3X more likely to support facilities management
- 2X more likely to support legal
- More than 4X more likely to support purchasing
- 5X more likely to support marketing
- Nearly 3X more likely to support enterprise operations

Given this rather heady show of data, it becomes harder and harder to argue against the impression that we're not only living in the midst of the "digital age" in which "digital transformation" is key, but that service catalogs are increasingly becoming a critical cornerstone in making digital transformation yet more of a reality. Current EMA research, underway now, will explore the role of service catalogs in optimizing IT for cost and value. I'll be sharing these highlights with you in another blog later in Q3.

Image removed.

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

The Enterprise Service Catalog - Unifying IT Services for the Digital Age

Dennis Drogseth

While service catalogs are not new, they are becoming increasingly critical to enterprises seeking to optimize IT efficiencies, service delivery and business outcomes. They are also a way of supporting both enterprise and IT services, as well as optimizing IT for cost and value with critical metrics and insights. In this blog, we'll look at how and why service catalogs are becoming ever more important both to IT organizations and to the businesses and organizations they serve.

What's Cooking in General with Service Catalog Deployments?

Potentially, service catalogs can span everything from supporting internal IT professional needs to end-user needs for IT support, to end-user access to internally delivered software and applications, to support for third-party cloud services across the board, to actual support for enterprise (non-IT) services as managed through an integrated service desk.

Of course the game is changing, with added pressures to support cloud, mobile and enterprise (non-IT) services. But data and dialogs from last year show clear trends that reflect pushing the bar forward in all these areas from past years — with a striking diversity of options. Indeed, enhanced automation for self-service was and remains at the very top of the list for IT service management priorities going forward.

Interestingly enough, internal IT-to-IT provisioning (new servers, deployment requests, etc.) and support for IT professional services (as in project management capabilities) remain among the highest priorities for enterprise service catalogs. But close behind, are:

■ Support for cloud and non-cloud delivered applications

■ End-user access to production services/ applications

■ End-user device (PC, laptop and mobile) provisioning

■ End-user support (help and incident management)

Perhaps not surprisingly, true "appstore" type access for end-user self-service provisioning was far behind these priorities in mid-year 2015. But current EMA dialogs show a growing interest in providing a more complete and self-sufficient storefront approach.

A Few Critical Service Catalog Dimensions

The dimensions of how this is done can range drastically in scope, but ideally enterprise service catalogs will provide metrics for cost and usage, selective service level (service quality) guarantees as appropriate, strong support for secure and appropriate access based on end-user or IT professional roles, and integrated levels of automation to make service provisioning more dynamic, accessible and efficient. Oh, and yes, in the more advanced IT environments, service catalog integrations can handshake as well with service modeling and configuration management databases (CMDBs) to enable yet more advanced levels of automation This can be especially helpful when catalog services are tied to development and DevOps initiatives.

And finally, service catalog access should span not only desktop and laptop access, but increasingly mobile access as appropriate. For instance, nearly two-thirds of our respondents in last year's research were seeking to provide mobile access to corporate application services, and that percentage is steadily climbing higher, as mobile continues to redefine IT and consumer priorities.

Growing areas of interest for service catalog inclusions: cloud and enterprise services

Even last year support for cloud services in service catalogs was striking — at nearly 90%. And cloud priorities in type reflect a growing and rich diversity. These include:

■ Internal software-as-a-service (SaaS) applications

■ Internal infrastructure-as-a-service (IaaS) services

■ Software-as-a-service from public cloud

■ Infrastructure as a service from public cloud

■ Internal platform-as-a-service (PaaS) offerings

■ Platform-as-a-service from public cloud

The above list is in ranked order based on mid-year 2015, and subsequent dialog and research in 2016 would indicate a fair amount of consistency, but with a modestly growing preference for public cloud.

Just as striking as cloud in its impact on IT is the growth of including enterprise service support through integrated service desk and IT service management options. Indeed, a separate commentary on the coming together of business process automation (BPA) and IT process automation (ITPA) — (it isn't really quite there yet) — would probably warrant at least a blog, and maybe a book. But this coming together is reflective of the striking number of IT organizations that are making the leap. Indeed, even a year ago, only 11% had no plans to consolidate IT and non-IT customer service.

In terms of service catalog specifics, the following enterprise groups were shown to depend on service catalogs to support their services:

■ Vendor and contract management

■ Facilities management

■ Purchasing

■ Enterprise operations

■ Sales

■ Human Resources

■ Marketing

■ External customer facing catalog options

■ Corporate finance

■ Legal

What Makes for Success When It Comes to Service Catalog Adoption?

As many of my readers know by now, in most of my research I like to contrast those who view themselves as ‘extremely successful' with those who were only marginally so (the two extremes), which almost always produces meaningful patterns of difference. In this case, the following patterns arose:

Those ITSM teams who viewed themselves as extremely successful were:

■ 2X more likely to have a service catalog

■ 2X more likely to offer users access to corporate applications through mobile

■ Dramatically more likely to support cloud-related services in their catalogs. In fact they were 5X more likely to support SaaS from public cloud and 6X more likely to support PaaS from public cloud.

■ Considerably more likely to support enterprise services, including:
- 2X more likely to support human resources
- 3X more likely to support facilities management
- 2X more likely to support legal
- More than 4X more likely to support purchasing
- 5X more likely to support marketing
- Nearly 3X more likely to support enterprise operations

Given this rather heady show of data, it becomes harder and harder to argue against the impression that we're not only living in the midst of the "digital age" in which "digital transformation" is key, but that service catalogs are increasingly becoming a critical cornerstone in making digital transformation yet more of a reality. Current EMA research, underway now, will explore the role of service catalogs in optimizing IT for cost and value. I'll be sharing these highlights with you in another blog later in Q3.

Image removed.

The Latest

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ...