Skip to main content

Second Gear Application Performance Management

Marcel M. Karman

In 2014 Gartner predicted that "75 percent of IT organizations will be bi-modal in some way by 2017." We are in the midst of this two-speed IT approach that organizations are adopting at an increasing rate to stay relevant for their customers. Where Speed 1 is the traditional IT that is being managed by the IT Operations persona, and Speed 2 is the agile IT where within the organization especially the Developer persona and the Line of Business Persona are involved to get the most out of the digital innovations that flood our daily lives.

One thing that these personas have in common is that they have a need for monitoring. In this blog I will focus on the needs of the various personas.

The Developer

Obviously a developer wants to build nice applications or cloud services. They want to build apps quickly like startups do, without being bogged down by testing and support, and wants to spend time on improving things rather than fixing things.

The requirements of a developer are that they want to be sure that their application is running and performing well for their end-users and if it’s not functioning properly than they need monitoring to help them to find the problem. And very important; the monitoring tool should not be intrusive and be very simple to use. Tools should fit the startup mentality workflow!

The Line of Business

You can say that the Line of Business (LoB) represent the organization`s customers. So they commonly want to improve the customer satisfaction and be able to see which services are successful and which ones are not. Requirements of the LoB are often that they want visibility into the customer experience of applications and services.

IT Operations

The IT Operations persona is another large user of monitoring solutions. Their point of view differs very much of that of the LoB and the Developer. Where the Developer and LoB have a startup mentality, the IT Operations persona most of the time has a mentality far from that. IT Operations has to deal with the scaling of applications that are being managed and they have to meet security and compliance standards as well. Important to them is that they can deliver applications in a controlled and efficient way. A status quo situation would be ideal for them because this improves the quality of the IT services and minimizes the risk of outages. However new services must be introduced by the organization to stay competitive, but this can destabilize the infrastructure and is therefore risky. So IT Operations is always in a balancing act; create stability – and managing newly introduced applications and services in the environment.

The requirements of IT Operations are at a minimum to manage services across the entire hybrid cloud environment and rapidly determine the cause of any issues. So therefore they need end-to-end visibility and control – aka One Dashboard where everything comes together from the on-premise environment and all the different cloud environments.

As an example; IT Operations could use an on-premise Application Performance Management (APM) solution that enables them to obtain the required visibility and control of the hybrid cloud environment. All the monitoring metrics that originate from the different environments (public and private cloud) can be shown in One Dashboard where IT Operations has an instant view on what is happening. Furthermore, IT Operations has always the need to work as effective and efficiently as possible and therefore they need to spot emerging problems fast which is possible with the APM solution build-in innovative analytics that can prevent possible costly outages.

Bringing it together

Below figure gives an overview of how an ideal APM solution could be used in the organization, where the three different personas all can use the same solution. Through the whole organization you should work with one solution, with the same look and feel, and that can fulfill the requirements of the different personas of the organization. The personas can see in their personal monitoring dashboard the items that are important for them and take the required actions when needed. Furthermore this solution can be used in different delivery models, such as on-premise, SaaS and PaaS, so plenty of choices to choose from, or to use jointly.

In the end

In the end there is only one point of view in the organization that really matters. How does the CIO feel about monitoring in the hybrid cloud environment with an organization that is running on two speeds?

The CIO point of view is a "very simple one". Most of the time the CIO has targets on Minimizing Risk, Reducing Costs and Improving Service Levels for the organization’s customers. Therefore an enterprise all-encompassing Application Performance Monitoring solution that can be delivered in multiple delivery models is an ideal fit. So this type of a hybrid APM solution is perfect match for the Two-speed IT approach that organizations are experiencing.

Marcel M. Karman is a Cloud Architect at IBM.

Hot Topics

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

Second Gear Application Performance Management

Marcel M. Karman

In 2014 Gartner predicted that "75 percent of IT organizations will be bi-modal in some way by 2017." We are in the midst of this two-speed IT approach that organizations are adopting at an increasing rate to stay relevant for their customers. Where Speed 1 is the traditional IT that is being managed by the IT Operations persona, and Speed 2 is the agile IT where within the organization especially the Developer persona and the Line of Business Persona are involved to get the most out of the digital innovations that flood our daily lives.

One thing that these personas have in common is that they have a need for monitoring. In this blog I will focus on the needs of the various personas.

The Developer

Obviously a developer wants to build nice applications or cloud services. They want to build apps quickly like startups do, without being bogged down by testing and support, and wants to spend time on improving things rather than fixing things.

The requirements of a developer are that they want to be sure that their application is running and performing well for their end-users and if it’s not functioning properly than they need monitoring to help them to find the problem. And very important; the monitoring tool should not be intrusive and be very simple to use. Tools should fit the startup mentality workflow!

The Line of Business

You can say that the Line of Business (LoB) represent the organization`s customers. So they commonly want to improve the customer satisfaction and be able to see which services are successful and which ones are not. Requirements of the LoB are often that they want visibility into the customer experience of applications and services.

IT Operations

The IT Operations persona is another large user of monitoring solutions. Their point of view differs very much of that of the LoB and the Developer. Where the Developer and LoB have a startup mentality, the IT Operations persona most of the time has a mentality far from that. IT Operations has to deal with the scaling of applications that are being managed and they have to meet security and compliance standards as well. Important to them is that they can deliver applications in a controlled and efficient way. A status quo situation would be ideal for them because this improves the quality of the IT services and minimizes the risk of outages. However new services must be introduced by the organization to stay competitive, but this can destabilize the infrastructure and is therefore risky. So IT Operations is always in a balancing act; create stability – and managing newly introduced applications and services in the environment.

The requirements of IT Operations are at a minimum to manage services across the entire hybrid cloud environment and rapidly determine the cause of any issues. So therefore they need end-to-end visibility and control – aka One Dashboard where everything comes together from the on-premise environment and all the different cloud environments.

As an example; IT Operations could use an on-premise Application Performance Management (APM) solution that enables them to obtain the required visibility and control of the hybrid cloud environment. All the monitoring metrics that originate from the different environments (public and private cloud) can be shown in One Dashboard where IT Operations has an instant view on what is happening. Furthermore, IT Operations has always the need to work as effective and efficiently as possible and therefore they need to spot emerging problems fast which is possible with the APM solution build-in innovative analytics that can prevent possible costly outages.

Bringing it together

Below figure gives an overview of how an ideal APM solution could be used in the organization, where the three different personas all can use the same solution. Through the whole organization you should work with one solution, with the same look and feel, and that can fulfill the requirements of the different personas of the organization. The personas can see in their personal monitoring dashboard the items that are important for them and take the required actions when needed. Furthermore this solution can be used in different delivery models, such as on-premise, SaaS and PaaS, so plenty of choices to choose from, or to use jointly.

In the end

In the end there is only one point of view in the organization that really matters. How does the CIO feel about monitoring in the hybrid cloud environment with an organization that is running on two speeds?

The CIO point of view is a "very simple one". Most of the time the CIO has targets on Minimizing Risk, Reducing Costs and Improving Service Levels for the organization’s customers. Therefore an enterprise all-encompassing Application Performance Monitoring solution that can be delivered in multiple delivery models is an ideal fit. So this type of a hybrid APM solution is perfect match for the Two-speed IT approach that organizations are experiencing.

Marcel M. Karman is a Cloud Architect at IBM.

Hot Topics

The Latest

Outages aren't new. What's new is how quickly they spread across systems, vendors, regions and customer workflows. The moment that performance degrades, expectations escalate fast. In today's always-on environment, an outage isn't just a technical event. It's a trust event ...

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...