Skip to main content

3 Tips for Reining in Your Application Portfolio

Gary Mann

Your organization's Application Management and IT Help Desk teams are your "first line of defense," and they also wear many hats. They help users resolve problems, manage the organization's technology portfolio, and ensure technology is available to end users 24x7. The constant juggle of day-to-day priorities can be dizzying.

One of the biggest challenges they face is the management of application portfolios, which can quickly become crowded, redundant, or even obsolete due to years of adding software with overlapping functionalities. This is only getting more complex with the emergence of new technology. Mergers and acquisitions also compound the problem as IT teams look to bring two application portfolios together. Unless your application portfolio is meticulously maintained, sprawl and application redundancies will occur, tying up IT resources more than they already are and driving up operating costs — all of which can impact application performance.

To help ensure your application and help desk operations are effective and manageable, there are a few simple things that IT leaders can do:

1. Assess the Strength of Your Application Management Program

Before you can make any changes to your program you need to understand its current state — down to the true cost of every application. A few key questions to ask include:

■ How have our applications been performing over time? 

■ Are some applications becoming obsolete or redundant? 

■ Does the cost to maintain an application align with its business value? 

■ Is the application portfolio able to meet changing business conditions? 

■ Does the program allow for innovation and improvement initiatives?

Completing this assessment isn't a simple task and it's not a one and done process. Dig deep and reassess regularly. The frequency of conducting an assessment depends entirely on the maturity of the organization. You need to question how dynamic and volatile the market place is, and what role the application portfolio plays in driving the organization's strategy.

For example, in some industries applications, and therefore the application management program, are ground zero not only for operational effectiveness, but also compliance.

Also, once the first assessment is done will you will want to put controls in place to monitor delivery and thresholds for making changes to your plan. The more mature your processes are to keep control and track thresholds the less frequently an assessment is needed. It will also depend on the size of the organization. It can be ungainly to make a blanket statement that you will analyze the application management program annually, but take several months to complete the assessment. You need to avoid analysis paralysis. One size does not fit all.

2. Build an Application Management Road Map

As a second step, once you have completed your initial assessment, and identified gaps, you will want to build an application management road map. Again, this is not a simple step in the least. Developing a roadmap requires strategic and tactical thinking. Priorities should be based on the direction you want to take your organization – whether it is building new capabilities to meet changing needs in the market place, or looking for ways to be more efficient with company's resources by identifying ways to decrease operational costs. These decisions are to be made in concert with the user community as they are the ones that will be most impacted by any changes you make to the application portfolio. End users can be very helpful in setting priorities and determining what applications are most important at the end of the day.

3. Monitor and Reassess

The final step, start all over again. Once you have conducted an assessment, built your roadmap and plan, and begun executing, you need to continue to monitor your application portfolio in order to make mid-course adjustments. Markets do not stagnate. Consequently, users' demands and strategic directions will change as well. If you have done your work correctly, the adjustments that need to be made will be minor, but they will occur. This may be as simple as a reprioritization of a small project, to a rethink of what is needed to support a market strategy.

What is important in all of this is to ensure you have clear methodologies to conduct the assessments, monitor the roadmap, and make mid-course adjustments.

In my 30 years in the industry, I have seen many organizations struggle with wrapping their arms around their ever-changing application portfolio, and ultimately giving their IT team breathing room to focus on strategic projects. Whether addressing these improvement initiatives in-house, or looking for outside assistance, following these steps will help your organization more effectively manage its technology resources.

Hot Topics

The Latest

As AI moves from generating responses to performing actions, the need for trust increases exponentially. And as organizations enlist AI agents for increasingly sophisticated business processes, trust is going to be the single most important theme for spurring adoption. What can organizations do to build trustworthy AI agents? ...

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

3 Tips for Reining in Your Application Portfolio

Gary Mann

Your organization's Application Management and IT Help Desk teams are your "first line of defense," and they also wear many hats. They help users resolve problems, manage the organization's technology portfolio, and ensure technology is available to end users 24x7. The constant juggle of day-to-day priorities can be dizzying.

One of the biggest challenges they face is the management of application portfolios, which can quickly become crowded, redundant, or even obsolete due to years of adding software with overlapping functionalities. This is only getting more complex with the emergence of new technology. Mergers and acquisitions also compound the problem as IT teams look to bring two application portfolios together. Unless your application portfolio is meticulously maintained, sprawl and application redundancies will occur, tying up IT resources more than they already are and driving up operating costs — all of which can impact application performance.

To help ensure your application and help desk operations are effective and manageable, there are a few simple things that IT leaders can do:

1. Assess the Strength of Your Application Management Program

Before you can make any changes to your program you need to understand its current state — down to the true cost of every application. A few key questions to ask include:

■ How have our applications been performing over time? 

■ Are some applications becoming obsolete or redundant? 

■ Does the cost to maintain an application align with its business value? 

■ Is the application portfolio able to meet changing business conditions? 

■ Does the program allow for innovation and improvement initiatives?

Completing this assessment isn't a simple task and it's not a one and done process. Dig deep and reassess regularly. The frequency of conducting an assessment depends entirely on the maturity of the organization. You need to question how dynamic and volatile the market place is, and what role the application portfolio plays in driving the organization's strategy.

For example, in some industries applications, and therefore the application management program, are ground zero not only for operational effectiveness, but also compliance.

Also, once the first assessment is done will you will want to put controls in place to monitor delivery and thresholds for making changes to your plan. The more mature your processes are to keep control and track thresholds the less frequently an assessment is needed. It will also depend on the size of the organization. It can be ungainly to make a blanket statement that you will analyze the application management program annually, but take several months to complete the assessment. You need to avoid analysis paralysis. One size does not fit all.

2. Build an Application Management Road Map

As a second step, once you have completed your initial assessment, and identified gaps, you will want to build an application management road map. Again, this is not a simple step in the least. Developing a roadmap requires strategic and tactical thinking. Priorities should be based on the direction you want to take your organization – whether it is building new capabilities to meet changing needs in the market place, or looking for ways to be more efficient with company's resources by identifying ways to decrease operational costs. These decisions are to be made in concert with the user community as they are the ones that will be most impacted by any changes you make to the application portfolio. End users can be very helpful in setting priorities and determining what applications are most important at the end of the day.

3. Monitor and Reassess

The final step, start all over again. Once you have conducted an assessment, built your roadmap and plan, and begun executing, you need to continue to monitor your application portfolio in order to make mid-course adjustments. Markets do not stagnate. Consequently, users' demands and strategic directions will change as well. If you have done your work correctly, the adjustments that need to be made will be minor, but they will occur. This may be as simple as a reprioritization of a small project, to a rethink of what is needed to support a market strategy.

What is important in all of this is to ensure you have clear methodologies to conduct the assessments, monitor the roadmap, and make mid-course adjustments.

In my 30 years in the industry, I have seen many organizations struggle with wrapping their arms around their ever-changing application portfolio, and ultimately giving their IT team breathing room to focus on strategic projects. Whether addressing these improvement initiatives in-house, or looking for outside assistance, following these steps will help your organization more effectively manage its technology resources.

Hot Topics

The Latest

As AI moves from generating responses to performing actions, the need for trust increases exponentially. And as organizations enlist AI agents for increasingly sophisticated business processes, trust is going to be the single most important theme for spurring adoption. What can organizations do to build trustworthy AI agents? ...

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...