Taking Control of a Vast and Complex Applications Portfolio

Brendan Crowe

Imagine you're sitting in a coffee shop and you notice that your smartphone is being sluggish yet again. Applications aren't opening immediately, there's a constant lag with everything and sometimes things seem to crash midway. Fortunately your smartphone has a "Manage Applications" tab that provides you with a list of all the applications running, the space consumed by each one and the last time you actually used any application. Powered with this knowledge, you can now make a quick and informed decision about the unnecessary applications that can be deleted to restore your phone to its optimal state.

However, when the same situation manifests itself at an enterprise level — where organizations have hundreds of applications they have acquired over the years — you could very easily be headed into a complex maze of blind turns without a possible escape.

Navigating a Complex Application Landscape

A typical IT organization expends close to 70% of its human and capital resources maintaining an ever-growing inventory of applications and supporting infrastructure. A lot of this effort is simply misdirected as the organization doesn't need a significant portion of these applications because they are simply not integral to the day-to-day functioning of its business. In many other cases, different departments within the company will implement applications on their own that have duplicate or overlapping functionality with other systems. It has been widely estimated that up to 50% of applications at a typical multinational could be shut down without the business knowing the difference.

Often times, this happens without IT even knowing about it and it creates challenges maintaining the authoritative source for business critical data. Most organizations have such complex application landscapes, that most IT teams have little idea about the number of applications in their inventory.

You need visibility into all your applications with key insights about each to make informed decisions on how to streamline, optimize and modernize them. Unfortunately, existing systematic and management processes typically do not provide a comprehensive, up-to-date view of the application portfolio for a number of reasons:

Business and Technical Fitness: Application information regarding business and technical fitness or related operational costs is incomplete or stored in multiple locations.

Inefficient Reporting: Unfortunately a lot of information is spreadsheet based, which leads to difficulties in flexible visual reporting.

Disjointed View: Most of the information is often managed separately at both enterprise and departmental levels leading to the lack of an integrated view.

Impact on Legacy Applications: Most organizations do not truly understand the impact of legacy applications on their business and continue to maintain them out of a fear of the unknown.

In addition, as internal IT teams are more concerned with putting out fires and showing short term cost savings, they shy away from engaging in a thorough application portfolio assessment. External IT vendors are engaged to provide application support and maintenance that helps an organization barely move forward while dragging along a bloated, expensive and often redundant portfolio of applications.

The Need for an Application Portfolio Assessment

The need of the hour is a multi-dimensional, top-down approach to effective application portfolio management. The first step is assessing the entire portfolio to create a comprehensive overview of your inventory. This includes the key insights and metrics needed to make intelligent decisions, and to develop a future state vision, strategy and roadmap. This type of roadmap is essential to drive efficiencies, fill gaps, eliminate redundancies, set the stage for modernization programs, and move towards those disruptive technologies and applications that will drive differentiation and competitive advantage for businesses today.

Including portfolio assessments as part of a traditional application management services engagement can help businesses proactively understand their applications footprint, connect the dots between legacy systems and functionality and weigh the benefits of retiring unnecessary applications. The next logical step in the journey is a rationalization exercise where a team of experts propose a roadmap that creates a lean, streamlined and efficient applications portfolio.

Working with your solutions provider from the very first step of assessment to the final stages of delivery ensures that all of the proposed business benefits and operational efficiencies are translated into timely and tangible business results. From the start, the intention should be to make the experience of managing applications as simple as pressing a button on your phone (almost).

Brendan Crowe is Global Application Services Director - Global Enterprise Services, Unisys

Related Links

Hot Topics

The Latest

When the Database Is the Problem, Is APM Enough?

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

From Cleanup to Prevention: The Future of Cloud-Native Cost Optimization

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

The Real Enterprise AI Risk Isn't Hallucinations

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 ...

Beyond Buy vs. Build: The New Playbook for Data Pipelines

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 ...

The Corporate Network Is Fading - Here's What Replaces It

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 ...

IT Leaders Must Establish a Network Data Architecture Practice

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 ...

Data Center Outages Are Decreasing but More Costly

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 ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

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 ...

TLS Certificate Expiration Is Becoming an Observability Problem

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 ...

Enterprise Cloud Observability: Choosing the Right Starting Point

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 ...

Taking Control of a Vast and Complex Applications Portfolio

Brendan Crowe

Imagine you're sitting in a coffee shop and you notice that your smartphone is being sluggish yet again. Applications aren't opening immediately, there's a constant lag with everything and sometimes things seem to crash midway. Fortunately your smartphone has a "Manage Applications" tab that provides you with a list of all the applications running, the space consumed by each one and the last time you actually used any application. Powered with this knowledge, you can now make a quick and informed decision about the unnecessary applications that can be deleted to restore your phone to its optimal state.

However, when the same situation manifests itself at an enterprise level — where organizations have hundreds of applications they have acquired over the years — you could very easily be headed into a complex maze of blind turns without a possible escape.

Navigating a Complex Application Landscape

A typical IT organization expends close to 70% of its human and capital resources maintaining an ever-growing inventory of applications and supporting infrastructure. A lot of this effort is simply misdirected as the organization doesn't need a significant portion of these applications because they are simply not integral to the day-to-day functioning of its business. In many other cases, different departments within the company will implement applications on their own that have duplicate or overlapping functionality with other systems. It has been widely estimated that up to 50% of applications at a typical multinational could be shut down without the business knowing the difference.

Often times, this happens without IT even knowing about it and it creates challenges maintaining the authoritative source for business critical data. Most organizations have such complex application landscapes, that most IT teams have little idea about the number of applications in their inventory.

You need visibility into all your applications with key insights about each to make informed decisions on how to streamline, optimize and modernize them. Unfortunately, existing systematic and management processes typically do not provide a comprehensive, up-to-date view of the application portfolio for a number of reasons:

Business and Technical Fitness: Application information regarding business and technical fitness or related operational costs is incomplete or stored in multiple locations.

Inefficient Reporting: Unfortunately a lot of information is spreadsheet based, which leads to difficulties in flexible visual reporting.

Disjointed View: Most of the information is often managed separately at both enterprise and departmental levels leading to the lack of an integrated view.

Impact on Legacy Applications: Most organizations do not truly understand the impact of legacy applications on their business and continue to maintain them out of a fear of the unknown.

In addition, as internal IT teams are more concerned with putting out fires and showing short term cost savings, they shy away from engaging in a thorough application portfolio assessment. External IT vendors are engaged to provide application support and maintenance that helps an organization barely move forward while dragging along a bloated, expensive and often redundant portfolio of applications.

The Need for an Application Portfolio Assessment

The need of the hour is a multi-dimensional, top-down approach to effective application portfolio management. The first step is assessing the entire portfolio to create a comprehensive overview of your inventory. This includes the key insights and metrics needed to make intelligent decisions, and to develop a future state vision, strategy and roadmap. This type of roadmap is essential to drive efficiencies, fill gaps, eliminate redundancies, set the stage for modernization programs, and move towards those disruptive technologies and applications that will drive differentiation and competitive advantage for businesses today.

Including portfolio assessments as part of a traditional application management services engagement can help businesses proactively understand their applications footprint, connect the dots between legacy systems and functionality and weigh the benefits of retiring unnecessary applications. The next logical step in the journey is a rationalization exercise where a team of experts propose a roadmap that creates a lean, streamlined and efficient applications portfolio.

Working with your solutions provider from the very first step of assessment to the final stages of delivery ensures that all of the proposed business benefits and operational efficiencies are translated into timely and tangible business results. From the start, the intention should be to make the experience of managing applications as simple as pressing a button on your phone (almost).

Brendan Crowe is Global Application Services Director - Global Enterprise Services, Unisys

Related Links

Hot Topics

The Latest

When the Database Is the Problem, Is APM Enough?

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

From Cleanup to Prevention: The Future of Cloud-Native Cost Optimization

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

The Real Enterprise AI Risk Isn't Hallucinations

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 ...

Beyond Buy vs. Build: The New Playbook for Data Pipelines

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 ...

The Corporate Network Is Fading - Here's What Replaces It

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 ...

IT Leaders Must Establish a Network Data Architecture Practice

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 ...

Data Center Outages Are Decreasing but More Costly

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 ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

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 ...

TLS Certificate Expiration Is Becoming an Observability Problem

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 ...

Enterprise Cloud Observability: Choosing the Right Starting Point

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 ...