Visible AI, Invisible Outcomes? Aligning AI/ITSM investments to Business Value

Perhaps you’ve noticed a pattern in organizations exploring AI for IT service management (ITSM) solutions. 

The story typically goes like this: A vendor demo impresses and captivates an executive team with an AI-powered virtual agent, a copilot for the service desk, or a predictive dashboard that seemingly reads the future. Budgets are found, projects are kicked off, and AI starts showing up in roadmaps and town halls. 

Six to twelve months later…something isn’t quite right. 

Yes, there is AI. People can see it. There’s a chatbot on the portal. There are suggested responses in the ITSM tool. There are new dashboards. But improved service performance? Better consumer and employee experiences? Meaningful and relevant business outcomes? 

Not so much. The problem isn’t that AI “doesn’t work.” The problem is that most organizations start with visible AI rather than with service outcomes.

What is “Visible AI”? 

 “Visible AI” represents AI capabilities that stakeholders can directly see and touch, such as: 

• Virtual agents and chatbots in the service portal 
• Agent assists or copilots in ITSM and support tools 
• AI-generated responses or recommendations in tickets and emails 
• Predictive alerts and “smart” dashboards for operations 

These capabilities are attractive and highly marketable. They demo well. They’re easy to showcase in town halls and leadership meetings. They look like progress. 

But visibility is different from value. If these visible uses of AI are not clearly aligned to service outcomes—and not supported by the right strategy, business case, knowledge, processes, and governance—they quickly become nothing more than “AI theater”: lots of show, with extraordinarily little impact.

The same old trap: starting with technology instead of services 

Too many AI-in-ITSM journeys start by asking, “Where can we use this AI feature?” instead of “What service outcomes do we need to improve?”  

Starting the solution design with the technology is backward. 

ITSM, at its core, is about services and the outcomes those services enable for the business. AI doesn’t change that. In fact, AI will amplify whatever you feed it—good or bad. 

If your starting point is an AI feature, such as implementing a chatbot, deploying a copilot, or enabling the predictive model, you’re making technology decisions in a vacuum. You might reduce some human workload here and there, but you’re unlikely to improve what really matters: productivity, reliability, risk, and experience. 

Visible AI only becomes valuable when it is intentionally embedded into workflows in ways that improve those outcomes.

Another trap: conducting pilots that prove nothing 

Another trap many organizations fall into is the way they conduct AI pilots. 

Many AI pilots never graduate to full production. When you take a close look at why these pilots didn’t succeed, a common reason is apparent: the pilot was never designed as a service-outcome experiment. Business-relevant success criteria weren’t clearly defined, stakeholder alignment was weak or non-existent, and there was no structured evaluation model.  

Instead, the “pilot” was conducted to prove that the technology “works.” 

• Can the virtual agent answer questions? (Yes, of course.) 
• Can the copilot suggest responses? (Yes, of course.) 
• Can the predictive dashboard show alerts? (Yes, of course.) 

Sorry, but that’s not enough. Candidly, the technology always works – otherwise, it wouldn’t be on the market. What about the results delivered by AI?

AI pilots should assess outcome-focused hypotheses like: 

• “If we use an AI virtual agent for these ten high-volume requests, we will reduce time-to-fulfillment for the ‘Access and Accounts’ service by 25% while maintaining or improving satisfaction.” 
• “If we introduce AI-assisted responses in the service desk for Service X, we will reduce handle time by Y% without increasing reopens.” 

Think of these outcome-focused pilots as living business use cases. You’re not just proving that the AI runs—you’re proving that it improves services in the ways that matter to your organization. 

When you design pilots around outcomes, you have a clear basis for deciding whether and how to move from pilot to production. You’re not asking, “Did the AI work?” You’re asking, “Did the service improve?” and “Did AI deliver relevant and measurable outcomes?” 

And those are much better questions.

Start AI where ITSM should always start: with outcomes 

If you’re hoping that AI will improve your service management capabilities, the place to start is with your ITSM environment. Ask yourself these questions: 

• What is your ITSM strategy? 
• Are you achieving your ITSM strategy? How do you know?  
• How has ITSM improved business outcomes? How do you know? 
• Is your ITSM capability mature enough to support AI adoption? 

If you can’t answer these questions, then you’re not ready to introduce AI within your service management environment. You’ll need to first address your ITSM challenges before looking at AI.  

But if your ITSM strategy delivers meaningful, impactful business outcomes, you are ready to take the next steps to introduce AI. Now it’s time to step back and ask an additional set of questions: 

• What are your overarching goals for AI?  
• What are the 3–5 services that matter most to your organization right now? 
• For each of these services, what outcomes matter most? 
• Faster time-to-resolution? 
• Higher employee or customer satisfaction? 
• Fewer business disruptions? 
• Reduced risk or improved compliance? 
• Lower cost-to-serve without sacrificing quality? 

Use these answers to identify opportunities where AI can deliver meaningful impact, rather than just picking whatever is easiest to automate.  

Once you are clear on service outcomes, you can start thinking about where AI might help. The conversation shifts from “should we buy this AI feature?” to “where can AI measurably improve the outcomes of our most critical services?”  

Defining the business case for how and where AI might help links AI adoption to business goals, expected benefits, costs, and risks. Defining solution evaluation criteria helps ensure that decisions are objective, consistent, and aligned with the goals identified in the business case.  

A virtual agent might make sense for one service but not another. A copilot might benefit one support team while adding little value for others. Predictive capabilities might be crucial in some operational areas but overkill in others. 

Without looking through the lens of services and outcomes, everything looks like a potential AI use case. With that lens, you can be selective and strategic.

The invisible foundation that makes visible AI work 

This is where the rest of your AI approach comes into play—and where your other ITSM investments must connect. 

Visible AI relies heavily on things that are often invisible to stakeholders, but are absolutely critical: 

• Strategy – Your AI strategy should spell out not only where AI might be used, but also what organizational change, data, skills, budget, and infrastructure will be required to make those uses successful. In other words, it outlines the foundations that must be in place before you present AI to your stakeholders. 
• Governance – Without clear policies and guidance on data quality, model usage, ethics, bias, and monitoring, AI can behave unpredictably and erode trust. Governance isn’t bureaucracy; it’s how you ensure that AI decisions remain aligned with your values and your risk tolerance over time. 
• Processes and practices – If your incident, request, change, and other service management practices are inconsistent or poorly defined, AI will simply accelerate your inconsistencies. “Smarter” routing doesn’t help if the underlying workflows are broken or misaligned with how the business actually works. 
• Knowledge – If your knowledge is incomplete, out of date, or scattered, your AI virtual agent will confidently provide bad answers faster than ever. AI amplifies the state of your knowledge, for better or worse. This is why “AI and knowledge: The foundation you can’t skip” is not optional reading. 
• Business Case – Securing and sustaining senior management commitment is essential to success, so once a viable solution is identified, present a clear business case that outlines its value. Address the technical and cultural challenges of AI adoption, highlight the opportunities it brings to service management, and explain the benefits, risk management approach, and measures of success. Also clarify the consequences of inaction and, most importantly, obtain firm commitment from management. 

Admittedly, these “invisible” elements don’t demo well in a town hall or executive management meeting. You can’t show a cool video of a well-designed knowledge article, a clearly defined and documented workflow, or a thoughtful data governance policy. But these invisible elements will make or break the success of your visible AI investments.

Designing visible AI that makes a difference  

Once you’ve done the foundational thinking—strategy, knowledge, processes, governance, and business case —you’re ready to design visible AI that matters. Here is an approach for doing that.  

1. Choose high-visibility, high-impact services 

Identify one or two services that are: 

• Highly visible to the business or customers 
• Experiencing a clear pain point today, such as long wait times, inconsistent responses, frequent escalations, etc. 
• Supported by reasonably good knowledge and defined workflows, or where you’re willing to invest in improving knowledge and workflows 

For these services, define the specific outcome you want to improve. For example: 

• Reduce average time-to-resolution for “Workplace Support” incidents by 30% 
• Improve satisfaction scores for “Employee Onboarding” by 10 points 
• Reduce business-impacting incidents for a customer-facing app by 40% 

Now ask: “Where could visible AI help us achieve these outcomes?” That’s a hugely different question from “where can we turn AI on?” 

2. Define success in terms of outcomes, not AI  

Next, measure success by service performance, not AI utilization. 

AI measures sound like this: 

• Bot deflection rate 
• Number of tickets touched by AI 
• Number of AI recommendations used 

These measures mean nothing to your organization or to your consumers. 

Outcome-based measures sound like this: 

• Time-to-resolution for Service X by channel (self-service, AI-assisted, traditional) 
• Satisfaction scores before and after AI for Service X 
• Reduction in escalations or handoffs for Service X 
• Reduction in business disruption related to Service X 

These measures are not only meaningful to your organization but also to your consumers. 

This is where having clear evaluation criteria matters. Defining evaluation criteria up front—such as alignment with your strategy, the ability of the solution to address issues identified by a SWOT analysis (a simple analysis of your strengths, weaknesses, opportunities, and threats), how the solution tackles the consumer issues that matter most, costs, and how the solution enables future opportunities – enables you to make strategic and outcome-relevant decisions. Apply that same lens to visible AI use cases so you don’t get pulled into high-visibility pilots that don’t support the services and outcomes that matter most. 

AI can and should show up in your metrics—but as a contributor to service performance, not as a standalone technology implementation story. 

3. Make AI’s contribution transparent 

If AI is going to be visible, its contribution to outcomes should be visible as well. That means: 

• Clearly identifying where AI is used in a service journey, so consumers aren’t surprised 
• Providing ways for consumers and support staff to give feedback when AI misses the mark 
• Reporting on how AI-assisted interactions compare to non-AI interactions for key services 
• Using that insight to adjust knowledge, workflows, and AI configurations 

This is where good AI governance and good service management practices intersect. You need clear ownership, clear decision rights, and a commitment to act on what you learn. 

Shift your focus from “AI as a feature” to “AI as a service capability” 

Remember that AI is not a “magic wand.” AI is not some feature you sprinkle on top of ITSM to make it more modern. AI won’t fix deficiencies in how your services are currently delivered.  

AI is a set of capabilities that, when used well, can make your services more effective, more reliable, more consumer-friendly and more intuitive. But that only happens when those capabilities are deliberately aligned with service outcomes and supported by solid foundations in strategy, business case, knowledge, process, and governance. 

Visible AI should be the manifestation of good decisions about services—not a substitute for them. So, before you add another AI tile to your portal or turn on the latest AI module in your ITSM tool, pause and ask: 

• Which service is this helping? 
• Which outcomes will this improve? 
• How will we know? 
• What strategy, business case, knowledge, processes, and governance need to be in place first? 

If you can answer those questions, your AI investments will not only be visible but also valuable because they deliver impactful outcomes.