Service Management Leadership Podcast · 2026-07-30 · 7 min
Key moments - from our scoring
Substance score
19 / 100
Five dimensions, 20 points each
Sticky metrics are a concept borrowed from sports analytics that identifies measurable indicators with historically strong correlations to future outcomes. Jeffrey Tefertiller, drawing on nearly two decades in sports analytics, applies this framework to IT service management and organizational transformation. The core insight is that most organizations fail to recognize which metrics are truly predictive and reliable, instead treating symptoms rather than root causes. Tefertiller provides concrete examples: failed changes predict outages; unaddressed defects correlate with incident volume and longer resolution times; poor CMDB reliability predicts change failures; infrequent patching predicts security incidents. The stickiness refers not to the metrics themselves but to their reliability as forward-looking indicators. For service leaders, IT directors, and transformation teams, understanding sticky metrics means shifting from reactive problem-solving to predictive decision-making. Rather than flooding the service desk after an outage occurs, leaders can prevent the outage by monitoring the leading indicators that precede it. This reframes metrics conversation from scorekeeping to causation and root-cause prevention.
Sticky metrics are leading indicators with historically strong correlations to future outcomes, showing what will predictably happen if something occurs - like failed changes predicting outages or unaddressed defects predicting incident volume.
Regular metrics often measure outcomes or symptoms; sticky metrics predict what will happen next, making them more valuable for preventive decision-making rather than reactive scorekeeping.
An unpredictable or unreliable CMDB is a sticky metric that predicts higher rates of failed changes, because poor data quality undermines change planning and execution.
Most organizations don't consciously think about which metrics are predictable leading indicators versus which are just symptoms; they lack the analytical discipline to identify and act on stickiness.
Our reviewer’s read on each dimension, with quotes from the episode.
The episode is a short solo monologue that introduces a plausible framing (sticky metrics as leading indicators in IT) but only offers surface-level, obvious correlations any IT practitioner already knows. There is significant throat-clearing and padding relative to the thin payload of ideas.
If we have a failed change to a big system, we're probably going to have an outage
you have higher rates of incidents when unaddressed defects are allowed to go live
Borrowing the 'sticky metrics' label from sports analytics as a framing device for IT leading indicators is a mildly fresh angle, but every actual example offered is textbook common sense rather than a counterintuitive or first-principles argument.
In the sports analytics world there is a something called sticky metrics
the stickiness just refers to the strong correlation and predictability
This is a solo host monologue with no guest; the host claims roughly 20 years in sports analytics and service management but the content itself does not demonstrate deep practitioner expertise or seniority - it stays at a high, conceptual level throughout.
I have been a, uh, part of the sports analytics world for a lot of years. Coming up on year 20 this fall
This is Jeffrey Tiefertiller. Thank you for being a part of what we're doing
There are zero named companies, zero real data points, zero metrics with actual numbers, and zero concrete case studies - every example is a generic hypothetical stated in probabilistic language, making it impossible to verify or learn from empirically.
service desk phones are going to get lit up Tom, because there's an outage
you're going to have higher rates of uh, failed changes if you have an unpredictable, unreliable cmdb
The episode is a solo monologue with no interviewer, no questions, no follow-ups, and no pushback possible; the structure wanders from a sports analogy introduction through a loose list of examples to a generic sign-off with no sharpening of any idea.
We, uh, put out a lot of content just to try to be of value to those that are trying to increase how they think about these topics
How are you going to respond? How are you going to change the ways that you do work?
Computed from the transcript - who did the talking, and the words that came up most.
In this episode, Jeffrey discusses sticky metrics Email Jeffrey with any questions or feedback (jtefertiller@servicemanagement.us) Each week, Jeffrey will be sharing his knowledge on Service Delivery (Mondays) and Service Management (Thursdays). Jeffrey is the founder of Service Management Leadership, an IT consulting firm specializing in Service Management, Asset Management, CIO Advisory, and Business Continuity services. The firm's website is Jeffrey has been in the industry for 30 years and brings a practical perspective to the discussions. He is an accomplished author with seven acclaimed books in the subject area and a popular YouTube channel with approximately 1,800 videos on various topics. Also, please follow the Service Management Leadership LinkedIn page.
Transcribed and scored by The B2B Podcast Index.
Speaker A: M. Foreign. Welcome to the Service Management Leadership Podcast with Jeffrey Tefertiller. Welcome to the Service Management Leadership Podcast. My name is Jeffrey Tfertiler and I have a great topic for you. I have been a, uh, part of the sports analytics world for a lot of years. Coming up on year 20 this fall. And in the sports analytics world there is a something called sticky metrics and there's this big desire to identify sticky metrics and what Sticky metrics seems like an odd name, but it's ones with historically strong correlation as leading indicators. We have these in our own lives that we just gloss over. If it thunders outside, it's probably going to rain, right? Think about that. In every part of our business world, our service management world, our transformation world, there are sticky metrics that have strong correlation as leading indicators, meaning we can predict that if something happens, something else will happen. In the stickiness just refers to the strong correlation and predictability. So this means that we are able to make educated decisions based upon the predictability of these metrics. Some sports are easier to identify metrics than others. I think of um, watching the World cup, maybe time of possession, shots on goal. There are metrics that predict outcomes much better than others. But a lot of times sports struggle with analytics because maybe there's not a big enough data sample size, maybe the predictability is difficult for one reason or another. But the stickiness metrics has made me think about our IT metrics. Right. Of course, I always think about it in our work terms. Which of our metrics have large enough sample sizes that are still very highly correlated leading predictable indicators. There are some, if we stop and think about it. Let me start by saying that this observation that most organizations don't think like this, so they really don't think what's sticky and what's not, what's predictable and what's not. But let me give you one. If we have a failed change to a big system, we're probably going to have an outage. Right? That makes sense. But let's start with some really deep ones. Positive user experience is the outcome we get oftentimes very predictable. When there is great self service, you have great self service. It's predictable that you will have great user experience. Another one, you have, uh, higher rates of incidents when unaddressed defects are allowed to go live. That's very sticky. Right? You have defects that go live. M. We're probably going to have incidents that we don't know how to resolve quickly. Here's another one. Service desk volume metrics. After A failed change. Yep. The service desk phones are going to get lit up Tom, because there's an outage and people are just struggling to be able to do their work. And here's the last one. You're going to have higher rates of uh, failed changes if you have an unpredictable, unreliable cmdb. If we know that these sticky metrics are true and you can think of the ones in security. Right. If you don't patch frequently and often you're, you're pretty likely to have a security, uh, incident or situation. You can adapt these to whichever ever, whichever part of an organization you reside. But if you grant me this thought process that these are true, how do you respond? How will you now say it? I, uh, know that if this happens, then that happens. How are you going to respond? How are you going to change the ways that you do work? Because many times we try to resolve the symptom when really the sticky metric is showing us the down deep rooted problem. This is Jeffrey Tiefertiller. Thank you for being a part of what we're doing. Thank you for supporting service management leadership. Let me know how either I or service management leadership can help your organization. We, uh, put out a lot of content just to try to be of value to those that are trying to increase how they think about these topics. So thank you for your support. Hope you have an awesome rest of your day and bye.
Other episodes covering the same guests and topics, from across The B2B Podcast Index.