Skip to main content

Q&A Part One: Gartner Talks About Business Value Dashboards

Pete Goldin
APMdigest

In Part One of APMdigest's exclusive interview, Colin Fletcher, Research Director, IT Operations Management for Gartner, talks about the emergence of the Business Value Dashboard (BVD).

APM: What areas do you cover for Gartner?

CF: I primarily cover IT event correlation and analysis and business service management for Gartner. Currently I also jointly cover a number of areas of monitoring in general, most recently adding network performance monitoring and diagnostics coverage. I also jointly cover IT operations analytics technologies; DevOps, in particular Application Release Automation; and of course Business Value Dashboards, and executive dashboards, with a basis in Business Service Management.

APM: Is “Business Value Dashboard” a Gartner term?

CF: It has been used in a couple of places but it is primarily a Gartner market definition.

APM: Can you describe the concept of Business Value Dashboards?

CF: Business Value Dashboards (BVD) uses a subjective and metrics-driven approach to demonstrate the direct impact of I&O (Infrastructure and Operations) as it relates to business performance and objectives. BVDs, and their underlying business value metrics, are about starting with identifying business performance measures and data, and then linking those measures to the line of business stakeholder's key specific I&O measures that drive those results that the business cares about.

APM: You mentioned BSM earlier. That is the first point I thought of when I heard the term Business Value Dashboards. It seems like BVD is the interface between the business and BSM.

CF: That is a good way to describe it. A Business Value Dashboard would be a line-of-business or role-specific view of a Business Service Management set of information. Although there is an important distinction: traditionally the Gartner definition of BSM is heavily steeped in the assumption of a number of levels of technical and logical groupings of IT elements and their associated service-level agreements, and building out those logical relationships as a foundation. To the contrary, Business Value Dashboards start from the other end, and while they will be informed from BSM-level relationships and interdependencies and service definitions, BVDs are not necessarily directly dependent on those relationships and that data. Ideally they are, but they do not presume the availability of that context.

APM: What do you see as the main distinction between a Business Value Dashboard and a traditional executive dashboard?

CF: BVDs tend to be more specific to lines of business specific metrics as they define their own performance and objectives. Executive dashboards tend to be focused at very high levels and also tend to be set up under the assumption of that Business Service Management style construct, well-defined logical groupings of infrastructure and applications and assorted guarantees with performance also measured and defined in very specific ways but still typically from a technical standpoint.

In the traditional executive dashboard it is still up to the user (typically not an IT practitioner) to decide at what level they want to establish importance or impact to their business performancemeasures. It is not to say that they cannot be used for Business Value Dashboards but they tend to make a lot of assumptions as to what is important to that particular business priority. Business Value Dashboard is different and simpler in many ways. It is about literally working through how existing lines of business outside of IT define their own performance – which is often very different using their own sets of data as well as reporting mechanisms and frequency – across multiple different tools and/or data sources in a way that ultimately makes sense to them whether or not it makes sense to the ultimate executive management.

So a sales organization in a particular region, for example, will have very specific goals, some of it may be about expense mitigation, growth, buyer retention. These are the types of points that rarely make it into traditional executive dashboards that are delivered by I&O organizations. And yet that is exactly the perspective that the lines of business care about, and that is precisely what Business Value Dashboards and business value metrics are designed to address.

The executive dashboard tends to be skewed by leaning towards the data we already have in hand, and that is easy to gather. It's human nature to do so. What is the relatively easy data to gather and report on? Basic things like uptime, Mean Time To Repair. These types of element categorization or domain technology categorization or asset information. These metrics are important, but I would argue that they are more often important to running the business of IT, which is different and independent of demonstrating impact of I&O on business performance. It is answering a different question for a different audience.

The Business Value Dashboard audience, much as defined for Business Service Management, is people outside of IT. It has to be something that they care about, that they want to use, and ultimately that is the measure of whether or not a dashboard is successful or not.

APM: Do you find confusion in the industry, when you talk to executives about BVDs. Do they say: I already have an executive dashboard?

CF: Absolutely. That is the response 90% of the time. If you follow up with a second question after that, which is: Have you polled your executives to see how frequently they interact with the dashboard? That tends to reveal an interesting insight, that executive dashboards are typically underutilized, if utilized at all, simply because they are often designed to answer questions that no one outside of IT is asking.

APM: Let's talk about that audience. Can you describe the profile of the Business Value Dashboard user?

CF: They tends to be IT-business liaisons. Line of business managers is the intended audience, with IT leaders and/or managers being the secondary audience. The purpose is to jointly understand what you are doing and why, and ultimately, how are you doing?

APM: Can users be on the level of CFO or CEO?

CF: They certainly can, and quite frankly that is often the target to find budget mandate, but ideally Business Value Dashboards start at a lower level, and ultimately feed higher-level BVDs for the topline executives.

There is a lot of groundwork that needs to be done. In I&O, we tend to focus on what we need, and for visibility, what the top executives need, but the most important people that we need to convince and win over are the ones in the middle. Because they are within lines of business where shadow IT continues to emerge and grow with increasing frequency. One of the reasons why is because they don't understand simply how precisely you are helping them accomplish their goals, much less agree with that. I think the biggest opportunity with BVDs is to get everybody involved as much possible.

Q&A Part Two: Gartner Talks About Business Value Dashboards

Hot Topic
The Latest
The Latest 10

The Latest

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

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

Q&A Part One: Gartner Talks About Business Value Dashboards

Pete Goldin
APMdigest

In Part One of APMdigest's exclusive interview, Colin Fletcher, Research Director, IT Operations Management for Gartner, talks about the emergence of the Business Value Dashboard (BVD).

APM: What areas do you cover for Gartner?

CF: I primarily cover IT event correlation and analysis and business service management for Gartner. Currently I also jointly cover a number of areas of monitoring in general, most recently adding network performance monitoring and diagnostics coverage. I also jointly cover IT operations analytics technologies; DevOps, in particular Application Release Automation; and of course Business Value Dashboards, and executive dashboards, with a basis in Business Service Management.

APM: Is “Business Value Dashboard” a Gartner term?

CF: It has been used in a couple of places but it is primarily a Gartner market definition.

APM: Can you describe the concept of Business Value Dashboards?

CF: Business Value Dashboards (BVD) uses a subjective and metrics-driven approach to demonstrate the direct impact of I&O (Infrastructure and Operations) as it relates to business performance and objectives. BVDs, and their underlying business value metrics, are about starting with identifying business performance measures and data, and then linking those measures to the line of business stakeholder's key specific I&O measures that drive those results that the business cares about.

APM: You mentioned BSM earlier. That is the first point I thought of when I heard the term Business Value Dashboards. It seems like BVD is the interface between the business and BSM.

CF: That is a good way to describe it. A Business Value Dashboard would be a line-of-business or role-specific view of a Business Service Management set of information. Although there is an important distinction: traditionally the Gartner definition of BSM is heavily steeped in the assumption of a number of levels of technical and logical groupings of IT elements and their associated service-level agreements, and building out those logical relationships as a foundation. To the contrary, Business Value Dashboards start from the other end, and while they will be informed from BSM-level relationships and interdependencies and service definitions, BVDs are not necessarily directly dependent on those relationships and that data. Ideally they are, but they do not presume the availability of that context.

APM: What do you see as the main distinction between a Business Value Dashboard and a traditional executive dashboard?

CF: BVDs tend to be more specific to lines of business specific metrics as they define their own performance and objectives. Executive dashboards tend to be focused at very high levels and also tend to be set up under the assumption of that Business Service Management style construct, well-defined logical groupings of infrastructure and applications and assorted guarantees with performance also measured and defined in very specific ways but still typically from a technical standpoint.

In the traditional executive dashboard it is still up to the user (typically not an IT practitioner) to decide at what level they want to establish importance or impact to their business performancemeasures. It is not to say that they cannot be used for Business Value Dashboards but they tend to make a lot of assumptions as to what is important to that particular business priority. Business Value Dashboard is different and simpler in many ways. It is about literally working through how existing lines of business outside of IT define their own performance – which is often very different using their own sets of data as well as reporting mechanisms and frequency – across multiple different tools and/or data sources in a way that ultimately makes sense to them whether or not it makes sense to the ultimate executive management.

So a sales organization in a particular region, for example, will have very specific goals, some of it may be about expense mitigation, growth, buyer retention. These are the types of points that rarely make it into traditional executive dashboards that are delivered by I&O organizations. And yet that is exactly the perspective that the lines of business care about, and that is precisely what Business Value Dashboards and business value metrics are designed to address.

The executive dashboard tends to be skewed by leaning towards the data we already have in hand, and that is easy to gather. It's human nature to do so. What is the relatively easy data to gather and report on? Basic things like uptime, Mean Time To Repair. These types of element categorization or domain technology categorization or asset information. These metrics are important, but I would argue that they are more often important to running the business of IT, which is different and independent of demonstrating impact of I&O on business performance. It is answering a different question for a different audience.

The Business Value Dashboard audience, much as defined for Business Service Management, is people outside of IT. It has to be something that they care about, that they want to use, and ultimately that is the measure of whether or not a dashboard is successful or not.

APM: Do you find confusion in the industry, when you talk to executives about BVDs. Do they say: I already have an executive dashboard?

CF: Absolutely. That is the response 90% of the time. If you follow up with a second question after that, which is: Have you polled your executives to see how frequently they interact with the dashboard? That tends to reveal an interesting insight, that executive dashboards are typically underutilized, if utilized at all, simply because they are often designed to answer questions that no one outside of IT is asking.

APM: Let's talk about that audience. Can you describe the profile of the Business Value Dashboard user?

CF: They tends to be IT-business liaisons. Line of business managers is the intended audience, with IT leaders and/or managers being the secondary audience. The purpose is to jointly understand what you are doing and why, and ultimately, how are you doing?

APM: Can users be on the level of CFO or CEO?

CF: They certainly can, and quite frankly that is often the target to find budget mandate, but ideally Business Value Dashboards start at a lower level, and ultimately feed higher-level BVDs for the topline executives.

There is a lot of groundwork that needs to be done. In I&O, we tend to focus on what we need, and for visibility, what the top executives need, but the most important people that we need to convince and win over are the ones in the middle. Because they are within lines of business where shadow IT continues to emerge and grow with increasing frequency. One of the reasons why is because they don't understand simply how precisely you are helping them accomplish their goals, much less agree with that. I think the biggest opportunity with BVDs is to get everybody involved as much possible.

Q&A Part Two: Gartner Talks About Business Value Dashboards

Hot Topic
The Latest
The Latest 10

The Latest

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

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.