Skip to main content

Digital Transformation Needs Intentionality

Larry Dragich

With the convergence of technology finding its way from the corporate world to our personal devices and home appliances, meeting the expectations of a quality customer experience is a formidable challenge.

Digital Transformation seems to be on everyone's radar but if there is no intentionality from the IT Executive who is sponsoring the program it becomes more of a loose correlation of technology initiatives under an IT strategy banner.

Consider some of the initiatives: Data/Analytics, Mobile Technology, Private Cloud, Artificial Intelligence (AI), Machine Learning, and the Internet of Things (IoT). All have their own unique role to play that is intrinsic to a Digital Transformation program. Although, when you step back and consider how to measure the success for such a program, things can get a little murky.

Digital Transformation requires more than just the latest technology, it's a mindset that iterative change is on the way and should be embraced. This also requires us to factor in the people and process parts of the equation and find ways to measure the end-user-experience (EUE).

One way to do this is to sponsor an Application Performance Monitoring (APM) initiative that can provide visibility to the business, help communicate the progress, and highlight the impacts to the organization.

Meaningful metrics can be difficult to obtain without a specific focus on business impact (transactions) and a concise way to collect them. Consider that a strong APM solution opens the door for better clarity on how each technology initiative affects the EUE, providing key metrics for a Digital Transformation program.

I recommend including all three monitoring factions within an APM strategy, Wire Data Analytics, Synthetic Transactions, and Agent Code Instrumentation.

1. Wire Data Analytics- Discover and decipher application performance data as it traverses the network.

2. Synthetic Transactions- Web robots that execute specific transactions for location-based availability and act as a barometer for measuring application performance.

3. Agent Code Instrumentation- Lightweight agents monitoring the application code as it executes from the Web and App servers. To gain visibility at the edge, script injection is often used for client render time.

Utilizing these overarching delivery mechanisms to provide input into a Machine Learning and/or AI solution has the potential to dramatically improve application delivery and performance across a variety of IT disciplines. This also lays the ground work to support a DevOps culture, providing an amplified feedback loop that is so desperately needed.

Once you develop a strategy on the best way to bring together the 3 monitoring factions, APM becomes "table stakes" on the digital transformation front because you can't improve what you don't measure.

The Latest

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

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

Digital Transformation Needs Intentionality

Larry Dragich

With the convergence of technology finding its way from the corporate world to our personal devices and home appliances, meeting the expectations of a quality customer experience is a formidable challenge.

Digital Transformation seems to be on everyone's radar but if there is no intentionality from the IT Executive who is sponsoring the program it becomes more of a loose correlation of technology initiatives under an IT strategy banner.

Consider some of the initiatives: Data/Analytics, Mobile Technology, Private Cloud, Artificial Intelligence (AI), Machine Learning, and the Internet of Things (IoT). All have their own unique role to play that is intrinsic to a Digital Transformation program. Although, when you step back and consider how to measure the success for such a program, things can get a little murky.

Digital Transformation requires more than just the latest technology, it's a mindset that iterative change is on the way and should be embraced. This also requires us to factor in the people and process parts of the equation and find ways to measure the end-user-experience (EUE).

One way to do this is to sponsor an Application Performance Monitoring (APM) initiative that can provide visibility to the business, help communicate the progress, and highlight the impacts to the organization.

Meaningful metrics can be difficult to obtain without a specific focus on business impact (transactions) and a concise way to collect them. Consider that a strong APM solution opens the door for better clarity on how each technology initiative affects the EUE, providing key metrics for a Digital Transformation program.

I recommend including all three monitoring factions within an APM strategy, Wire Data Analytics, Synthetic Transactions, and Agent Code Instrumentation.

1. Wire Data Analytics- Discover and decipher application performance data as it traverses the network.

2. Synthetic Transactions- Web robots that execute specific transactions for location-based availability and act as a barometer for measuring application performance.

3. Agent Code Instrumentation- Lightweight agents monitoring the application code as it executes from the Web and App servers. To gain visibility at the edge, script injection is often used for client render time.

Utilizing these overarching delivery mechanisms to provide input into a Machine Learning and/or AI solution has the potential to dramatically improve application delivery and performance across a variety of IT disciplines. This also lays the ground work to support a DevOps culture, providing an amplified feedback loop that is so desperately needed.

Once you develop a strategy on the best way to bring together the 3 monitoring factions, APM becomes "table stakes" on the digital transformation front because you can't improve what you don't measure.

The Latest

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

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...