Skip to main content

5 IT Operations Challenges – and 1 Main Cause

A recent survey of IT Operations executives found the following to be the most impactful challenges facing their teams:

1. Too much time spent resolving business-impacting application outages or slowdowns

IT Operations teams spend too many work hours resolving application performance problems. The biggest single opportunity to reduce this resource drain is to streamline the process of localizing the problem – in short, find the actual problem faster.

The Mean Time to Resolve issues (MTTR) is the primary measure that Operations teams use to determine their effectiveness in dealing with problems. Whenever Operations teams speak about management projects, the ultimate goal is to reduce MTTR.

Forrester Research’s Evelyn Oehrlich breaks down MTTR as the sum of four sub-components:

- The time it takes to detect a problem (measured by the MTTI or “Mean Time to Identify”)

- The time it takes to isolate the problem (measured by the MTTK or “Mean Time to Know”)

- The time it takes to implement the fix (measured by MTTF or “Mean Time to Fix”)

- The time it takes to verify that the fix is working (measured by MTTV or “Mean Time to Verify”)


Image removed.

As shown in the above graphic, the best opportunity to reduce the overall time to resolve issues is to cut the time spent isolating the root cause of the problem. Understanding that quickly finding where a problem occurred has the most potential for improvement, the focus should be on tools that isolate issues across the infrastructure, as opposed to solving more issues on specific platforms.

2. Too many Experts are required to help with application incidents

Having too many people spending time on bridge calls is a well-documented complaint. But really it is a symptom of a process problem. Bridge calls are attended by specialists – experts from the web tier, the database, the application server, etc. They are all on the same call to facilitate a broken process – that of using people to isolate the source of an application problem.

Management tools that provide a holistic view of application performance can eliminate the need to assemble the large team, and instead allow a single individual to isolate the problem component. With the source of the problem isolated, that individual can then engage only with the appropriate expert.

3. Problems are only discovered when users complain about them

As an Operations executive, I have a rule for my team that I never be surprised. I’m also realistic enough to know that sometimes things will go wrong. In an IT environment, outages will happen. The key is to not be surprised by the outages. This means proactive monitoring of applications – not just at the individual component level, but across the entire application infrastructure.

In today’s complex environments, relying on resource monitoring of individual servers is a sure-fire path to unpleasant surprises.

4. Management Tools can’t support the Mix of Technologies that Make up Apps

Management tools are built to address specific problems. Many of the APM tools in the field today were built to handle Java and .Net application code manipulation. These capabilities are important, but they don’t address problems that originate outside the application code. Enterprise applications of today are complicated animals – often consisting of several different discrete component types. IT Operations teams need to ensure that their management tools can identify and address the most common sources of application failures.

5. Implementation of mass virtualization, Private, and Hybrid Cloud

Virtualization and Private Cloud have become mainstream components of today’s application environments, and Hybrid Cloud is expected to be very big in 2013. Disconnecting the applications from the infrastructure specification creates a management visibility gap as to how systems are working together to deliver the business services. IT Operations teams need tools that can provide a complete application view across all these environments to be able to avoid the management blind spots.

One Major Cause: Application Complexity

The key difference in today’s applications from those running even 3 years ago is growing complexity. New technologies allow for more sophisticated enterprise applications - the days of applications being made up of a web server and a database are gone. Today’s applications feature a broad mixture of technologies and platforms, all with specialized functions and specialized management tools.

It’s this massive complexity that creates the other challenges:

- Today’s applications employ infrastructure components that alter the transaction paths and topology layout of applications on the fly, making it difficult or impossible to understand how transactions, applications and infrastructure work together.

- The resulting visibility gaps require experts for each platform to be available, just to TRY to understand (as a team) where applications and transactions go.

- Rapid change means that management tools struggle to keep up with the pace of change in technologies. In some cases, the platforms are so new that traditional management tools have no effective way of seeing even basic information.

- Finally, it is this dynamic complexity that makes it difficult for either IT Operations team members or full SWAT teams to solve problems when they occur. There are simply too many moving parts, too many new technologies, all put together in an unknown way (to the Operations Team) to deliver the desired business service.

The best way to deal with these challenges is to take a service-oriented approach to application service delivery. IT Operations teams that focus on how infrastructure performance impacts end-user service levels and use tools that manage transactions, applications, and infrastructure together will be able to overcome the 5 major challenges – cutting through those management gaps to provide true service management.

ABOUT Vic Nyman

Vic Nyman is the co-founder and COO of BlueStripe Software. Nyman has over 20 years of experience in systems management and APM and has held leadership positions at Wily Technology, IBM Tivoli, and Relicore/Symantec.

Hot Topics

The Latest

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

5 IT Operations Challenges – and 1 Main Cause

A recent survey of IT Operations executives found the following to be the most impactful challenges facing their teams:

1. Too much time spent resolving business-impacting application outages or slowdowns

IT Operations teams spend too many work hours resolving application performance problems. The biggest single opportunity to reduce this resource drain is to streamline the process of localizing the problem – in short, find the actual problem faster.

The Mean Time to Resolve issues (MTTR) is the primary measure that Operations teams use to determine their effectiveness in dealing with problems. Whenever Operations teams speak about management projects, the ultimate goal is to reduce MTTR.

Forrester Research’s Evelyn Oehrlich breaks down MTTR as the sum of four sub-components:

- The time it takes to detect a problem (measured by the MTTI or “Mean Time to Identify”)

- The time it takes to isolate the problem (measured by the MTTK or “Mean Time to Know”)

- The time it takes to implement the fix (measured by MTTF or “Mean Time to Fix”)

- The time it takes to verify that the fix is working (measured by MTTV or “Mean Time to Verify”)


Image removed.

As shown in the above graphic, the best opportunity to reduce the overall time to resolve issues is to cut the time spent isolating the root cause of the problem. Understanding that quickly finding where a problem occurred has the most potential for improvement, the focus should be on tools that isolate issues across the infrastructure, as opposed to solving more issues on specific platforms.

2. Too many Experts are required to help with application incidents

Having too many people spending time on bridge calls is a well-documented complaint. But really it is a symptom of a process problem. Bridge calls are attended by specialists – experts from the web tier, the database, the application server, etc. They are all on the same call to facilitate a broken process – that of using people to isolate the source of an application problem.

Management tools that provide a holistic view of application performance can eliminate the need to assemble the large team, and instead allow a single individual to isolate the problem component. With the source of the problem isolated, that individual can then engage only with the appropriate expert.

3. Problems are only discovered when users complain about them

As an Operations executive, I have a rule for my team that I never be surprised. I’m also realistic enough to know that sometimes things will go wrong. In an IT environment, outages will happen. The key is to not be surprised by the outages. This means proactive monitoring of applications – not just at the individual component level, but across the entire application infrastructure.

In today’s complex environments, relying on resource monitoring of individual servers is a sure-fire path to unpleasant surprises.

4. Management Tools can’t support the Mix of Technologies that Make up Apps

Management tools are built to address specific problems. Many of the APM tools in the field today were built to handle Java and .Net application code manipulation. These capabilities are important, but they don’t address problems that originate outside the application code. Enterprise applications of today are complicated animals – often consisting of several different discrete component types. IT Operations teams need to ensure that their management tools can identify and address the most common sources of application failures.

5. Implementation of mass virtualization, Private, and Hybrid Cloud

Virtualization and Private Cloud have become mainstream components of today’s application environments, and Hybrid Cloud is expected to be very big in 2013. Disconnecting the applications from the infrastructure specification creates a management visibility gap as to how systems are working together to deliver the business services. IT Operations teams need tools that can provide a complete application view across all these environments to be able to avoid the management blind spots.

One Major Cause: Application Complexity

The key difference in today’s applications from those running even 3 years ago is growing complexity. New technologies allow for more sophisticated enterprise applications - the days of applications being made up of a web server and a database are gone. Today’s applications feature a broad mixture of technologies and platforms, all with specialized functions and specialized management tools.

It’s this massive complexity that creates the other challenges:

- Today’s applications employ infrastructure components that alter the transaction paths and topology layout of applications on the fly, making it difficult or impossible to understand how transactions, applications and infrastructure work together.

- The resulting visibility gaps require experts for each platform to be available, just to TRY to understand (as a team) where applications and transactions go.

- Rapid change means that management tools struggle to keep up with the pace of change in technologies. In some cases, the platforms are so new that traditional management tools have no effective way of seeing even basic information.

- Finally, it is this dynamic complexity that makes it difficult for either IT Operations team members or full SWAT teams to solve problems when they occur. There are simply too many moving parts, too many new technologies, all put together in an unknown way (to the Operations Team) to deliver the desired business service.

The best way to deal with these challenges is to take a service-oriented approach to application service delivery. IT Operations teams that focus on how infrastructure performance impacts end-user service levels and use tools that manage transactions, applications, and infrastructure together will be able to overcome the 5 major challenges – cutting through those management gaps to provide true service management.

ABOUT Vic Nyman

Vic Nyman is the co-founder and COO of BlueStripe Software. Nyman has over 20 years of experience in systems management and APM and has held leadership positions at Wily Technology, IBM Tivoli, and Relicore/Symantec.

Hot Topics

The Latest

Seeing is believing, or in this case, seeing is understanding, according to New Relic's 2025 Observability Forecast for Retail and eCommerce report. Retailers who want to provide exceptional customer experiences while improving IT operations efficiency are leaning on observability ... Here are five key takeaways from the report ...

Technology leaders across the federal landscape are facing, and will continue to face, an uphill battle when it comes to fortifying their digital environments against hostile and persistent threat actors. On one hand, they are being asked to push digital transformation ... On the other hand, they are facing the fiscal uncertainty of continuing resolutions (CR) and government shutdowns looming near and far. In the face of these challenges, CIOs, CTOs, and CISOs must figure out how to modernize legacy systems and infrastructure while doing more with less and still defending against external and internal threats ...

Reliability is no longer proven by uptime alone, according to the The SRE Report 2026 from LogicMonitor. In the AI era, it is experienced through speed, consistency, and user trust, and increasingly judged by business impact. As digital services grow more complex and AI systems move into production, traditional monitoring approaches are struggling to keep pace, increasing the need for AI-first observability that spans applications, infrastructure, and the Internet ...

If AI is the engine of a modern organization, then data engineering is the road system beneath it. You can build the most powerful engine in the world, but without paved roads, traffic signals, and bridges that can support its weight, it will stall. In many enterprises, the engine is ready. The roads are not ...

In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...

In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...