Managed Service Providers (MSPs) aren’t short on data. Most of them have dashboards, KPIs, and utilization reports running across multiple screens. But having data and using it to make better decisions are two different things, and the gap between them is wider than you might think, with one study finding that only 32% of companies effectively use data to drive business value.
For the other 68%, the numbers exist, they just… don’t do much. They’re data-decorated, but not data-driven.
This article breaks down how MSPs and IT teams can change that, including which metrics matter, how to introduce them without creating anxiety, and how to build the kind of shared data literacy that moves performance forward.
Key takeaways:
- Having dashboards and being data-driven are not the same thing; every metric worth tracking should connect to a decision or a behavior change.
- Utilization, service margin, and client health scores are the three metrics most worth introducing to your broader team, and how you introduce them matters as much as the numbers themselves.
- The altitude gap between what leadership sees in the data and what technicians experience day to day is real, but it’s closeable. Data literacy isn’t built in a single meeting. It’s built through short, consistent exposure, real examples, and a culture where questions are treated as signals of engagement rather than resistance.
Your Guide to Selling Managed Network Services
Get templates for network assessment reports, presentations, pricing & more—designed just for MSPs.
Why are most teams data-decorated rather than data-driven?
Data-decorated teams have all the trappings of a metrics-driven culture: the dashboards, the CSAT scores in the weekly report, and the utilization targets posted in the service room. What they’re missing is the connective tissue between those numbers.
A big part of why comes down to what Amanda Doucette-Lachapelle, Auvik’s MSP Field Strategist, calls the altitude gap. As Amanda puts it:
“Leadership sees numbers as business signals. Technicians see tickets and people. Same reality, different altitude.”
The altitude gap is more about context than it is capability. A technician who spends their day resolving tickets and managing client environments isn’t naturally thinking in terms of margin or retention risk. This isn’t because they don’t care, but because nobody has connected those concepts to the work they do.
Leadership, meanwhile, is pattern-matching across the whole business and making decisions based on signals that never get translated downward. The result is a team where everyone is technically looking at the same data, but nobody is seeing the same picture.
The hidden cost of vanity metrics in MSP environments
Bridging the altitude gap requires looking honestly at which metrics you’re tracking and whether they’re telling you anything useful. For many MSP teams, the dashboard is full of numbers that feel good but don’t drive decisions. These are vanity metrics that don’t actually change how anyone thinks, decides, or acts. These metrics create the appearance of performance without the substance of it.
Three of the most common vanity metrics in MSP environments:
- 100% CSAT from five responses: A perfect score means nothing when the sample is too small to be statistically meaningful. Five happy clients don’t tell you how the other 45 feel… they tell you that five clients responded.
- Tickets closed without a quality check: Closure volume is easy to track and easy to game. A ticket marked resolved isn’t the same as a problem actually fixed, and teams that optimize for close rates often do so at the expense of resolution quality.
- Handle time that rewards speed over resolution: When technicians are measured on how fast they close tickets, the incentive structure works against thoroughness. Speed and quality aren’t always in conflict, but when the metric only captures one of them, you get more of one at the cost of the other.
How to spot vanity metrics and turn them into actionable metrics
The test for any metric is whether it connects to a real decision or behavior. Three questions help draw that line:
- What decision will we make if this number changes? If the answer is “nothing changes,” the metric is decorative. An actionable metric has a clear owner and a clear response. For example, if utilization crosses a threshold, you have a staffing conversation. If ticket aging spikes in a specific account, you investigate before the client calls. If you can’t articulate what you’d do differently based on a number moving up or down, it’s not doing any work for you.
- Who is responsible for influencing it? Metrics without owners don’t move. An actionable metric is assigned, and someone on the team understands that this number is part of what they’re accountable for and has the tools and authority to affect it. Shared accountability across too many people usually means no accountability at all.
- How does it tie back to client experience or operational health? Every metric worth tracking should have a visible line back to either how clients experience your service or how sustainable your operation is. If you can’t draw that line, the metric is likely measuring activity rather than outcome.
| Client Impact | Vanity Metric | Actionable Metric |
| Client satisfaction | 100% CSAT from 5 survey responses | CSAT score paired with response rate across all active clients |
| Resolution quality | Number of tickets closed this week | Percentage of tickets resolved without reopening within 7 days |
| Response speed | Average handle time | First response time paired with resolution rate by issue type |
| Account health | No escalations this month | Ticket volume trend per account over 90 days |
| Team capacity | Utilization percentage | Utilization rate with burnout indicators and PTO correlation |
A quick note on why CSAT alone isn’t enough
Of all the metrics MSP teams over-rely on, CSAT is the most deceptive when it stands alone. A high CSAT score with a low response rate tells you almost nothing because it likely reflects the clients who are already happy and motivated enough to respond, while the dissatisfied ones stay quiet until they churn.
Pairing CSAT with response rate gives you a much more accurate picture. Together, these two data points form one of the most reliable indicators of true client experience available to an MSP team.
How MSPs and leadership teams can work together to improve data literacy, broken down by metrics
The instinct in many organizations is to keep business metrics at the leadership level. Share too much, the thinking goes, and you create anxiety. But the opposite tends to be true.
When technicians have no context for the numbers leadership is watching, every resourcing decision, process change, or strategic shift lands without explanation. Building data literacy across your team gives everyone enough context to understand why things work the way they do, which creates shared understanding and accountability. This is how you create agency and ownership in teams in an MSP.
Utilization rate
What it is: Utilization rate is the percentage of paid staff time that’s going toward billable or client-facing work. It sounds straightforward, but it’s one of those metrics that lands very differently depending on how you introduce it. At the leadership level, it’s a capacity and profitability signal. On the floor, if it’s not framed carefully, it feels more like a productivity tracker, or worse, micromanagement.
When you bring this one to junior technicians, skip the targets. Start with what healthy utilization means for them day to day: fewer last-minute fire drills, PTO that doesn’t come with guilt, and a real justification for hiring before everyone’s already stretched thin. Something like “this number tells us if we have enough people to do the work without burning out” lands a lot better than a percentage and a benchmark.
What to avoid: Framing utilization as a way to account for every unbillable minute. That turns it into a surveillance conversation almost immediately, and once it does, people stop reporting honestly. You’ll have cleaner numbers and a less accurate picture of what’s happening.
Service margin
What it is: Service margin is about whether the work you’re doing on a given account pays for itself (the people, time, tools). Not the whole business, but just that account or that service line. It’s the metric that explains why some clients get more attention from leadership than others, and why certain process changes happen when they do.
You don’t need to walk technicians through the math to make this useful. What you need is cause and effect. “When one account consistently takes twice the effort to support, it limits what we can put into training and tools for everyone” is a lot more meaningful than a margin percentage. It connects a business concept to something people feel at work.
What to avoid: Tying individual performance reviews to account-level margin. People can’t fully control that number, and when they feel like they’re being evaluated on something outside their control, it breeds anxiety rather than engagement. Keep margin as context versus as a scorecard.
Client health score
What it is: A client health score pulls together a handful of signals (ticket volume trends, CSAT patterns, escalation frequency, overdue invoices etc.) into a single view of how an account is doing. The idea is to catch accounts that are quietly heading sideways before it turns into a call you weren’t expecting.
The framing that works best with junior team members is early warning, not judgment. A dropping health score isn’t evidence that someone did something wrong but rather a flag that an account needs attention. “This client’s ticket volume has been climbing and we haven’t heard from them on satisfaction in a while, so let’s check in” is a very different conversation than “this account is at risk.” Same information, very different response.
What to avoid: Turning health scores into a ranking. If the team starts seeing certain accounts as problem clients based on a score, it affects how they approach the work, and rarely in a good way.
How to promote metric literacy without inviting resistance
Introducing business metrics to a team that’s never had visibility into them can be tricky. People bring their own history to these conversations, like past managers who used numbers as a gotcha, performance reviews that felt arbitrary, or a general sense that data sharing is a precursor to something bad. Aim to be deliberate about how you sequence the introduction and what you signal along the way.
1. Start with observation, not ownership
The fastest way to create resistance is to hand someone a metric and tell them they’re responsible for moving it before they understand what it means. Ownership comes after comprehension, not before. Give your team time to notice patterns and ask questions before you attach accountability to anything.
In practice, this might look like spending two or three team meetings simply sharing what the numbers are doing without asking anyone to act on them. Pull up the client health dashboard and walk through what you’re seeing. Point out that one account’s ticket volume has been climbing for six weeks. Don’t assign it yet… just name it and let the team sit with it. Build familiarity before you build accountability.
2. Use real examples over abstract data
A percentage on a slide means almost nothing to someone who hasn’t seen what that number looks like when it changes. Abstract metrics stay abstract until they’re connected to something people have lived through, so concrete stories stick in a way that benchmarks and targets simply don’t.
For example, instead of explaining utilization as a concept, try pointing to a moment the team already remembers:
“Last March, when we were short-staffed and everyone was working weekends, our utilization was sitting at 94% for six straight weeks. That’s what an unsustainable number looks like in real life. Healthy utilization is what gives us the buffer so that doesn’t happen again.”
That single example does more work than any slide explaining what the metric is and why it matters.
3. Invite questions: treat curiosity as a signal, not a challenge
When someone asks “why do we even track this?” in a team meeting, the instinct can be to defend the metric or redirect the conversation. Resist that. Curiosity is almost always a sign of engagement, not pushback. A technician who wants to understand why something is being measured is a technician who’s paying attention, and that’s exactly what you want! The goal is to make questioning feel safe, because the alternative is a team that nods along without buying in.
A good response to “why does our CSAT response rate matter if the scores are already good?” is a conversation. “That’s a fair question. What do you think we might be missing if only a small percentage of clients are responding?” Turning the question back opens a dialogue and often leads to the technician arriving at the answer themselves, which makes it far more likely to stick.
4. Repeat calmly and consistently: short, frequent exposure
One deep dive on business metrics in a quarterly review does nothing for long-term data literacy. People need repeated, low-stakes exposure to numbers before those numbers start to feel familiar enough to think with. Comfort is built up over time through those consistent, brief touchpoints.
This can be as simple as spending five minutes at the start of every weekly team meeting on one metric. Just a quick pulse check. For example: “Ticket aging is up this week, mostly concentrated in two accounts, and here’s what we’re watching.” Over time, the team starts to build a mental map of what normal looks like, which makes it much easier for them to notice and flag when something is off. That’s when data literacy starts doing real work.
Sign up for Auvik today to unlock data-driven decision-making for your MSP team
Building a data-driven MSP team takes a shift in how your whole organization relates to the numbers it already has, and it starts with giving every member of your team enough context to understand what those numbers mean for them.
The tools to support that shift are already there. Auvik’s network performance reporting tools and network traffic analysis software give you the IT metrics and KPIs to track success. And with Auvik AI bringing practical intelligence to IT operations, the path from raw data to real insight is shorter than it’s ever been.
Ready to see what that looks like for your team? Start a free trial or schedule a demo to see Auvik in action.
Try Auvik Network Management
Free to try! Setup takes less than 15 minutes and you will see results in an hour.
Frequently Asked Questions
What does it mean to be a data-driven IT team?
A data-driven IT team doesn’t just track metrics, but uses them to make decisions, change behavior, and improve outcomes at every level of the organization. The difference between a data-driven team and a data-decorated one is whether the numbers influence how people work day to day.
What are the most important KPIs for MSPs to track?
The metrics that matter most in an MSP environment are utilization rate, service margin, client health score, CSAT paired with response rate, and ticket aging. Each one surfaces a different dimension of operational and client health. Utilization tells you about capacity, margin tells you about sustainability, client health tells you about risk, and ticket aging tells you where workload is piling up before it becomes a client experience problem.
What is a vanity metric in IT or MSP?
A vanity metric is one that looks good on a report but doesn’t drive a decision or a behavior change. A common example in MSP environments is a 100% CSAT score drawn from only five survey responses, because it signals satisfaction without providing enough data to be meaningful or actionable.
How do you explain the utilization rate to IT technicians?
Skip the percentages and lead with what healthy utilization means for the people doing the work: fewer fire drills, guilt-free PTO, and a business case for hiring before the team burns out. Framing it as a capacity signal rather than a productivity tracker makes it feel relevant rather than threatening.
What is a client health score in MSP?
A client health score is a composite view of how an account is trending, typically drawing on ticket volume, CSAT patterns, escalation frequency, and invoice status. It’s designed to surface accounts that are quietly heading in the wrong direction before a formal complaint or churn event.
How do MSP leaders build data literacy across their team?
Start with giving your team visibility into metrics before attaching accountability to them. Use real examples from your own environment instead of abstract benchmarks, invite questions openly, and build familiarity through short, consistent exposure in regular team meetings rather than one-off training sessions. Literacy builds gradually, not in a single conversation.
