Informa helps businesses and professionals in hundreds of ways.

Our international portfolio of live events, world-leading research publications, and innovative digital services provide specialists with the knowledge and connections they need to thrive.

HDI Service & Support World
April 25-29, 2027
Caesars PalaceLas Vegas, NV
How to Turn Service Metrics into Meaningful Accountability

Early in my career as a delivery operations manager, I sat in an operational review, staring at a dashboard that was a sea of solid green. Our SLA response times were in 90s, average handle times were down, and ticket queues were moving exactly on schedule.

Yet, when I spoke to our client’s leadership team, the sentiment didn't match the data. They were frustrated. Their users felt rushed, complex issues were being bounced between teams to avoid SLA breaches and the business was feeling the friction.

That was my wake-up call. We were winning the battle of the stopwatch, but we were losing the war of user experience. We had fallen into a classic trap: managing activities rather than outcomes.


Activity Metrics vs. Outcome Metrics

Service desks are drowning in data, but not all data is created equal. To build a high-performing support culture, we must understand the difference between movement and value.

  • Activity Metrics (The Movement): These are measures like ticket volume, average handle time, SLA response times and backlog size. They tell you how fast and how much work is being done.
  • Outcome Metrics (The Value): These are measures like First Contact Resolution (FCR), Mean Time to Resolution (MTTR) and deflection rates. They tell you the impact of the work on the user and the business.

When we focus too heavily on activity, we accidentally encourage our teams to game the system — rushing users off the phone or passing tickets along just to stop their personal timers. Outcome-driven leadership shifts the conversation from, "How many tickets did we close today?" to "Did we resolve the user's issue effectively?"


Leading with Data

If your team dreads metric reviews, it’s usually because data is being used as a weapon rather than a tool. When frontline analysts feel judged solely by a ticking clock, they hide problems and take shortcuts.

In my operations roles, I learned to establish a golden rule: Metrics are used to ask better questions, not to assign blame. Instead of pulling an analyst into an office to ask why their average handle time spiked on a Tuesday, look at the trend together.

  • Is a new software update causing more complex, time-consuming issues?
  • Is there a gap in our knowledge base?
  • Does the team lack the proper administrative access to resolve the issue on the first call?

When your team realizes that data is used to advocate for better tools, clearer documentation and targeted coaching, they stop fearing the dashboard. They start owning it.


The Outcome-Based Review Framework

To help your team transition from simply reporting history to actively driving improvement, try structuring your next operational review around these six questions:

What Happened? (Facts): State the raw data objectively.

Example: "Our First Contact Resolution (FCR) rate dropped by 8% this month."

Why Did It Happen? (Analysis): Dig into the root cause. Do not settle for "we were busy."

Example: "A spike in complex remote-work connectivity issues required escalations to the network team."

What is the Business Impact? (Context): Translate the metric into real-world consequences.

Example: "Remote employees experienced an average of four hours of downtime while waiting for ticket handoffs."

What Do We Own? (Accountability): Identify what is within your team's control to fix.

Example: "We own the initial triage, but we currently lack the diagnostic tools to resolve these network issues at Tier 1."

What Will We Do Next? (Action): Define a concrete, time-bound action plan.

Example: "We will partner with the network team next week to build a diagnostic checklist and secure limited troubleshooting access for our service desk analysts."

How Will We Confirm Improvement? (Measurement): Determine the success criteria.

Example: "We expect to see FCR for connectivity tickets rise by 15% over the next 30 days."

Related news

Bridging the Gap: 5 Tips for Cross-Functional Collaboration That Enables AI Transformation

Ask ten executives who owns AI at their company, and you’ll get ten different answers. IT says it’s not their call. Legal gets blamed for slowing everything down. HR figures it’s someone else’s department. Meanwhile, teams are buying tools nobody signed off on, duplicating work and hoping it all sorts itself out. Sound familiar?

Lisa Duerre spent the last year studying why that happens. As part of an applied research project for her leadership consulting collective, RLD Group, she studied where AI adoption breaks down inside organizations, and where it works. The findings from RLD Group’s research helped inform a collaboration on the CONVERSATIONS WORTH HAVING®: The Human Accelerator for Artificial Intelligence Quick Start Guide, which is available as a digital download.

Duerre views organizations through what she calls an I–WE–US leadership framework, defined like this:

  • I: individual judgment and accountability

  • WE: workflows and cross-functional coordination

  • US: governance, decision rights and organizational measures

“All three levels are contributing to the breakdown or the alignment, whether people realize it or not,” Duerre says. “AI is amplifying whatever’s already true in your system. The teams that were disconnected before AI showed up are more disconnected now. The ones that talked to each other are moving faster, together.”

If your company is ready to collaborate better with AI tools, Duerre shared the following tips. Take a look.

Form a cross-functional AI committee

Duerre’s background is in HR, and she says most HR leaders assume AI ownership belongs to IT. It doesn’t, at least not exclusively.

“Ownership needs to sit at the system level,” Duerre says. “Each function carries a piece of it, based on what they do, how well they understand that part of the business and how their work depends on everyone else’s. AI is flattening how we work. You can’t just keep it in your own business unit anymore. You have to look all around you.”

For starters, she suggests building a cross-functional AI committee instead of having one department make all the AI decisions. Legal, IT, cybersecurity and HR should be on the committee, Duerre says.

“If you have a C in front of your title, you should be on that committee,” Duerre says. “That’s how I look at it, because it’s a system-level solution.”

During these meetings, Duerre says you’ll find out that some departments are racing ahead with AI and others are holding back.

“Both sides need to name the trade-offs aloud,” Duerre says. “With teams moving too cautiously, you have to talk about the opportunity cost of falling behind. With teams sprinting ahead, you have to ask them what happens if they don’t bring everyone else along with them.”

Figure out how to use AI strategically

Most companies spent the past two years telling employees to use AI with anything, without much strategy behind it. Duerre says that’s starting to catch up with organizations as finance teams scrutinize the cost.

Her rule of thumb: if you can’t articulate the goal and how you’ll measure success, don’t roll it out yet.

“Teams that use AI well have a strategy behind it,” Duerre says. “They’ve kicked the tires on what they’re trying to solve it for. You need to ask yourself, ‘Which business outcome are we trying to improve, and what must be aligned for AI to create measurable value?’”

Here are a few examples of how to use AI strategically:

  • A company could select a workflow that regularly creates delays, redesign it with AI and test the new approach. Then, measure whether it improves time, cost, quality or capacity.

  • Use AI to support early sales outreach and qualification across markets and languages. AI can help a business reach and assess more potential opportunities, while people remain responsible for understanding the customer and building trust.

  • Flag patterns in customer complaints across multiple channels with AI, so leadership can see recurring problems before it shows up in satisfaction scores.

Check-in regularly during an AI rollout

Duerre recommends a minimum weekly check-in during any AI rollout, sometimes daily depending on complexity. But the format matters more than the frequency. Status updates don’t cut it.

“Ask, ‘What are we learning and what are we surprised by?’ That’s a question that helps you with your check-ins, versus, ‘It’s in three products now and we’ve tested six,’” Duerre says. “That doesn't help, because you’re having these meetings to figure out what’s working and why. If you ask more strategic questions, you can move even faster.”

Publish AI guardrails

Employees who don’t know what’s allowed with AI will either freeze or go around the system entirely, Duerre says. She recommends publishing clear, specific guardrails on what’s okay and what’s not. Come up with some real examples, and pair them with an intake process that doesn’t require writing a thesis to get an approval for using it.

"The approval path should be lightweight, not bureaucratic,” Duerre says. “Something like, ‘If you’re going to use AI, here’s the path. And if it needs approval, here’s three or four quick questions for you to answer.’”

Take employee anxiety about AI seriously

“AI is just a tool” is a phrase Duerre hears at nearly every conference she attends, but she doesn’t buy it.

“Saying it’s a tool is underselling what’s happening at companies right now,” Duerre says. “AI is changing how we work. It’s changing how we lead teams.”

Duerre wants leaders to remember that a lot of employees are fearful of AI. Pew Research Center found 52% of U.S. workers are worried about the future impact of AI in the workplace.

Employees who feel AI is being “done to them,” instead of built alongside them are especially anxious, she says.

“Leaders need to recognize that anxiety is contagious,” Duerre says. “As a leader, this is your opportunity to show up as the safe, steady person who is showing what you’re learning with AI. And don’t be afraid to show how you’ve failed using AI, too.”

Duerre asks every executive she works with: “Who am I with AI?” and encourages them to pass this mindset question along to their employees, too.

“AI is now your teammate,” Duerre says. “Phrasing it as, ‘who am I with AI?’ is different than, ‘what’s going to happen to me with AI?’ You really want your team to feel empowered with AI and show them how it can help accelerate their career.”

Put these ideas into action

Rewiring your organization for AI requires more than the right tools. It takes shared language, practical frameworks, and a willingness to keep learning. Here are a few resources to help you take the next step.

  • Enterprise AI Playbook: Practical frameworks and executive discussion questions to help IT, HR, and business leaders align around AI that delivers measurable value.

  • Work-First AI Use Case Assessment: Identify the workflows where AI can have the greatest impact before you invest in new tools.

  • The REWIRED Brief: Get weekly insights, real-world case studies, and practical advice on leading AI transformation.

4 Ways to Get Your Team Ready For Their Future Career

The World Economic Forum states that 39% of the skills your team relies on today will change by 2030. Most organizations have not built a plan to prepare their teams for that shift. At my company, we are still debating how to manage this upcoming shift.