{"id":528647,"date":"2024-09-12T15:00:00","date_gmt":"2024-09-12T17:30:51","guid":{"rendered":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/"},"modified":"2026-01-29T14:51:45","modified_gmt":"2026-01-29T19:51:45","slug":"39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way","status":"publish","type":"post","link":"https:\/\/xentegra.com\/fr\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/","title":{"rendered":"39: Syncing with ServiceNow: How to reduce MTTR by helping people get out of their own way"},"content":{"rendered":"<p><iframe loading=\"lazy\" style=\"width: 100%; height: 200px;\" src=\"https:\/\/www.buzzsprout.com\/1759550\/episodes\/15741715-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way?iframe=true\" width=\"100%\" height=\"200\" frameborder=\"0\" scrolling=\"no\"><\/iframe><\/p>\n<p>IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant. Year after year, <a href=\"https:\/\/www.servicenow.com\/lpayr\/ema-real-world-incident-response-management-prevention.html\">Enterprise Management Associates (EMA) research<\/a> consistently ranks reducing the frequency, duration, and impact of incidents and outages as the top operational objective for IT. That goal holds true for organizations of all sizes across industries globally.<\/p>\n<p>The best-case scenario is to predict and prevent outages before they happen. When directly asked, \u201cIf you could choose one thing to do really well, what would have the biggest positive impact?\u201d 43% of IT leaders chose \u201cproactive response to incidents before they impact users,\u201d according to a global EMA survey.<\/p>\n<p>The next best scenario is to significantly <a href=\"https:\/\/hub.servicenow.com\/wcc\/eh\/1237365\/lp\/4264703\/reducing_mttr_and_accelerating_the_move_to_cloudnative\/?partnerref=on24seo\">reduce MTTR<\/a>,1 regardless of whether the \u201cR\u201d stands for \u201crepair,\u201d \u201crespond,\u201d \u201crestore,\u201d or \u201crevive.\u201d That effort begins with identifying and attacking the most significant influencers on time, the first \u201cT\u201d in MTTR.<\/p>\n<p>Animateur : Andy Whiteside<br \/>\nCo-host: Mike Sabia<br \/>\nCo-host: Eddie McDonald<br \/>\nCo-animateur : Fred Reynolds<\/p>\n<div class=\"transcript\">\n<p><!--block-->WEBVTT<\/p>\n<p>1<br \/>\n00:00:02.330 &#8211;&gt; 00:00:18.219<br \/>\nAndy Whiteside: Hello! And welcome to Episode 39 of syncing with service. Now I&#8217;m your host, Andy Whiteside. I&#8217;m happy to be back missed a couple of weeks. I think we missed a couple of weeks. There might have been a holiday or 2 in there somewhere along the way. I appreciate you guys covering, covering this while I was going. Let me let me do the commercial, real quick<\/p>\n<p>2<br \/>\n00:00:18.740 &#8211;&gt; 00:00:30.480<br \/>\nAndy Whiteside: government. We&#8217;re a service now, partner, because the world needs better and more service now, partners, and if you&#8217;re a service now, user, if you&#8217;re a service now, if your organization has service now.<\/p>\n<p>3<br \/>\n00:00:30.550 &#8211;&gt; 00:00:37.480<br \/>\nAndy Whiteside: there&#8217;s a chance that we can help you a ton, because there&#8217;s always room for improvement, and the way we come about it, the way we come at it<\/p>\n<p>4<br \/>\n00:00:37.570 &#8211;&gt; 00:00:51.809<br \/>\nAndy Whiteside: gives us the opportunity to be successful with you. Long term. Yes, we are a business, but we we don&#8217;t have to. We don&#8217;t have to maximize profitability at your expense in order to to be a a business. And that&#8217;s kind of how we see the world.<\/p>\n<p>5<br \/>\n00:00:52.250 &#8211;&gt; 00:00:56.270<br \/>\nAndy Whiteside: I&#8217;ve got my experts on Fred Reynolds, who runs the practice.<\/p>\n<p>6<br \/>\n00:00:56.340 &#8211;&gt; 00:00:59.699<br \/>\nAndy Whiteside: Fred, how is it going in service now&#8217;s integral world.<\/p>\n<p>7<br \/>\n00:00:59.700 &#8211;&gt; 00:01:27.130<br \/>\nFred Reynolds: It is going wonderful. Got a lot of lot of customers. We&#8217;re starting to work with a lot of customers that we&#8217;ve done work for that. Keep coming back and looking for more. So loving the fact that we&#8217;re consulting a lot. You know, I&#8217;d say part of this is obviously out there trying to to to make our brand known. But the customers we&#8217;re working with are certainly realizing the type of work and the quality. We do. So. I&#8217;m loving to see the repeat questions and and consulting questions that that lead us to have that lifelong<\/p>\n<p>8<br \/>\n00:01:27.450 &#8211;&gt; 00:01:28.460<br \/>\nFred Reynolds: customer.<\/p>\n<p>9<br \/>\n00:01:28.460 &#8211;&gt; 00:01:35.670<br \/>\nAndy Whiteside: Client for life. I&#8217;m gonna ask you a question. Give me the honest answer. I don&#8217;t know. I didn&#8217;t stage it customer retention rate for your group is what.<\/p>\n<p>10<br \/>\n00:01:36.680 &#8211;&gt; 00:01:38.230<br \/>\nFred Reynolds: 100%. So far.<\/p>\n<p>11<br \/>\n00:01:38.440 &#8211;&gt; 00:01:38.950<br \/>\nEddie McDonald: Yeah.<\/p>\n<p>12<br \/>\n00:01:38.950 &#8211;&gt; 00:01:40.209<br \/>\nAndy Whiteside: Is it really 100%? Yeah.<\/p>\n<p>13<br \/>\n00:01:40.210 &#8211;&gt; 00:01:43.829<br \/>\nFred Reynolds: I haven&#8217;t had any customers that said they didn&#8217;t like us and wanted to leave us. That&#8217;s for sure.<\/p>\n<p>14<br \/>\n00:01:43.830 &#8211;&gt; 00:01:49.036<br \/>\nAndy Whiteside: Yeah, I&#8217;ll I&#8217;ll tell you. I I got a I got a text from a former employee last week that said<\/p>\n<p>15<br \/>\n00:01:50.200 &#8211;&gt; 00:02:03.600<br \/>\nAndy Whiteside: you know he he left on good good terms, good enough terms, but he was on a golf course somewhere, and he heard somebody talking about his integra and how much the customer loved working with us, so he thought he&#8217;d give me a text and tell me that was that was pretty nice. And honestly, I needed that on Friday, after all other stuff going on.<\/p>\n<p>16<br \/>\n00:02:03.600 &#8211;&gt; 00:02:04.660<br \/>\nFred Reynolds: Absolutely.<\/p>\n<p>17<br \/>\n00:02:05.140 &#8211;&gt; 00:02:07.540<br \/>\nAndy Whiteside: Eddie Mcdonald, how are you?<\/p>\n<p>18<br \/>\n00:02:07.700 &#8211;&gt; 00:02:13.900<br \/>\nEddie McDonald: I&#8217;m good, Buddy, I&#8217;m I&#8217;m thinner, richer, and better looking than I was yesterday, so it&#8217;s a good day.<\/p>\n<p>19<br \/>\n00:02:14.750 &#8211;&gt; 00:02:16.380<br \/>\nAndy Whiteside: Are any of those things actually true?<\/p>\n<p>20<br \/>\n00:02:16.380 &#8211;&gt; 00:02:19.108<br \/>\nEddie McDonald: Yeah, every one of them is true.<\/p>\n<p>21<br \/>\n00:02:19.696 &#8211;&gt; 00:02:21.910<br \/>\nAndy Whiteside: Alright. Well, Eddie&#8217;s a liar, Mike, how are you.<\/p>\n<p>22<br \/>\n00:02:23.080 &#8211;&gt; 00:02:25.421<br \/>\nMike Sabia: I am doing well. I<\/p>\n<p>23<br \/>\n00:02:26.130 &#8211;&gt; 00:02:34.819<br \/>\nMike Sabia: My wife moved out of the office to another space in the house, so I spent the the weekend, doing a new mesh networking with my thousands of IoT devices, switching them over<\/p>\n<p>24<br \/>\n00:02:35.190 &#8211;&gt; 00:02:36.360<br \/>\nMike Sabia: now. So, feeling productive.<\/p>\n<p>25<br \/>\n00:02:36.360 &#8211;&gt; 00:02:40.299<br \/>\nAndy Whiteside: Yours? Was that her choice? Did she move out, or yours.<\/p>\n<p>26<br \/>\n00:02:40.758 &#8211;&gt; 00:02:44.929<br \/>\nMike Sabia: I think she initiated it, but I think it was a good move, you know.<\/p>\n<p>27<br \/>\n00:02:44.930 &#8211;&gt; 00:02:58.360<br \/>\nFred Reynolds: I love that conversation. Mike had told me that earlier today. So I spent his weekend. And I&#8217;m like, you know, that&#8217;s never been a problem, because there&#8217;s no way my wife would work in the same room as me, because I talk all day. I&#8217;m loud, I get excited. I pace, and I walk through the house already.<\/p>\n<p>28<br \/>\n00:02:58.730 &#8211;&gt; 00:03:02.600<br \/>\nMike Sabia: That was my wife&#8217;s biggest complaint. You talk all day long, is what she said.<\/p>\n<p>29<br \/>\n00:03:03.280 &#8211;&gt; 00:03:04.240<br \/>\nFred Reynolds: Consultants.<\/p>\n<p>30<br \/>\n00:03:04.240 &#8211;&gt; 00:03:13.499<br \/>\nEddie McDonald: Lee Lee and I, my wife and I had next door offices, and it wouldn&#8217;t work. We had to go on the opposite ends of the house, we could still hear each other. So yeah, I get it.<\/p>\n<p>31<br \/>\n00:03:13.670 &#8211;&gt; 00:03:15.779<br \/>\nFred Reynolds: Well, Andy goes to another, States.<\/p>\n<p>32<br \/>\n00:03:17.863 &#8211;&gt; 00:03:25.699<br \/>\nAndy Whiteside: my wife was supposed to ride with me tomorrow to Raleigh to go see our kids who are in school there, and she said, Are you gonna be on calls all the time on the way up there? And I said, yes, she said, well, I think I won&#8217;t go.<\/p>\n<p>33<br \/>\n00:03:25.920 &#8211;&gt; 00:03:26.470<br \/>\nAndy Whiteside: Oh.<\/p>\n<p>34<br \/>\n00:03:29.289 &#8211;&gt; 00:03:33.839<br \/>\nAndy Whiteside: well, guys Mike, I cut you off to make fun of you. But glad to have you.<\/p>\n<p>35<br \/>\n00:03:33.840 &#8211;&gt; 00:03:35.019<br \/>\nMike Sabia: No, no, it&#8217;s all good.<\/p>\n<p>36<br \/>\n00:03:35.500 &#8211;&gt; 00:03:36.520<br \/>\nMike Sabia: I don&#8217;t know.<\/p>\n<p>37<br \/>\n00:03:36.520 &#8211;&gt; 00:03:42.909<br \/>\nAndy Whiteside: And I&#8217;m curious about your mesh network and how you do it. And I&#8217;m even more curious around your IoT comment. But that&#8217;ll have to be for a different time.<\/p>\n<p>38<br \/>\n00:03:44.676 &#8211;&gt; 00:04:00.070<br \/>\nAndy Whiteside: So, guys, you brought a blog here from August 29th of 2024, I you know. Funny. I I read that date, and I said, Well, that&#8217;s last year. I think that&#8217;s in the future like Oh, crap! It&#8217;s already September. I literally have forgotten, and it&#8217;s from Valerie O&#8217;connell.<\/p>\n<p>39<br \/>\n00:04:00.280 &#8211;&gt; 00:04:19.540<br \/>\nAndy Whiteside: So thank you, Valerie, for writing this and the the title is how to reduce M. Ttr. By helping people get out of their own way I had to go look up what Mttr. Is. I know you guys knew, and it&#8217;s mean time to resolution. That&#8217;s paramount. If you&#8217;re working a<\/p>\n<p>40<br \/>\n00:04:19.750 &#8211;&gt; 00:04:33.510<br \/>\nAndy Whiteside: customer call center a help desk. You name it. I think that matters whether it&#8217;s me complaining about my new, you know, my new top or my bronco being too windy, or you know somebody complaining they can&#8217;t log in, or their logins are slow. Mike, why did you pick this one.<\/p>\n<p>41<br \/>\n00:04:34.390 &#8211;&gt; 00:04:44.690<br \/>\nMike Sabia: I thought it was pretty apropos, and also it was recent. We always look to have blogs that are that are recently published so that we can speak to topics that may people may be interested in.<\/p>\n<p>42<br \/>\n00:04:45.155 &#8211;&gt; 00:04:47.230<br \/>\nMike Sabia: You know. Mtdr. Of course.<\/p>\n<p>43<br \/>\n00:04:47.550 &#8211;&gt; 00:05:10.440<br \/>\nMike Sabia: refers to mean time to resolve or repair, but it also has some other definitions depending on how you want to use it. Mean time to respond service. Now&#8217;s 2 principal sla&#8217;s are regarding response and resolution response would be the 1st person to assign to it, and the resolution is the the resolution of the issue. Sometimes those are both exposed to customers, sometimes only one and the other is just used internally.<\/p>\n<p>44<br \/>\n00:05:10.720 &#8211;&gt; 00:05:14.480<br \/>\nMike Sabia: but very apropos and and pertinent topics.<\/p>\n<p>45<br \/>\n00:05:14.710 &#8211;&gt; 00:05:23.770<br \/>\nAndy Whiteside: Fred, does this acronym apply to just the Csm portion itsm. But Csm portion of service now, or just kind of apply to all things service.<\/p>\n<p>46<br \/>\n00:05:23.770 &#8211;&gt; 00:05:45.800<br \/>\nFred Reynolds: I think it applies to everything. I mean, you could put a spin on it right, because everything that has a case or an incident or a anything can have a defined response, so it might kind of let on your sla is how you build those. So it&#8217;s really how you define a service you want to provide, and then how you&#8217;re going to respond to those. And this gets look, Mike proposed this blog today. But we kind of got excited before this got started, because<\/p>\n<p>47<br \/>\n00:05:45.800 &#8211;&gt; 00:06:03.750<br \/>\nFred Reynolds: to me we, as we go through this, I want you to keep in mind that these conversations around. Meantime the response or and and the definition around this like this has been conversations I&#8217;ve been having for 20 plus years, and probably 20 plus years before me. This is still a problem for any customer of any size today.<\/p>\n<p>48<br \/>\n00:06:03.750 &#8211;&gt; 00:06:16.729<br \/>\nFred Reynolds: I mean, it&#8217;s interested in this much time that people still don&#8217;t have a lot of this stuff handled. People still need help with this, and that&#8217;s the whole purpose of like a platform like service. Now to help with this, so I won&#8217;t go too deep, but I just find it a very applicable I&#8217;m I&#8217;m<\/p>\n<p>49<br \/>\n00:06:17.120 &#8211;&gt; 00:06:23.679<br \/>\nFred Reynolds: happy, and this is one of those blogs like I&#8217;m happy to talk to because I lived it for so long. I&#8217;m trying to get better around this place. Pace.<\/p>\n<p>50<br \/>\n00:06:24.300 &#8211;&gt; 00:06:38.426<br \/>\nAndy Whiteside: So so this is the one Mike brought. He normally does. But, Eddie, I&#8217;m gonna come to you 1st with the the low tech side of Mtr. I think. You would probably be the best person to explain how you explain that to people from a business level as well as just from<\/p>\n<p>51<br \/>\n00:06:38.970 &#8211;&gt; 00:06:42.479<br \/>\nAndy Whiteside: you know, from from yeah. I guess from a business level, how.<\/p>\n<p>52<br \/>\n00:06:42.480 &#8211;&gt; 00:06:46.650<br \/>\nEddie McDonald: I love it that you say the low tech one is good for me. So thanks for that.<\/p>\n<p>53<br \/>\n00:06:48.010 &#8211;&gt; 00:06:53.120<br \/>\nAndy Whiteside: Just because your present company is Mike and Fred. I&#8217;ll I&#8217;ll I&#8217;ll let. I&#8217;ll tease this one up for you. But I think you&#8217;re knocking out.<\/p>\n<p>54<br \/>\n00:06:53.120 &#8211;&gt; 00:07:14.729<br \/>\nEddie McDonald: Sure. Well, you know. So let&#8217;s take a step back. Let&#8217;s talk about what is Mttr. So we have an issue. And how long does it take to resolve that issue? So if we&#8217;re talking about service now at its core, it is a productivity engine, that&#8217;s what it&#8217;s there for is to get people to work more efficiently. Visibility work in one place, and<\/p>\n<p>55<br \/>\n00:07:14.790 &#8211;&gt; 00:07:16.330<br \/>\nEddie McDonald: too often.<\/p>\n<p>56<br \/>\n00:07:16.370 &#8211;&gt; 00:07:30.580<br \/>\nEddie McDonald: you know, if we take a person&#8217;s hourly salary, and there&#8217;s there&#8217;s numbers here we&#8217;ll talk about. If it takes a half an hour to Mtr. An issue, then that&#8217;s a half an hour times X, amount of people that are lost productivity.<\/p>\n<p>57<br \/>\n00:07:30.580 &#8211;&gt; 00:07:55.080<br \/>\nEddie McDonald: And it&#8217;s in. Fred just said it. It&#8217;s a significant issue. It&#8217;s been a significant issue since it has been around. When stuff breaks, people stop working, and and they get distracted, because now they have to go fix that thing, it&#8217;s all real dollars that are being lost. So the low tech side of it is, people aren&#8217;t working. When stuff is broken. We need to get visibility early.<\/p>\n<p>58<br \/>\n00:07:55.080 &#8211;&gt; 00:08:15.590<br \/>\nEddie McDonald: We need to get fixes that are automated and get the people out of the fix as well. But when you&#8217;re talking low tech, it&#8217;s literally people on phones saying something is broken, and other people on the other end of those phones talking to other people trying to fix it. It&#8217;s very low tech in most environments today.<\/p>\n<p>59<br \/>\n00:08:17.080 &#8211;&gt; 00:08:33.170<br \/>\nAndy Whiteside: Hey? And I want you to walk through these. I I wanna stage this for you, though real quick and I want Mike to respond, and Fred over the top. But like, I think, a lot of times, it&#8217;s the person on the other end of the equation. If it&#8217;s not urgent like, if they&#8217;re not down, if they&#8217;re not totally broken, I think they slow down<\/p>\n<p>60<br \/>\n00:08:33.169 &#8211;&gt; 00:08:56.060<br \/>\nAndy Whiteside: the process. But before we do that Mike Mike saved us a while ago, and I was too done to look. They had a note, a footnote, and they actually defined it for the sake of this article, the way the author meant it, and I think Mike said it. But I&#8217;m just Gonna repeat it. Mttr is a commonly used abbreviation in it. Services and operations that stands for mean time to repair, meantime to response, meantime to respond, and meantime to resolution.<\/p>\n<p>61<br \/>\n00:08:56.434 &#8211;&gt; 00:09:01.549<br \/>\nAndy Whiteside: I I guess it depends on your frame of reference as to which one you mean by Mtr.<\/p>\n<p>62<br \/>\n00:09:03.000 &#8211;&gt; 00:09:17.330<br \/>\nEddie McDonald: I think generally it&#8217;s it&#8217;s resolution is is, how long does it take to fix it? Now? Now, I guess there are elements where responding is is for like a help desk. What is nttr, if there&#8217;s a certain issue that pops up.<\/p>\n<p>63<br \/>\n00:09:17.330 &#8211;&gt; 00:09:39.340<br \/>\nFred Reynolds: So so truly, I think that&#8217;s what it&#8217;s meant meantime to restore right to to res to resolve the issue. But all those steps in there which is so neat about this article, because we do need to go through these. What it&#8217;s calling out here to percentages of why, that&#8217;s what this is trying to say is, where are they today? Still, today in this this journey, and one of the biggest problems are still trying to solve. So I&#8217;ll stop there. But I think these percentages really need to go over.<\/p>\n<p>64<br \/>\n00:09:39.340 &#8211;&gt; 00:09:54.690<br \/>\nAndy Whiteside: Mike, why don&#8217;t you walk us through the graph as well as the numbers down below? And and when you find the one that applies to say me when it&#8217;s not urgent. Aka Andy, cause I&#8217;m you know I don&#8217;t respond to the for 3 days when somebody sends me something highlight where that one fit. But go ahead.<\/p>\n<p>65<br \/>\n00:09:55.020 &#8211;&gt; 00:10:05.909<br \/>\nMike Sabia: So I mean, per this chart with the 5 orange percentages detection identification logging, you know, identifying what the issue is and and what this one<\/p>\n<p>66<br \/>\n00:10:06.240 &#8211;&gt; 00:10:21.379<br \/>\nMike Sabia: concept this article does not talk about is deflection, you know. If a person could, you know, go to your your website, say, I want to report an issue, and and they&#8217;re able to resolve themselves. That&#8217;s deflection. And it&#8217;s not going to be Mtr. Mtrs. Once the ticket is opened.<\/p>\n<p>67<br \/>\n00:10:22.013 &#8211;&gt; 00:10:34.020<br \/>\nMike Sabia: But this 1st item of detection. Identification logging does touch a little bit. And and I think it&#8217;s mentioned elsewhere in the article about proactive customer support, you know, identifying issues before the customer<\/p>\n<p>68<br \/>\n00:10:34.070 &#8211;&gt; 00:10:45.380<br \/>\nMike Sabia: notices. It&#8217;s an issue. If you can find out that a system is offline, automatically create it, resolve it. The customer may not even know it, or they may be able to see that they&#8217;re reporting it. And we fix it 5\u00a0min later.<\/p>\n<p>69<br \/>\n00:10:46.402 &#8211;&gt; 00:11:05.789<br \/>\nMike Sabia: So identifying it, submitting it categorization, triage, prioritization routing talks about like, Hey, once, you know, created the ticket, you want to classify it. So it gets to the correct group to work on it, you triage it to understand what&#8217;s going on. You prioritize it. Say, hey, yes, this is a high issue.<\/p>\n<p>70<br \/>\n00:11:05.820 &#8211;&gt; 00:11:20.079<br \/>\nMike Sabia: but it&#8217;s only impacting one person versus maybe something that is, you know, just stepped down from high person. But impacting 10,000 people there, there has to obviously be a relative prioritization. And then, you know, per the characterization, the routing to the correct group.<\/p>\n<p>71<br \/>\n00:11:20.080 &#8211;&gt; 00:11:24.090<br \/>\nAndy Whiteside: Yeah, hey, Mike, the 1st one, you it has 12%. Here. You, you agree with that.<\/p>\n<p>72<br \/>\n00:11:28.080 &#8211;&gt; 00:11:30.080<br \/>\nMike Sabia: yeah, I think that&#8217;s about right.<\/p>\n<p>73<br \/>\n00:11:30.320 &#8211;&gt; 00:11:35.289<br \/>\nAndy Whiteside: Yeah, that that means 12% of the total time is spent in detection, slash identification and logging.<\/p>\n<p>74<br \/>\n00:11:36.110 &#8211;&gt; 00:11:36.730<br \/>\nAndy Whiteside : Oui.<\/p>\n<p>75<br \/>\n00:11:36.730 &#8211;&gt; 00:11:57.440<br \/>\nMike Sabia: I mean from an end user, you know, identifying the issue and then submitting. It is part of their part of their problem. How long does it take to go to the right place to open the ticket? How do you find out where you can open the ticket? If you have a problem with your refrigerator who you&#8217;re going to call. That can absolutely be a part of time. But for us, hopefully, they know where to go. And and it would be smaller, I&#8217;d say, on average, 12<\/p>\n<p>76<br \/>\n00:11:57.460 &#8211;&gt; 00:11:58.720<br \/>\nMike Sabia: is reasonable.<\/p>\n<p>77<br \/>\n00:11:59.270 &#8211;&gt; 00:11:59.599<br \/>\nAndy Whiteside: And then.<\/p>\n<p>78<br \/>\n00:11:59.600 &#8211;&gt; 00:12:00.180<br \/>\nMike Sabia: And then.<\/p>\n<p>79<br \/>\n00:12:00.180 &#8211;&gt; 00:12:03.699<br \/>\nAndy Whiteside: That&#8217;s part of that, too. And that&#8217;s that&#8217;s continuous throughout the entire<\/p>\n<p>80<br \/>\n00:12:03.780 &#8211;&gt; 00:12:05.140<br \/>\nAndy Whiteside: cycle. I would think<\/p>\n<p>81<br \/>\n00:12:06.160 &#8211;&gt; 00:12:09.060<br \/>\nAndy Whiteside: the entire time the logging piece.<\/p>\n<p>82<br \/>\n00:12:09.160 &#8211;&gt; 00:12:11.840<br \/>\nAndy Whiteside: Is it logging the initial issue? Or is that.<\/p>\n<p>83<br \/>\n00:12:11.840 &#8211;&gt; 00:12:12.570<br \/>\nFred Reynolds : Oui.<\/p>\n<p>84<br \/>\n00:12:12.740 &#8211;&gt; 00:12:15.560<br \/>\nMike Sabia: I would say, logging the issue, opening the the ticket.<\/p>\n<p>85<br \/>\n00:12:15.560 &#8211;&gt; 00:12:16.280<br \/>\nAndy Whiteside : D'accord.<\/p>\n<p>86<br \/>\n00:12:16.280 &#8211;&gt; 00:12:42.780<br \/>\nFred Reynolds: I have a couple of comments with that. So so one it the the 1st thing coming in of somebody raising an incident, or we&#8217;ll create, instance, for now, right? Detection, identification logging. I mean, it could come from. It depends on the source it&#8217;s coming from, too. It could be so picking up the phone and saying, I have an issue. It could be something come from monitoring tools, and that has a login with it, and logs that go along with that. So I mean, I would say that you would hope that it&#8217;s a lot less than 12% for someone to raise an issue and tell someone what&#8217;s going on to create that<\/p>\n<p>87<br \/>\n00:12:42.780 &#8211;&gt; 00:12:53.610<br \/>\nFred Reynolds: ticket or case for them. I think sometimes it becomes a lot more complex and takes time because of of all the information needs to be captured to create that problem right? The better tech section.<\/p>\n<p>88<br \/>\n00:12:53.610 &#8211;&gt; 00:13:06.760<br \/>\nFred Reynolds: So auto detection is one thing, and then, I think you know, coming off of that to identify what the real problem is is probably why it goes up to 12 because it&#8217;s auto detected. It should be quick. If it&#8217;s something that somebody has identified. The problem is, it&#8217;s gonna take a lot longer to create. That case would be my<\/p>\n<p>89<br \/>\n00:13:07.100 &#8211;&gt; 00:13:08.769<br \/>\nFred Reynolds: my only thoughts on that.<\/p>\n<p>90<br \/>\n00:13:10.500 &#8211;&gt; 00:13:18.559<br \/>\nAndy Whiteside: So so we have the next category which Mike, you&#8217;ve already covered. Categorization triage prioritization and routing. You put that at 25%. That<\/p>\n<p>91<br \/>\n00:13:19.475 &#8211;&gt; 00:13:19.880<br \/>\nAndy Whiteside: that&#8217;s.<\/p>\n<p>92<br \/>\n00:13:19.880 &#8211;&gt; 00:13:26.810<br \/>\nMike Sabia: But they put a 25. I I would hope that that would be quicker. I I&#8217;m I&#8217;m surprised that the the you know<\/p>\n<p>93<br \/>\n00:13:26.810 &#8211;&gt; 00:13:50.860<br \/>\nMike Sabia: I mean, triage is part of it, you know. Yes, you open the ticket. Maybe it gets auto categorized, you know. You prioritize you, Brad it. But the triage could take a fair amount of time. Say, hey, what exactly is going on? Somebody&#8217;s reporting an issue with their VPN. Well, why is it something individually to them is a server down. Is it related to a schedule change? That? That&#8217;s the pro part that I would say increases it.<\/p>\n<p>94<br \/>\n00:13:51.160 &#8211;&gt; 00:13:51.950<br \/>\nMike Sabia : Oui.<\/p>\n<p>95<br \/>\n00:13:51.950 &#8211;&gt; 00:14:16.330<br \/>\nEddie McDonald: Especially if they don&#8217;t have a tool like service now is using itun service mapping. You can see the impact upstream downstream of a server going down. You know you might not know you and I might be able to identify and triage an issue quickly. But if they don&#8217;t have these tools in place that triage. So the 25% could be very valid and a not, you know, up to speed environment.<\/p>\n<p>96<br \/>\n00:14:16.330 &#8211;&gt; 00:14:42.469<br \/>\nFred Reynolds: Well, I&#8217;ll tell you from 10 plus years or like service desk and running manage services. I mean, that triage is that piece right? Categorization, prioritization and routing should be automatic. If you&#8217;re using something like service now to your point, Eddie, for anybody out there that&#8217;s not using a service now, it definitely changes it right? Because who knows how they&#8217;re handling the routing, how they&#8217;re prioritizing? But with tools like service. Now, you can auto set those values. But triage Mike&#8217;s point. That&#8217;s another pain point, right? You got to be able to triage and understand.<\/p>\n<p>97<br \/>\n00:14:42.470 &#8211;&gt; 00:14:47.540<br \/>\nFred Reynolds: Real problem is and define that. Because if you can&#8217;t define it. You can&#8217;t get it to the right people, which means you can&#8217;t route it.<\/p>\n<p>98<br \/>\n00:14:47.540 &#8211;&gt; 00:14:59.590<br \/>\nFred Reynolds: You can&#8217;t put it in the right prioritization because you don&#8217;t know the effect or the business services that you&#8217;re impacted. So so 25% to me, Andy is very reasonable. I think probably 2523% of that is on the triage place.<\/p>\n<p>99<br \/>\n00:14:59.590 &#8211;&gt; 00:15:03.500<br \/>\nAndy Whiteside: Well, like, yeah, 80% of the 25 is more is the triage.<\/p>\n<p>100<br \/>\n00:15:04.152 &#8211;&gt; 00:15:06.760<br \/>\nEddie McDonald: Making up, numbers, now.<\/p>\n<p>101<br \/>\n00:15:06.760 &#8211;&gt; 00:15:11.379<br \/>\nFred Reynolds: Like the same thing said before identification and then triage. And now we&#8217;re up to the 3rd thing. So yeah.<\/p>\n<p>102<br \/>\n00:15:11.380 &#8211;&gt; 00:15:13.809<br \/>\nEddie McDonald: 50% of the time it works every time.<\/p>\n<p>103<br \/>\n00:15:16.350 &#8211;&gt; 00:15:18.180<br \/>\nAndy Whiteside: Oh, you guys are doing fuzzy man!<\/p>\n<p>104<br \/>\n00:15:18.180 &#8211;&gt; 00:15:46.099<br \/>\nEddie McDonald: So the 3rd one with that 30, the team engagement incident, communication collaboration that goes back to what I was talking about before people on phones, talking to other people on phones, shooting emails to each other. It&#8217;s a lot of chasing your tail during that piece, and you can see that this is, you know, as far as this graph is concerned, the largest time Chunk is getting people together to figure out how to go forward with the fix.<\/p>\n<p>105<br \/>\n00:15:46.290 &#8211;&gt; 00:15:56.809<br \/>\nAndy Whiteside: Yeah. Like for me, I&#8217;m envisioning. If I had to call Fred or Eddie to talk about this communication would be 90% of the 30%. But if I had to call Mike, it&#8217;d be like 10% of the 30%.<\/p>\n<p>106<br \/>\n00:15:57.082 &#8211;&gt; 00:16:17.220<br \/>\nFred Reynolds: You know. The thing is, though, it does show that out of the all the time you put into trying to resolve something to get something to close. They&#8217;re saying the bulk of that, I mean 30%, or the the leading cause of that is team engagement, incident, communication and collaboration. Right? So what tools are around that to help someone be more efficient in that? And that&#8217;s a big part of this.<\/p>\n<p>107<br \/>\n00:16:17.220 &#8211;&gt; 00:16:24.000<br \/>\nAndy Whiteside: So since we were letting Mike walk us through this, and Mike didn&#8217;t get a chance to comment on this one comment, Mike, what is your thoughts on this one.<\/p>\n<p>108<br \/>\n00:16:24.000 &#8211;&gt; 00:16:25.179<br \/>\nMike Sabia : Oui.<\/p>\n<p>109<br \/>\n00:16:25.720 &#8211;&gt; 00:16:27.591<br \/>\nMike Sabia: I would say, that&#8217;s<\/p>\n<p>110<br \/>\n00:16:28.130 &#8211;&gt; 00:16:46.919<br \/>\nMike Sabia: It&#8217;s bad that it&#8217;s so high for sure. And there are, you know, if you have customers, many customers reporting the same issue. And you have major major incident management or major issue management there are ways to facilitate the communication and collaboration. But yes.<\/p>\n<p>111<br \/>\n00:16:47.488 &#8211;&gt; 00:16:51.869<br \/>\nMike Sabia: the to to Eddie&#8217;s point. The amount of time it takes<\/p>\n<p>112<br \/>\n00:16:52.020 &#8211;&gt; 00:16:55.950<br \/>\nMike Sabia: us to reach out to the correct people and pull the right people together<\/p>\n<p>113<br \/>\n00:16:56.240 &#8211;&gt; 00:16:57.320<br \/>\nMike Sabia: can be high.<\/p>\n<p>114<br \/>\n00:16:57.650 &#8211;&gt; 00:17:05.510<br \/>\nAndy Whiteside: Is, is it fair to say this section here, the one we&#8217;ve been talking about engagement, incident, communication, and collaboration? That&#8217;s where AI has the most promise.<\/p>\n<p>115<br \/>\n00:17:07.329 &#8211;&gt; 00:17:08.539<br \/>\nFred Reynolds: And the one before.<\/p>\n<p>116<br \/>\n00:17:08.880 &#8211;&gt; 00:17:11.540<br \/>\nMike Sabia: I would say, the second one is probably the the<\/p>\n<p>117<br \/>\n00:17:11.550 &#8211;&gt; 00:17:29.120<br \/>\nMike Sabia: the 1st place, that there&#8217;s opportunity, and some of that is not what we think of as generative. AI is just predictive intelligence. So the second one is more predictive intelligence. How do you auto categorize it? Based on keywords who it&#8217;s coming from the number of people that it&#8217;s impacting the like<\/p>\n<p>118<br \/>\n00:17:29.520 &#8211;&gt; 00:17:39.759<br \/>\nMike Sabia: team engagement. I I&#8217;d see an opportunity for that to to get it to the correct people, and then, you know, notify the people. And pre, you know, automatically schedule meetings.<\/p>\n<p>119<br \/>\n00:17:40.417 &#8211;&gt; 00:17:53.789<br \/>\nMike Sabia: But there&#8217;s also opportunity in the in the last one, as well, you know, once you have written it up and you need to. You know, I know we&#8217;re getting ahead of ourselves. But to to write it up and to summarize the issue and communicate that out. That&#8217;s also an opportunity for AI.<\/p>\n<p>120<br \/>\n00:17:54.330 &#8211;&gt; 00:18:04.489<br \/>\nEddie McDonald: Yeah, I don&#8217;t know if the AI capabilities are there yet to be able to scan the challenges in your seem to be, or your or your<\/p>\n<p>121<br \/>\n00:18:04.690 &#8211;&gt; 00:18:12.680<br \/>\nEddie McDonald: your back office to identify what the problem is, and then propose solutions. I don&#8217;t know if it&#8217;s quite there yet.<\/p>\n<p>122<br \/>\n00:18:12.680 &#8211;&gt; 00:18:23.400<br \/>\nMike Sabia: I I will say that AI does come in for the 1st one detection. You know there are logs out there that will say, hey? This thing is trending up, but it hasn&#8217;t hit your threshold.<\/p>\n<p>123<br \/>\n00:18:23.510 &#8211;&gt; 00:18:30.690<br \/>\nMike Sabia: Do you want to wait till it hits the threshold for you to realize there was a problem, or do you want to have AI seeing? Oh, this is trending up.<\/p>\n<p>124<br \/>\n00:18:30.760 &#8211;&gt; 00:18:37.039<br \/>\nMike Sabia: but isn&#8217;t there? But there&#8217;s another one that&#8217;s just below, but it&#8217;s completely stable. There&#8217;s a great opportunity for AI there.<\/p>\n<p>125<br \/>\n00:18:37.490 &#8211;&gt; 00:18:38.180<br \/>\nMike Sabia: Yep.<\/p>\n<p>126<br \/>\n00:18:38.780 &#8211;&gt; 00:18:49.930<br \/>\nEddie McDonald: Right? Yes. Cause yeah. The cause that functionality exists today in service now. But there&#8217;s only an alert that is sent out. If there&#8217;s an upgrade due or something. It won&#8217;t actually propose that solution.<\/p>\n<p>127<br \/>\n00:18:50.710 &#8211;&gt; 00:18:59.729<br \/>\nFred Reynolds: Let&#8217;s hit large on those solution types. Right? So I mean again, in general, I think it&#8217;s there, like Mike said. Predictive intelligence has been there. People have used that before to help to<\/p>\n<p>128<br \/>\n00:18:59.730 &#8211;&gt; 00:19:21.710<br \/>\nFred Reynolds: do some of that from a from an automation standpoint. But true AI and Gen. AI. I think we&#8217;ll start seeing more use cases around that and how you use it with some of this communication type stuff, right? Summaries of issues. How do you kind of go through toward a resolution. How do you summarize that and get that out? To close that case, I think a lot of that can be used for some general AI. And communication back to the person who put the case in.<\/p>\n<p>129<br \/>\n00:19:22.934 &#8211;&gt; 00:19:29.049<br \/>\nAndy Whiteside: So yeah, kind of teed you go wait a minute with last one Mike. The last section here says closure and post incident, reporting.<\/p>\n<p>130<br \/>\n00:19:29.290 &#8211;&gt; 00:19:30.810<br \/>\nAndy Whiteside: It says 5%.<\/p>\n<p>131<br \/>\n00:19:31.510 &#8211;&gt; 00:19:32.155<br \/>\nMike Sabia: Yeah,<\/p>\n<p>132<br \/>\n00:19:34.100 &#8211;&gt; 00:19:38.350<br \/>\nMike Sabia: I I&#8217;d say, you know, summarizing it in order to give an update to the customer.<\/p>\n<p>133<br \/>\n00:19:38.510 &#8211;&gt; 00:19:41.100<br \/>\nMike Sabia: 5% is reasonable.<\/p>\n<p>134<br \/>\n00:19:41.873 &#8211;&gt; 00:20:09.136<br \/>\nMike Sabia: You know we&#8217;ve all seen tickets that have languished for weeks at a customer because, or at a at a partner or or customer, because it just takes so long to resolve it, but assuming that it&#8217;s a a reasonably approached ticket summarizing it and closing it is about 5% seems reasonable. But again, AI is also ability to speed this up as far as summarizing the issue, summarizing the the communications into<\/p>\n<p>135<br \/>\n00:20:10.125 &#8211;&gt; 00:20:12.800<br \/>\nMike Sabia: readable outputs for the end user.<\/p>\n<p>136<br \/>\n00:20:15.990 &#8211;&gt; 00:20:18.890<br \/>\nAndy Whiteside: Okay, the next section gets<\/p>\n<p>137<br \/>\n00:20:18.970 &#8211;&gt; 00:20:28.490<br \/>\nAndy Whiteside: to my point earlier and it talks about what percentage of Mttr is inactive time spent waiting for information or response.<\/p>\n<p>138<br \/>\n00:20:28.880 &#8211;&gt; 00:20:31.180<br \/>\nAndy Whiteside: Mike, you want to talk through the numbers they provide here.<\/p>\n<p>139<br \/>\n00:20:31.180 &#8211;&gt; 00:20:36.440<br \/>\nMike Sabia: So this is quotes from people on thinking how much time is wasted.<\/p>\n<p>140<br \/>\n00:20:36.450 &#8211;&gt; 00:20:45.390<br \/>\nMike Sabia: So 27% think that 50% or more time is wasted 42%. It says it&#8217;s a quarter. 19% says it&#8217;s 10<\/p>\n<p>141<br \/>\n00:20:45.580 &#8211;&gt; 00:20:49.049<br \/>\nMike Sabia: and 12% says it&#8217;s it&#8217;s almost no wasted time.<\/p>\n<p>142<br \/>\n00:20:49.646 &#8211;&gt; 00:21:03.119<br \/>\nMike Sabia: I&#8217;m assuming that this question is asked of the It departments who are working it? Not, you know, the end user. The end user is not going to normally know that, but might be wondering how much time is being wasted. Why haven&#8217;t I got response back?<\/p>\n<p>143<br \/>\n00:21:06.740 &#8211;&gt; 00:21:28.770<br \/>\nMike Sabia: it&#8217;s all perceptive, you know, an end user. I might think that it&#8217;s it&#8217;s wasted. I I recently opened some tickets, and I&#8217;m like, Hey, where? What&#8217;s my status? Not with with internal, but with service now itself saying, Hey, what&#8217;s the status of my ticket? And and I don&#8217;t get an answer and a lot of it&#8217;s maybe that person hasn&#8217;t prioritized my ticket across. However, many other tickets that are assigned to them.<\/p>\n<p>144<br \/>\n00:21:28.850 &#8211;&gt; 00:21:31.820<br \/>\nMike Sabia: it to me that was a waste of time, but<\/p>\n<p>145<br \/>\n00:21:31.890 &#8211;&gt; 00:21:33.110<br \/>\nMike Sabia: or<\/p>\n<p>146<br \/>\n00:21:33.150 &#8211;&gt; 00:21:39.219<br \/>\nMike Sabia: person working on it, maybe it&#8217;s just an efficient use of what they were assigned, and and their availability so.<\/p>\n<p>147<br \/>\n00:21:39.220 &#8211;&gt; 00:21:56.910<br \/>\nEddie McDonald: I I feel like it&#8217;s implied that the question was posed to the folks working on the issue and the takeaway. If you get out of the granularity of these numbers, 90% of the people question says, there are significant wasted time in the resolution.<\/p>\n<p>148<br \/>\n00:21:56.910 &#8211;&gt; 00:22:18.730<br \/>\nEddie McDonald: Yeah, it&#8217;s a big deal. I I mean, it&#8217;s it goes back to what Andy and I were saying at the beginning that this is every hour. And the next segment is, gonna talk about what that Mttr is. If it&#8217;s 30\u00a0min to 2\u00a0h. If we average out an hour times X number of people, these are real dollars that these issues are burning through.<\/p>\n<p>149<br \/>\n00:22:20.580 &#8211;&gt; 00:22:48.860<br \/>\nFred Reynolds: Look. I think I think those percentages to me would seem accurate. But again, to Mike&#8217;s point is perception, right? So 50% of times wasted. I feel like that. Probably everything I open because you always feel like half the time you&#8217;re trying to re-explain something you&#8217;ve already said is an issue, or you&#8217;re waiting for people to figure out how to go about fixing it. It&#8217;s usually not how to fix this user identifying and triaging it. So you have to think that if half the battle is actually articulating what the problem is and triaging it, then certainly you cut 50% of your waste of time out by trying to get to that quicker.<\/p>\n<p>150<br \/>\n00:22:48.990 &#8211;&gt; 00:22:50.209<br \/>\nFred Reynolds: That would be my takeaway.<\/p>\n<p>151<br \/>\n00:22:50.210 &#8211;&gt; 00:22:57.982<br \/>\nMike Sabia: I I haven&#8217;t seen it with many customers, but the 1st the 1st company I work for when I got into service now, which is 11 years ago,<\/p>\n<p>152<br \/>\n00:22:58.570 &#8211;&gt; 00:23:01.079<br \/>\nMike Sabia: as an education company. The way they<\/p>\n<p>153<br \/>\n00:23:01.090 &#8211;&gt; 00:23:04.260<br \/>\nMike Sabia: did their changes is they actually looked at how<\/p>\n<p>154<br \/>\n00:23:04.300 &#8211;&gt; 00:23:13.519<br \/>\nMike Sabia: much, how many impacted user minutes there were like, Hey, this took an hour or this took 10\u00a0min, but multiplied by how many people were impacted<\/p>\n<p>155<br \/>\n00:23:13.680 &#8211;&gt; 00:23:28.339<br \/>\nMike Sabia: and based on that that calculation. Then they would determine. You know, when a change could happen. Is it something that could happen during the day, or has to happen the weekend because of of just how many impacted minutes there were of an inch issue<\/p>\n<p>156<br \/>\n00:23:28.390 &#8211;&gt; 00:23:30.060<br \/>\nMike Sabia: as a result of it.<\/p>\n<p>157<br \/>\n00:23:30.420 &#8211;&gt; 00:23:33.440<br \/>\nMike Sabia: a planned or unplanned change. So<\/p>\n<p>158<br \/>\n00:23:33.980 &#8211;&gt; 00:23:35.469<br \/>\nMike Sabia: it&#8217;s interesting.<\/p>\n<p>159<br \/>\n00:23:36.147 &#8211;&gt; 00:23:41.519<br \/>\nMike Sabia: But by itself, without knowing how many people it&#8217;s impacting.<\/p>\n<p>160<br \/>\n00:23:43.060 &#8211;&gt; 00:23:59.670<br \/>\nMike Sabia: I don&#8217;t know. I mean, you know, is it 50% time wasted? But it&#8217;s a a low priority issue that&#8217;s quite different from some super high critical issues impacting thousands of people or systems offline. And and I don&#8217;t know. The statistics fully represent that.<\/p>\n<p>161<br \/>\n00:24:00.230 &#8211;&gt; 00:24:17.649<br \/>\nEddie McDonald: Yeah, I think these I mean again, just looking at the numbers. I think these are rounded up, and this are general. Yes, I mean. I know personally that when I in my life, when I try to explain, like what&#8217;s wrong with my marriage, 50% of that time is wasted, you know, that&#8217;s just time that I&#8217;m never gonna get back.<\/p>\n<p>162<br \/>\n00:24:18.470 &#8211;&gt; 00:24:20.237<br \/>\nFred Reynolds: Is that your 50% or something.<\/p>\n<p>163<br \/>\n00:24:20.490 &#8211;&gt; 00:24:25.838<br \/>\nEddie McDonald: Yeah, yeah, my 50% is all wasted time trying to explain that problem.<\/p>\n<p>164<br \/>\n00:24:26.490 &#8211;&gt; 00:24:28.449<br \/>\nAndy Whiteside: I&#8217;m not touching that one. Okay.<\/p>\n<p>165<br \/>\n00:24:29.600 &#8211;&gt; 00:24:30.000<br \/>\nAndy Whiteside: that&#8217;s okay.<\/p>\n<p>166<br \/>\n00:24:30.000 &#8211;&gt; 00:24:31.329<br \/>\nFred Reynolds: Don&#8217;t want my mouth moved, but go ahead and.<\/p>\n<p>167<br \/>\n00:24:32.490 &#8211;&gt; 00:24:40.539<br \/>\nAndy Whiteside: So it says, what&#8217;s the problem? And then, for instance, problems what are the biggest challenges to effective incident, response and management?<\/p>\n<p>168<br \/>\n00:24:40.710 &#8211;&gt; 00:24:42.199<br \/>\nAndy Whiteside: Select 2<\/p>\n<p>169<br \/>\n00:24:42.584 &#8211;&gt; 00:24:47.299<br \/>\nAndy Whiteside: Mike again, I&#8217;ll let you lead us on this. But what what if? What are people<\/p>\n<p>170<br \/>\n00:24:47.500 &#8211;&gt; 00:24:49.529<br \/>\nAndy Whiteside: saying? The problems are.<\/p>\n<p>171<br \/>\n00:24:49.830 &#8211;&gt; 00:25:03.069<br \/>\nMike Sabia: So since you can respond to 2, these numbers should app, add up to 200. So looking at the 1st one, it says, 51% of people say that getting the right teams engaged in collaborating is critical. And I would agree.<\/p>\n<p>172<br \/>\n00:25:03.472 &#8211;&gt; 00:25:21.740<br \/>\nMike Sabia: You know, I I&#8217;ve opened tickets where I&#8217;m like, Hey, I don&#8217;t know if it&#8217;s I. I opened it against the correct team. And so sometimes I I open 2 tickets. Because I&#8217;m like, well, probably one of these will get it quicker, because I need a quick answer, you know. Being able to get it to the correct team is is absolutely high critical importance.<\/p>\n<p>173<br \/>\n00:25:22.330 &#8211;&gt; 00:25:48.399<br \/>\nMike Sabia: Because you can&#8217;t start until it&#8217;s to the right team second, lack of a unified view and dependency mapping of service elements. That&#8217;s 39%. And this goes back to one things that Eddie mentioned. You know, a person calling up doesn&#8217;t know that there&#8217;s a load balancer, web server or the like down. They just know that their service is having an issue. Their VPN a service is having an issue. Their email is having an issue their connectivity to some systems having an issue, and to be able to<\/p>\n<p>174<br \/>\n00:25:48.400 &#8211;&gt; 00:25:59.530<br \/>\nMike Sabia: lock or associate that service to the dependent items and then identify, you know which issues or which Cis might have changed recently. That could be.<\/p>\n<p>175<br \/>\n00:25:59.560 &#8211;&gt; 00:26:09.110<br \/>\nMike Sabia: you know, causing this is is high, and and I would probably say, this is in reality, probably one of the highest, but it is ranked second.<\/p>\n<p>176<br \/>\n00:26:09.250 &#8211;&gt; 00:26:36.459<br \/>\nFred Reynolds: So my, I was gonna pause you for seconds, those number 2. I&#8217;m glad you just said it, because that&#8217;s that&#8217;s the 1st thing popped my mind. I&#8217;m surprised by that, because the reality is what Mike said, it is that number 2, the unified view, understanding what&#8217;s been affected service map and understand what what&#8217;s being impacted. That&#8217;s the number one thing that&#8217;s going to delay your time, because in order to find that out, sometimes you have to get teams together. Which teams do you get together like it kind of goes hand in hand, but really not understanding what&#8217;s being impacted<\/p>\n<p>177<br \/>\n00:26:36.460 &#8211;&gt; 00:27:00.819<br \/>\nFred Reynolds: is what takes the most wasted time perception, because once you find out the person, let&#8217;s just say it ends up being a networking issue, a bad port in somebody&#8217;s office, but they think it&#8217;s a hundred things else by the time you get to identify that that person could probably fix it very quickly. But you spend a lot of time identifying what&#8217;s been impacted. So I would like Mike, you said it. I was gonna say, if you didn&#8217;t like that number 2 instead of 39 should probably be like 80, and the rest could fall behind that, in my opinion. But.<\/p>\n<p>178<br \/>\n00:27:03.338 &#8211;&gt; 00:27:18.670<br \/>\nMike Sabia: Right? So the 3rd one ha! Is understanding the impact. And when I open tickets, whether it&#8217;s internally or with service now, or you know about my refrigerator. I always start saying, You know, I don&#8217;t just say, Hey, this is the issue. I&#8217;m saying, Hey, this is my impact. I&#8217;m trying to do this I can&#8217;t.<\/p>\n<p>179<br \/>\n00:27:18.960 &#8211;&gt; 00:27:25.059<br \/>\nMike Sabia: And then I go into the details of what I&#8217;m seeing, so that people can understand what I&#8217;m what I&#8217;m dealing with.<\/p>\n<p>180<br \/>\n00:27:25.720 &#8211;&gt; 00:27:28.320<br \/>\nMike Sabia: The the reason why this is important.<\/p>\n<p>181<br \/>\n00:27:30.160 &#8211;&gt; 00:27:41.170<br \/>\nMike Sabia: I. I think that as a receiver of tickets, not knowing that context where you have to go back into the custom. Say, Okay, I&#8217;m I&#8217;m seeing what you&#8217;re seeing. But but why is this important<\/p>\n<p>182<br \/>\n00:27:42.030 &#8211;&gt; 00:27:44.180<br \/>\nMike Sabia: that that could be fairly large.<\/p>\n<p>183<br \/>\n00:27:45.870 &#8211;&gt; 00:27:50.380<br \/>\nMike Sabia: going on to the 4th one inefficient manual processes and bottlenecks.<\/p>\n<p>184<br \/>\n00:27:51.310 &#8211;&gt; 00:28:08.119<br \/>\nMike Sabia: for sure. I mean automating these tools, whether it&#8217;s orchestration to fix the issue or having knowledge articles to describe the issue. You know, people have had this problem before. Why am I not able to find a quick Google answer or see it? This, in my, in my knowledge base that could be considerable.<\/p>\n<p>185<br \/>\n00:28:08.600 &#8211;&gt; 00:28:09.200<br \/>\nMike Sabia: A lot.<\/p>\n<p>186<br \/>\n00:28:09.200 &#8211;&gt; 00:28:21.919<br \/>\nEddie McDonald: I can that one&#8217;s actually really important as well, because you know, not to work in a commercial in the middle of this, podcast but every every conversation we have with our customer begins with process.<\/p>\n<p>187<br \/>\n00:28:21.920 &#8211;&gt; 00:28:49.560<br \/>\nEddie McDonald: We are not going to build a platform out to something that&#8217;s that&#8217;s antiquated and broken. So inefficient manual processes, we can practically automate any process. I mean, it&#8217;s a blanket statement. There&#8217;s some things we can&#8217;t. But 98% of the time we&#8217;re going to be able to automate that and remove those bottlenecks. So that is something where we start the conversation which by this this takes care of 31% of those challenges right there by automating these processes.<\/p>\n<p>188<br \/>\n00:28:50.430 &#8211;&gt; 00:28:51.150<br \/>\nEddie McDonald: Okay.<\/p>\n<p>189<br \/>\n00:28:52.511 &#8211;&gt; 00:29:04.460<br \/>\nMike Sabia: The second to last is too many alerts, as if you had, like an alerting system arm system that&#8217;s reporting on issues. And it&#8217;s just spamming you with tickets. It&#8217;s hard to know what&#8217;s most important.<\/p>\n<p>190<br \/>\n00:29:04.680 &#8211;&gt; 00:29:08.899<br \/>\nMike Sabia: So there is a certain amount of noise that one has to deal with.<\/p>\n<p>191<br \/>\n00:29:10.300 &#8211;&gt; 00:29:22.900<br \/>\nMike Sabia: I could see why, that&#8217;s important. And hopefully, as once you start, seeing that you start having some filters on items to indicate whether it&#8217;s automated whether people are actually, you know, real people are reporting it.<\/p>\n<p>192<br \/>\n00:29:23.320 &#8211;&gt; 00:29:28.520<br \/>\nMike Sabia: whether it&#8217;s just you know, flipping over and over and over.<\/p>\n<p>193<br \/>\n00:29:28.890 &#8211;&gt; 00:29:30.420<br \/>\nMike Sabia: That&#8217;s 19%.<\/p>\n<p>194<br \/>\n00:29:30.490 &#8211;&gt; 00:29:38.775<br \/>\nMike Sabia: And then the last one of the biggest challenges is Silas systems and tools. And of course, that&#8217;s a a fantastic<\/p>\n<p>195<br \/>\n00:29:39.680 &#8211;&gt; 00:30:02.249<br \/>\nMike Sabia: ability of service. Now that it brings everything into a single pane of glass, that instead of having one system for this, and one system for that, one system, for the 3rd thing, you can see everything together. You can see your incident, you can see how it&#8217;s tied to your scene to be. You can see how it&#8217;s tied to your users, whether it&#8217;s associated with projects, or or the like, or everything being able to come together in service now is, is<\/p>\n<p>196<br \/>\n00:30:02.470 &#8211;&gt; 00:30:08.269<br \/>\nMike Sabia: it is able to reduce that percentage for sure for any service. Now. Ticket.<\/p>\n<p>197<br \/>\n00:30:08.490 &#8211;&gt; 00:30:31.629<br \/>\nFred Reynolds: And you know one thing I like one thing I love about our team, and here in our service. Now, partner, says Integrs, you look at all of those. What are 6 items? Right? I could take each one of those and kind of identify, you know, within the applications of service. Now within the platform, how it can help you solve these things even because of too many alerts. Right? There&#8217;s so much things we&#8217;ve done in the past to help with that, you know, between stacking the business services. Aspect of it. Right? You know, being able to<\/p>\n<p>198<br \/>\n00:30:31.630 &#8211;&gt; 00:30:55.389<br \/>\nFred Reynolds: to be able to take one instance, a real issue, and then fold up 45 other things underneath it, because you know that that&#8217;s not the real cause. I mean, there&#8217;s so many things that we can look at that service now can solve, for that&#8217;s going to be the next part. But that&#8217;s 1 thing I love about our team is that we have so much experience of years of not only implementing service now in technology workflows, but also being in the industry like Mike said, seeing that in the companies we work for and doing it real time.<\/p>\n<p>199<br \/>\n00:30:55.710 &#8211;&gt; 00:30:56.080<br \/>\nAndy Whiteside : Oui.<\/p>\n<p>200<br \/>\n00:30:56.080 &#8211;&gt; 00:31:21.029<br \/>\nEddie McDonald: You know, Fred&#8217;s a great point. I mean, you and I are working on this deal right now, what&#8217;s actually closing? It&#8217;s a global Satellite company. And we&#8217;ve been scoping this work. They&#8217;re going to source to pay from from opportunity creation to implementation. 90% of the last 3 months has been talking about their processes and streamlining those removing those bottlenecks before we ever talk about the platform. So<\/p>\n<p>201<br \/>\n00:31:21.030 &#8211;&gt; 00:31:27.850<br \/>\nEddie McDonald: that is separate from this Mttr. Conversation. But it&#8217;s a thread that runs through everything that we do.<\/p>\n<p>202<br \/>\n00:31:28.210 &#8211;&gt; 00:31:29.120<br \/>\nFred Reynolds: Exactly.<\/p>\n<p>203<br \/>\n00:31:29.303 &#8211;&gt; 00:31:36.646<br \/>\nAndy Whiteside: You know. For me it&#8217;s most exciting. 2 things, one, Fred made a comment. We&#8217;ve never lost a customer that on the service. Now side that that&#8217;s close. It may be a hundred percent true, but it&#8217;s really really close.<\/p>\n<p>204<br \/>\n00:31:37.181 &#8211;&gt; 00:31:57.850<br \/>\nAndy Whiteside: But what I love about this space and it&#8217;s just the reality of it is if you go in and you solve number 3 here, business context, understanding the impact. And that number goes down, all the other numbers go up because it&#8217;s still just a percentage of the overall problem, and the problem gets better and better and better. But it never goes away. It just moves from 1 1<\/p>\n<p>205<br \/>\n00:31:58.120 &#8211;&gt; 00:32:00.330<br \/>\nAndy Whiteside: answer to the other.<\/p>\n<p>206<br \/>\n00:32:00.370 &#8211;&gt; 00:32:04.090<br \/>\nAndy Whiteside: and you&#8217;re just whittling them all down the best you can. But you know it&#8217;s it&#8217;s still<\/p>\n<p>207<br \/>\n00:32:04.280 &#8211;&gt; 00:32:04.830<br \/>\nAndy Whiteside: it&#8217;ll.<\/p>\n<p>208<br \/>\n00:32:04.830 &#8211;&gt; 00:32:08.350<br \/>\nEddie McDonald: And eventually they&#8217;ll stop asking the questions. That&#8217;s the goal.<\/p>\n<p>209<br \/>\n00:32:08.350 &#8211;&gt; 00:32:32.389<br \/>\nFred Reynolds: Well, truthfully, guys, I lived in a state for many, many years where I had that type of status there, like those type of measurements, and over here the measurements on our on our meantime resolution numbers. Right? So how do you drive those numbers down, or how do you put it within the sla time, as Mike mentioned. Right you. You set your sla&#8217;s, and you have to measure against that. And as you attack these things, so maybe it is that people getting the teams dead better together. And you implement some things within service. Now to<\/p>\n<p>210<br \/>\n00:32:32.390 &#8211;&gt; 00:32:50.609<br \/>\nFred Reynolds: help with that skills based routing? Who&#8217;s the right people. How do you get it to them? Right? How do you notify them? How do you make sure they&#8217;re responding? And all those I mean, all those things are really necessary, and you will see those numbers going down here. And then why? Because those numbers drop over here and you tackle the next thing. It&#8217;s a never ending battle. Once you fix a couple of things, something else is going to pop up.<\/p>\n<p>211<br \/>\n00:32:50.610 &#8211;&gt; 00:32:50.970<br \/>\nAndy Whiteside: What?<\/p>\n<p>212<br \/>\n00:32:50.970 &#8211;&gt; 00:32:51.350<br \/>\nEddie McDonald: Right.<\/p>\n<p>213<br \/>\n00:32:51.350 &#8211;&gt; 00:32:59.319<br \/>\nAndy Whiteside: Like it&#8217;s like whack a mole. But but the moles are getting smaller and less impactful. But yet there&#8217;s always going to be moles to whack.<\/p>\n<p>214<br \/>\n00:32:59.320 &#8211;&gt; 00:33:15.810<br \/>\nFred Reynolds: When you get to a point where your Mttr is within your Sla range, and you don&#8217;t have to discussion anymore. But it&#8217;s not that difficult to to attack your Mttr. For most companies, if you have a solution like service now, outside of that, I can&#8217;t really speak to it right. But I had to implement service now to get there.<\/p>\n<p>215<br \/>\n00:33:15.810 &#8211;&gt; 00:33:20.260<br \/>\nAndy Whiteside: Have visibility and the tools. You&#8217;re right. If you don&#8217;t, you ain&#8217;t never gonna solve it.<\/p>\n<p>216<br \/>\n00:33:20.260 &#8211;&gt; 00:33:21.110<br \/>\nFred Reynolds: That&#8217;s correct.<\/p>\n<p>217<br \/>\n00:33:21.110 &#8211;&gt; 00:33:27.929<br \/>\nEddie McDonald: Well, it&#8217;s like my drinking problem. My 1st step was acknowledging that I had a problem, and then it&#8217;s easy to fix.<\/p>\n<p>218<br \/>\n00:33:28.530 &#8211;&gt; 00:33:29.130<br \/>\nFred Reynolds: Yup!<\/p>\n<p>219<br \/>\n00:33:29.590 &#8211;&gt; 00:33:31.639<br \/>\nAndy Whiteside: Man. Here we go down that one, though.<\/p>\n<p>220<br \/>\n00:33:31.640 &#8211;&gt; 00:33:33.860<br \/>\nEddie McDonald: I, yeah, dude, yeah, I I mean, I didn&#8217;t.<\/p>\n<p>221<br \/>\n00:33:33.860 &#8211;&gt; 00:33:34.710<br \/>\nFred Reynolds: But I&#8217;ll sleep in there.<\/p>\n<p>222<br \/>\n00:33:34.710 &#8211;&gt; 00:33:36.715<br \/>\nEddie McDonald: I&#8217;m all over the place today.<\/p>\n<p>223<br \/>\n00:33:37.050 &#8211;&gt; 00:33:39.280<br \/>\nAndy Whiteside: Think I think I know what the wife conversation.<\/p>\n<p>224<br \/>\n00:33:39.280 &#8211;&gt; 00:33:40.110<br \/>\nFred Reynolds: I could.<\/p>\n<p>225<br \/>\n00:33:40.110 &#8211;&gt; 00:33:40.810<br \/>\nAndy Whiteside: And I would.<\/p>\n<p>226<br \/>\n00:33:42.470 &#8211;&gt; 00:33:44.320<br \/>\nFred Reynolds: Can we do another podcast on Eddie.<\/p>\n<p>227<br \/>\n00:33:45.310 &#8211;&gt; 00:33:46.300<br \/>\nEddie McDonald: Michael.<\/p>\n<p>228<br \/>\n00:33:46.300 &#8211;&gt; 00:33:47.300<br \/>\nAndy Whiteside: Oh, you hadn&#8217;t comment!<\/p>\n<p>229<br \/>\n00:33:47.300 &#8211;&gt; 00:33:50.220<br \/>\nMike Sabia: I am. Gonna add one piece<\/p>\n<p>230<br \/>\n00:33:50.230 &#8211;&gt; 00:33:51.000<br \/>\nMike Sabia: and<\/p>\n<p>231<br \/>\n00:33:51.980 &#8211;&gt; 00:33:54.671<br \/>\nMike Sabia: And now Eddie&#8217;s distracted me.<\/p>\n<p>232<br \/>\n00:33:57.590 &#8211;&gt; 00:34:22.979<br \/>\nMike Sabia: I wanted to say, oh, right. So even if your Mtr. Is going down or is good. That doesn&#8217;t mean that there might be certain groups where it&#8217;s it&#8217;s going higher, and that could be a manual effort. Hey? Let me go look at all of my teams, and maybe do Mtr. By each one. But service now, going back to the AI capability, there are AI capabilities that will help you identify those teams. You don&#8217;t have to wait through the data.<\/p>\n<p>233<br \/>\n00:34:24.489 &#8211;&gt; 00:34:25.219<br \/>\nFred Reynolds: Good point.<\/p>\n<p>234<br \/>\n00:34:26.690 &#8211;&gt; 00:34:46.529<br \/>\nAndy Whiteside: Alright last section. Here we&#8217;re running low on time, and I&#8217;m sure our listeners are either enthusiastic or gone to sleep one or the other. It talks about finding a realistic solution. And I like that. They call it a realistic solution, not just a solution. Because, as we were just pointing out, it&#8217;s it&#8217;s it&#8217;s not solvable. It&#8217;s just we can make it better. Mike. Go ahead.<\/p>\n<p>235<br \/>\n00:34:46.870 &#8211;&gt; 00:34:47.360<br \/>\nAndy Whiteside: Well.<\/p>\n<p>236<br \/>\n00:34:47.360 &#8211;&gt; 00:35:07.069<br \/>\nMike Sabia: This is interesting. It talks about, of course, you know, doing information, sharing collaboration, cross functional workflows to address these challenges, but they go into the fact that most it leaders expect that outage, frequency, and duration would continue to rise because of how much stuff is going on, but that an intriguing 18% of<\/p>\n<p>237<br \/>\n00:35:07.080 &#8211;&gt; 00:35:16.238<br \/>\nMike Sabia: the panel counter trend ran counter trend staying. That instance actually have decreased, due to proactive systems that have been put place, you know.<\/p>\n<p>238<br \/>\n00:35:16.650 &#8211;&gt; 00:35:38.059<br \/>\nMike Sabia: if we&#8217;re talking about what I mentioned at the beginning, the deflection of tickets, you might see that overall. The number of tickets are going down because you have those deflections. But that might mean that the length of your tickets might be going higher because the remaining tickets are maybe more complex<\/p>\n<p>239<br \/>\n00:35:38.330 &#8211;&gt; 00:35:42.749<br \/>\nMike Sabia: multiple value multiple issues coming on the plate here.<\/p>\n<p>240<br \/>\n00:35:43.759 &#8211;&gt; 00:35:53.359<br \/>\nMike Sabia: Going to the 3rd paragraph, you know, service now, absolutely offers many robust weapons in the battle from predictive intelligence to more advanced AI<\/p>\n<p>241<br \/>\n00:35:53.390 &#8211;&gt; 00:35:54.274<br \/>\nMike Sabia: to<\/p>\n<p>242<br \/>\n00:35:55.730 &#8211;&gt; 00:36:01.219<br \/>\nMike Sabia: the ability to do. You know, major incident management communication.<\/p>\n<p>243<br \/>\n00:36:01.370 &#8211;&gt; 00:36:12.340<br \/>\nMike Sabia: the ability to have that uniform unified platform in order to get rid of some of those silos. You can&#8217;t go into all of the service style capabilities in in just a<\/p>\n<p>244<br \/>\n00:36:12.430 &#8211;&gt; 00:36:23.879<br \/>\nMike Sabia: brief blog to remediate these issues. But Servicenow Platform is absolutely trying to address Mtr. And all the topics that we&#8217;ve discussed during this blog today.<\/p>\n<p>245<br \/>\n00:36:24.090 &#8211;&gt; 00:36:24.740<br \/>\nMike Sabia : Oui.<\/p>\n<p>246<br \/>\n00:36:24.740 &#8211;&gt; 00:36:41.171<br \/>\nEddie McDonald: Yeah. And and you know, at its core. And Mike just touched on, it&#8217;s the unified platform, I think, is these is where we start. You know you can collaborate if your operations team your help desk, your end users. Your leaders are all on the same platform, working in the same plane of class<\/p>\n<p>247<br \/>\n00:36:41.710 &#8211;&gt; 00:36:56.340<br \/>\nEddie McDonald: life just gets simpler, you know, is just is, especially when you get visibility into your your your organization, all your your seem to be all of your org. Your service mapping is all in one place.<\/p>\n<p>248<br \/>\n00:36:56.340 &#8211;&gt; 00:37:12.289<br \/>\nEddie McDonald: then these decisions and these resolution times will naturally go down. It&#8217;s just a it starts with a simple solution which is a unified platform. And then we can scale into those other areas where those those percentages were high.<\/p>\n<p>249<br \/>\n00:37:12.290 &#8211;&gt; 00:37:39.240<br \/>\nFred Reynolds: And I. And I wanted to say this, too, I think finding a realistic solution has to come with also the investment, a realistic investment from the people trying to solve the problem. You know, I think that when you have a platform like service now, and you&#8217;re trying to really solve for problems. I think that&#8217;s the biggest thing that I see is a lack of investment and time to make those things get corrected. If you have a lot of issues with issues, with team collaborations or triage and those types of things<\/p>\n<p>250<br \/>\n00:37:39.240 &#8211;&gt; 00:37:59.909<br \/>\nFred Reynolds: you really have to spend the time like, it was important for us to spend 3 months with the customer, to understand what their real process issues are. What&#8217;s the bottleneck? Because if we don&#8217;t find that out or fix that and putting a tool into many types, not even going to solve any of that stuff. Right? So I think it&#8217;s a matter of somebody has to have a realistic solution by realistically looking at the problem at hand and understanding how we need to solve that. And I.<\/p>\n<p>251<br \/>\n00:37:59.910 &#8211;&gt; 00:38:01.460<br \/>\nEddie McDonald: Yeah, sorry. That&#8217;s.<\/p>\n<p>252<br \/>\n00:38:01.610 &#8211;&gt; 00:38:11.999<br \/>\nFred Reynolds: Yeah, but I would say, service now is toolbox. Right? I&#8217;m I&#8217;m sold. I quit my other job to come here and just concentrate on service. Now, for that reason it is a Swiss army life. It can solve all these things we mentioned right.<\/p>\n<p>253<br \/>\n00:38:12.180 &#8211;&gt; 00:38:31.740<br \/>\nEddie McDonald: Yeah, Fred, I think the spot on point. I think it&#8217;s really important to understand that this is not a Band-aid approach. This is a strategic solution to an overarching problem. And it&#8217;s not gonna happen in a day. It&#8217;s gonna it&#8217;s organizational change. It&#8217;s changing hearts and minds. It&#8217;s changing platforms. This is a big deal to a long term solution.<\/p>\n<p>254<br \/>\n00:38:31.740 &#8211;&gt; 00:38:46.709<br \/>\nFred Reynolds: The long term solution with digital transformation, culture change and everything. I mean, it starts somewhere right? And you find your biggest problems. And you try to prove that and solve it? And again, Nttr. Is a major problem for everybody. In my opinion you just either have it solved or you don&#8217;t.<\/p>\n<p>255<br \/>\n00:38:47.020 &#8211;&gt; 00:38:50.130<br \/>\nFred Reynolds: Alright, that&#8217;s my final comments, Andy, I mean Andy.<\/p>\n<p>256<br \/>\n00:38:50.790 &#8211;&gt; 00:38:52.205<br \/>\nAndy Whiteside: Well, maybe<\/p>\n<p>257<br \/>\n00:38:53.620 &#8211;&gt; 00:38:54.970<br \/>\nEddie McDonald: You mean.<\/p>\n<p>258<br \/>\n00:38:54.970 &#8211;&gt; 00:39:01.599<br \/>\nAndy Whiteside: Earlier sla&#8217;s. And I just wonder, from y&#8217;all&#8217;s experience do you find people coming to us with defined sla&#8217;s? Or is that<\/p>\n<p>259<br \/>\n00:39:01.940 &#8211;&gt; 00:39:02.700<br \/>\nAndy Whiteside: typically.<\/p>\n<p>260<br \/>\n00:39:02.700 &#8211;&gt; 00:39:10.840<br \/>\nEddie McDonald: Yeah, we&#8217;ll have something. It&#8217;s usually generic. The the problem comes in when they have the sla is the same for an incident, or request<\/p>\n<p>261<br \/>\n00:39:10.990 &#8211;&gt; 00:39:16.510<br \/>\nEddie McDonald: those 2 things. There&#8217;s oil and water. They&#8217;re not the same. But yeah, they generally have something to find.<\/p>\n<p>262<br \/>\n00:39:16.730 &#8211;&gt; 00:39:38.190<br \/>\nFred Reynolds: I think what&#8217;s important about sla is. I will say this because I think it&#8217;s a matter of me dealing with this for so Long Mike&#8217;s mentioned deflection a couple of times. I think that&#8217;s very interesting, right? Cause I feel like that couple of the providers for me. Let&#8217;s just say cable provider, for instance, right? Their their tactic is deflection, and it makes you want to give up on stuff right? So that that&#8217;s a man I was kind of losing a little bit.<\/p>\n<p>263<br \/>\n00:39:38.190 &#8211;&gt; 00:39:49.190<br \/>\nMike Sabia: Be good and bad deflection if you can get the person to self self resolve through like a service. Now, Portal fantastic. But yeah, if you just want to kiss, kick the can down the road as Fred is laying.<\/p>\n<p>264<br \/>\n00:39:49.350 &#8211;&gt; 00:39:50.350<br \/>\nMike Sabia: That&#8217;s a problem.<\/p>\n<p>265<br \/>\n00:39:50.680 &#8211;&gt; 00:39:51.630<br \/>\nFred Reynolds: That is a problem.<\/p>\n<p>266<br \/>\n00:39:51.900 &#8211;&gt; 00:40:01.080<br \/>\nEddie McDonald: Yeah, or those those those voice prompt loops you get in and you can&#8217;t get out of. That&#8217;s a great way to deflect a ticket from ever being created.<\/p>\n<p>267<br \/>\n00:40:01.080 &#8211;&gt; 00:40:02.289<br \/>\nFred Reynolds: That&#8217;s exactly right.<\/p>\n<p>268<br \/>\n00:40:03.450 &#8211;&gt; 00:40:21.069<br \/>\nAndy Whiteside: Hey? Let&#8217;s see the the one last thing I was gonna say, we get a lot of pushback on service now being expensive if we apply what we&#8217;ve talked about here. And we&#8217;re solving problems faster. And we&#8217;re bringing, maybe replacing other tools in the process. And we have one unified platform to do this with Eddie. Is it expensive.<\/p>\n<p>269<br \/>\n00:40:21.070 &#8211;&gt; 00:40:30.970<br \/>\nEddie McDonald: Absolutely not. And that is such. I I look, I love that question. I love that comment. Service now is not expensive. People are expensive<\/p>\n<p>270<br \/>\n00:40:30.970 &#8211;&gt; 00:40:55.369<br \/>\nEddie McDonald: platform. Technology is cheap across the board. Whether it&#8217;s a laptop or a platform. Technology is cheap. It&#8217;s our job to show you where the value is. If you feel the service now is expensive. Whoever you&#8217;ve spoken to in the past has not done a good job of showing you where you&#8217;re gonna ultimately save that money increase productivity, increase visibility, you know. Ticket deflection. Mttr.<\/p>\n<p>271<br \/>\n00:40:55.370 &#8211;&gt; 00:40:59.510<br \/>\nEddie McDonald: All of this value. Without a doubt its service.<\/p>\n<p>272<br \/>\n00:40:59.510 &#8211;&gt; 00:41:20.550<br \/>\nEddie McDonald: It might not look cheap on paper, but when you look at the value of what you&#8217;re buying, 100% is cheap, I&#8217;m very passionate about that, because that is that is something that&#8217;s come up over the years is too expensive. No, is because the people, the consultants have gotten lazy, explaining where the value of the platform is.<\/p>\n<p>273<br \/>\n00:41:20.550 &#8211;&gt; 00:41:27.550<br \/>\nFred Reynolds: But to Eddie&#8217;s point. If you could spend $50,000 to to create some automation or to help<\/p>\n<p>274<br \/>\n00:41:28.150 &#8211;&gt; 00:41:31.579<br \/>\nFred Reynolds: a automated process to help solve Mttr.<\/p>\n<p>275<br \/>\n00:41:31.920 &#8211;&gt; 00:41:44.829<br \/>\nFred Reynolds: you know, and you put that up against the number of hours spent by the people like Eddie&#8217;s Point. People are expensive, I guarantee, would justify itself tenfold, because once you put a solution in place that can solve for that, that&#8217;s a lifetime of that process.<\/p>\n<p>276<br \/>\n00:41:44.830 &#8211;&gt; 00:41:59.260<br \/>\nEddie McDonald: Yeah, there, there&#8217;s a reason why 88% of fortune, 500 companies or service now users, you don&#8217;t think they do their due diligence, and they spend 7 8 digits on the platform licenses. So it&#8217;s 100%. The values there. Yup.<\/p>\n<p>277<br \/>\n00:41:59.940 &#8211;&gt; 00:42:01.530<br \/>\nAndy Whiteside: I knew I could get Fred to go again.<\/p>\n<p>278<br \/>\n00:42:04.140 &#8211;&gt; 00:42:07.820<br \/>\nAndy Whiteside: Mike. Mike, you&#8217;re and only your final thoughts.<\/p>\n<p>279<br \/>\n00:42:12.240 &#8211;&gt; 00:42:22.020<br \/>\nMike Sabia: I I think that Mtdr. Is a fantastic metric. There are other kpis that come into place if you&#8217;re doing implementation.<\/p>\n<p>280<br \/>\n00:42:22.110 &#8211;&gt; 00:42:35.480<br \/>\nMike Sabia: you know. Yes, Mtr. Might be one of the things you&#8217;re trying to address. But there might be other kpis that you want to look at, and if we come and do an implementation for you as a customer, we will be discussing those as well.<\/p>\n<p>281<br \/>\n00:42:36.490 &#8211;&gt; 00:42:41.409<br \/>\nAndy Whiteside: I like the In Ttr conversation, just because it&#8217;s gonna it&#8217;s gonna impact user perception and<\/p>\n<p>282<br \/>\n00:42:41.610 &#8211;&gt; 00:42:43.989<br \/>\nAndy Whiteside: user perception is just massively important.<\/p>\n<p>283<br \/>\n00:42:45.820 &#8211;&gt; 00:42:48.690<br \/>\nAndy Whiteside: Gentlemen, thank you, and we&#8217;ll do it again in 2 weeks.<\/p>\n<p>284<br \/>\n00:42:48.690 &#8211;&gt; 00:42:52.423<br \/>\nEddie McDonald: You know I had like 4 more jokes keyed up. Just so, you know.<\/p>\n<p>285<br \/>\n00:42:53.620 &#8211;&gt; 00:42:56.625<br \/>\nFred Reynolds: And for our podcast we&#8217;re starting on Eddie&#8217;s life<\/p>\n<p>286<br \/>\n00:42:57.450 &#8211;&gt; 00:42:58.670<br \/>\nFred Reynolds: every other week.<\/p>\n<p>287<br \/>\n00:42:58.670 &#8211;&gt; 00:43:00.789<br \/>\nAndy Whiteside: We&#8217;ll put that in the outtakes or next week.<\/p>\n<p>288<br \/>\n00:43:01.830 &#8211;&gt; 00:43:04.300<br \/>\nFred Reynolds: Alright! Thanks everybody. Thanks, John.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant. Year after year, Enterprise Management Associates (EMA) research consistently ranks reducing the frequency, &hellip;<\/p>","protected":false},"author":7,"featured_media":65795,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_price":"","_stock":"","_tribe_ticket_header":"","_tribe_default_ticket_provider":"","_tribe_ticket_capacity":"0","_ticket_start_date":"","_ticket_end_date":"","_tribe_ticket_show_description":"","_tribe_ticket_show_not_going":false,"_tribe_ticket_use_global_stock":"","_tribe_ticket_global_stock_level":"","_global_stock_mode":"","_global_stock_cap":"","_tribe_rsvp_for_event":"","_tribe_ticket_going_count":"","_tribe_ticket_not_going_count":"","_tribe_tickets_list":"[]","_tribe_ticket_has_attendee_info_fields":false,"footnotes":""},"categories":[5],"tags":[186],"class_list":["post-528647","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-podcast","tag-applications"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.3 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>39: Syncing with ServiceNow: How to reduce MTTR<\/title>\n<meta name=\"description\" content=\"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/xentegra.com\/fr\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/\" \/>\n<meta property=\"og:locale\" content=\"fr_CA\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"39: Syncing with ServiceNow: How to reduce MTTR\" \/>\n<meta property=\"og:description\" content=\"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/xentegra.com\/fr\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/\" \/>\n<meta property=\"og:site_name\" content=\"XenTegra\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/XenTegra\/\" \/>\n<meta property=\"article:published_time\" content=\"2024-09-12T17:30:51+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-01-29T19:51:45+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1100\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Chase Newmyer\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@xentegra\" \/>\n<meta name=\"twitter:site\" content=\"@xentegra\" \/>\n<meta name=\"twitter:label1\" content=\"\u00c9crit par\" \/>\n\t<meta name=\"twitter:data1\" content=\"Chase Newmyer\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimation du temps de lecture\" \/>\n\t<meta name=\"twitter:data2\" content=\"44 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/\"},\"author\":{\"name\":\"Chase Newmyer\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/#\\\/schema\\\/person\\\/84736408f096bfd92b80305aea8846a7\"},\"headline\":\"39: Syncing with ServiceNow: How to reduce MTTR by helping people get out of their own way\",\"datePublished\":\"2024-09-12T17:30:51+00:00\",\"dateModified\":\"2026-01-29T19:51:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/\"},\"wordCount\":9845,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2024\\\/03\\\/Sycning-with-ServiceNow.png\",\"keywords\":[\"Applications\"],\"articleSection\":[\"Podcast\"],\"inLanguage\":\"fr-CA\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/\",\"url\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/\",\"name\":\"39: Syncing with ServiceNow: How to reduce MTTR\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2024\\\/03\\\/Sycning-with-ServiceNow.png\",\"datePublished\":\"2024-09-12T17:30:51+00:00\",\"dateModified\":\"2026-01-29T19:51:45+00:00\",\"description\":\"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#breadcrumb\"},\"inLanguage\":\"fr-CA\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-CA\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#primaryimage\",\"url\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2024\\\/03\\\/Sycning-with-ServiceNow.png\",\"contentUrl\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2024\\\/03\\\/Sycning-with-ServiceNow.png\",\"width\":1100,\"height\":600},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/resources\\\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/xentegra.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"39: Syncing with ServiceNow: How to reduce MTTR by helping people get out of their own way\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/#website\",\"url\":\"https:\\\/\\\/xentegra.com\\\/\",\"name\":\"XenTegra\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/xentegra.com\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-CA\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/#organization\",\"name\":\"XenTegra\",\"url\":\"https:\\\/\\\/xentegra.com\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-CA\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/1519903807641-min.jpg\",\"contentUrl\":\"https:\\\/\\\/xentegra.com\\\/wp-content\\\/uploads\\\/2023\\\/06\\\/1519903807641-min.jpg\",\"width\":200,\"height\":200,\"caption\":\"XenTegra\"},\"image\":{\"@id\":\"https:\\\/\\\/xentegra.com\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/XenTegra\\\/\",\"https:\\\/\\\/x.com\\\/xentegra\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/xentegra-llc\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/xentegra.com\\\/#\\\/schema\\\/person\\\/84736408f096bfd92b80305aea8846a7\",\"name\":\"Chase Newmyer\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-CA\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g\",\"caption\":\"Chase Newmyer\"},\"url\":\"https:\\\/\\\/xentegra.com\\\/fr\\\/resources\\\/author\\\/chasenewmyer\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"39: Syncing with ServiceNow: How to reduce MTTR","description":"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/xentegra.com\/fr\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/","og_locale":"fr_CA","og_type":"article","og_title":"39: Syncing with ServiceNow: How to reduce MTTR","og_description":"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.","og_url":"https:\/\/xentegra.com\/fr\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/","og_site_name":"XenTegra","article_publisher":"https:\/\/www.facebook.com\/XenTegra\/","article_published_time":"2024-09-12T17:30:51+00:00","article_modified_time":"2026-01-29T19:51:45+00:00","og_image":[{"width":1100,"height":600,"url":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png","type":"image\/png"}],"author":"Chase Newmyer","twitter_card":"summary_large_image","twitter_creator":"@xentegra","twitter_site":"@xentegra","twitter_misc":{"\u00c9crit par":"Chase Newmyer","Estimation du temps de lecture":"44 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#article","isPartOf":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/"},"author":{"name":"Chase Newmyer","@id":"https:\/\/xentegra.com\/#\/schema\/person\/84736408f096bfd92b80305aea8846a7"},"headline":"39: Syncing with ServiceNow: How to reduce MTTR by helping people get out of their own way","datePublished":"2024-09-12T17:30:51+00:00","dateModified":"2026-01-29T19:51:45+00:00","mainEntityOfPage":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/"},"wordCount":9845,"commentCount":0,"publisher":{"@id":"https:\/\/xentegra.com\/#organization"},"image":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#primaryimage"},"thumbnailUrl":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png","keywords":["Applications"],"articleSection":["Podcast"],"inLanguage":"fr-CA","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/","url":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/","name":"39: Syncing with ServiceNow: How to reduce MTTR","isPartOf":{"@id":"https:\/\/xentegra.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#primaryimage"},"image":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#primaryimage"},"thumbnailUrl":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png","datePublished":"2024-09-12T17:30:51+00:00","dateModified":"2026-01-29T19:51:45+00:00","description":"IT experiences regular waves of innovation, most recently with generative AI. Meanwhile, IT\u2019s core imperatives remain constant.","breadcrumb":{"@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#breadcrumb"},"inLanguage":"fr-CA","potentialAction":[{"@type":"ReadAction","target":["https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/"]}]},{"@type":"ImageObject","inLanguage":"fr-CA","@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#primaryimage","url":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png","contentUrl":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2024\/03\/Sycning-with-ServiceNow.png","width":1100,"height":600},{"@type":"BreadcrumbList","@id":"https:\/\/xentegra.com\/resources\/39-syncing-with-servicenow-how-to-reduce-mttr-by-helping-people-get-out-of-their-own-way\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/xentegra.com\/"},{"@type":"ListItem","position":2,"name":"39: Syncing with ServiceNow: How to reduce MTTR by helping people get out of their own way"}]},{"@type":"WebSite","@id":"https:\/\/xentegra.com\/#website","url":"https:\/\/xentegra.com\/","name":"XenTegra","description":"","publisher":{"@id":"https:\/\/xentegra.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/xentegra.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-CA"},{"@type":"Organization","@id":"https:\/\/xentegra.com\/#organization","name":"XenTegra","url":"https:\/\/xentegra.com\/","logo":{"@type":"ImageObject","inLanguage":"fr-CA","@id":"https:\/\/xentegra.com\/#\/schema\/logo\/image\/","url":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2023\/06\/1519903807641-min.jpg","contentUrl":"https:\/\/eadn-wc05-13529174.nxedge.io\/wp-content\/uploads\/2023\/06\/1519903807641-min.jpg","width":200,"height":200,"caption":"XenTegra"},"image":{"@id":"https:\/\/xentegra.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/XenTegra\/","https:\/\/x.com\/xentegra","https:\/\/www.linkedin.com\/company\/xentegra-llc"]},{"@type":"Person","@id":"https:\/\/xentegra.com\/#\/schema\/person\/84736408f096bfd92b80305aea8846a7","name":"Chase Newmyer","image":{"@type":"ImageObject","inLanguage":"fr-CA","@id":"https:\/\/secure.gravatar.com\/avatar\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/d46cd44f0bd433dc5a386cbac549c62fd92266e3951669c705b347be2130cca3?s=96&d=mm&r=g","caption":"Chase Newmyer"},"url":"https:\/\/xentegra.com\/fr\/resources\/author\/chasenewmyer\/"}]}},"_links":{"self":[{"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/posts\/528647","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/comments?post=528647"}],"version-history":[{"count":555,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/posts\/528647\/revisions"}],"predecessor-version":[{"id":717557,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/posts\/528647\/revisions\/717557"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/media\/65795"}],"wp:attachment":[{"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/media?parent=528647"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/categories?post=528647"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xentegra.com\/fr\/wp-json\/wp\/v2\/tags?post=528647"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}