Skip to main content

The Threat Behind Digital Transformation

Jonah Kowall

The age of digital disruption is upon us, as the last decade alone has proven in terms of technology and disruption with the progression of organizations like Uber, Airbnb, and Netflix. We are also on the brink of new disruptions in industry, including banking or payments, insurance, healthcare, construction, packaging, and many more. These not only come from startups disrupting a sector, but companies being able to shift from their existing focus areas to build on new opportunities. They’re driven internally or by creating a new spinoff company into additional areas.

The CxO organization is becoming more concerned with outsiders entering into their markets. In the past, the cost of entry into a new market was significantly higher than it is today. Digital businesses and software-driven business models are changing the playing field, for new entrants to shift into new markets. The cost of experimentation continues to decrease, with lower cost computing models that allow for the rental of resources and software.

Open source plays a key role in both building new applications and creating community leverage; and senior executives are taking notice. IBM’s Global C-Suite Study is a great data set consisting of data collected between January and June 2015. They surveyed 5,247 business leaders from 21 industries in more than 70 countries. The sample comprises 818 CEOs, 643 CFOs, 601 CHROs, 1,805 CIOs, 723 CMOs, and 657 COOs :


Today’s native digital generations prefer to work on digital channels versus in-person channels. This ongoing trend has given rise to improvements in customer service, where interactions are delivered across multiple digital channels, ranging from social channels like Twitter and Facebook to text and voice communications. However, there is still more work to be done to unify these platforms more seamlessly. Technologies such as social, chat, and more recently, bots create the personal touch in a more scalable manner, reducing costs and increasing customer satisfaction. These trends will continually take hold, personalization and fast touch points are valued by today’s users who seemingly have less time than ever before.

The level of patience and complexity involved in making these channels seamless is an increasing challenge with today’s IT complexity. Your customers will not tolerate failure, and expect technology to just work. IBM’s survey data confirms this trend.


This accelerating trend is what will differentiate those businesses who learn to engage in new and differentiated ways across multiple channels. Companies which lead, versus those that follow have very different perspectives on what will likely transpire during a time of disruption.

In Figure 8 below, those indicated as torchbearers see companies who look for another market to expand into being able to enter these markets quickly as innovators in another segment or market. Similarly, these first-mover companies see the need to enter into new or adjacent markets. For this reason you see most companies creating labs or innovation centers. We increasingly see next generation visibility being required for these new and highly agile software systems. This demand is critical for survival, innovation, and growth.

These experiments can only be done promptly when the organization adopts smaller agile teams across the business and technology groups. Breaking up large, and likely slow moving monolithic organizations, software, and systems into smaller units which operate independently. The ability to experimentation and make decisions on their own.

The companies who lead tend to do this far more frequently than those who follow or are laggards. We see this regularly in our customer base, where a large degree of diversity exists in the autonomy within each team. The question remains as to how this will play out with economic changes or political change.


In summary, while this data and analysis confirm many trends, it shows clearly different and increasingly changed thinking as digital becomes the preferred channel for many businesses. The IBM data also informs that decentralized decision making and experimentation are clearly taking hold, but those who lead are in a different place than those who follow. It will be interesting to see how this progresses with IBMs new survey data.

The Latest

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

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

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

The Threat Behind Digital Transformation

Jonah Kowall

The age of digital disruption is upon us, as the last decade alone has proven in terms of technology and disruption with the progression of organizations like Uber, Airbnb, and Netflix. We are also on the brink of new disruptions in industry, including banking or payments, insurance, healthcare, construction, packaging, and many more. These not only come from startups disrupting a sector, but companies being able to shift from their existing focus areas to build on new opportunities. They’re driven internally or by creating a new spinoff company into additional areas.

The CxO organization is becoming more concerned with outsiders entering into their markets. In the past, the cost of entry into a new market was significantly higher than it is today. Digital businesses and software-driven business models are changing the playing field, for new entrants to shift into new markets. The cost of experimentation continues to decrease, with lower cost computing models that allow for the rental of resources and software.

Open source plays a key role in both building new applications and creating community leverage; and senior executives are taking notice. IBM’s Global C-Suite Study is a great data set consisting of data collected between January and June 2015. They surveyed 5,247 business leaders from 21 industries in more than 70 countries. The sample comprises 818 CEOs, 643 CFOs, 601 CHROs, 1,805 CIOs, 723 CMOs, and 657 COOs :


Today’s native digital generations prefer to work on digital channels versus in-person channels. This ongoing trend has given rise to improvements in customer service, where interactions are delivered across multiple digital channels, ranging from social channels like Twitter and Facebook to text and voice communications. However, there is still more work to be done to unify these platforms more seamlessly. Technologies such as social, chat, and more recently, bots create the personal touch in a more scalable manner, reducing costs and increasing customer satisfaction. These trends will continually take hold, personalization and fast touch points are valued by today’s users who seemingly have less time than ever before.

The level of patience and complexity involved in making these channels seamless is an increasing challenge with today’s IT complexity. Your customers will not tolerate failure, and expect technology to just work. IBM’s survey data confirms this trend.


This accelerating trend is what will differentiate those businesses who learn to engage in new and differentiated ways across multiple channels. Companies which lead, versus those that follow have very different perspectives on what will likely transpire during a time of disruption.

In Figure 8 below, those indicated as torchbearers see companies who look for another market to expand into being able to enter these markets quickly as innovators in another segment or market. Similarly, these first-mover companies see the need to enter into new or adjacent markets. For this reason you see most companies creating labs or innovation centers. We increasingly see next generation visibility being required for these new and highly agile software systems. This demand is critical for survival, innovation, and growth.

These experiments can only be done promptly when the organization adopts smaller agile teams across the business and technology groups. Breaking up large, and likely slow moving monolithic organizations, software, and systems into smaller units which operate independently. The ability to experimentation and make decisions on their own.

The companies who lead tend to do this far more frequently than those who follow or are laggards. We see this regularly in our customer base, where a large degree of diversity exists in the autonomy within each team. The question remains as to how this will play out with economic changes or political change.


In summary, while this data and analysis confirm many trends, it shows clearly different and increasingly changed thinking as digital becomes the preferred channel for many businesses. The IBM data also informs that decentralized decision making and experimentation are clearly taking hold, but those who lead are in a different place than those who follow. It will be interesting to see how this progresses with IBMs new survey data.

The Latest

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

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

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