now, our next step is going to be testing our theory to determine our cause. So we've gone ahead and we've established our theory of probable cause. And we've researched our theory and we've narrowed down what our problem might be the next we're going to test and see. This is exactly this is actually what the issue is.
So before we again test our theory to determine our cause,
we want to back up before we make any changes. So we're gonna back up settings and we want a backup files so we don't run into any issues or we don't run in to any data loss. Once our theory is confirmed, we may want to determine our next steps. So let's say we say Okay, well, I'm pretty sure that my theory are that
what's causing this issue is
ah, Bad Ram module. So
we implement our theory, we test our theory and we remove a ram module or we swap our ram modules around and we say, OK, so yes, this ram module is what's causing the problem. We've our theory has been proven correct. Or we may want to try installing a patch so up
windows isn't functioning properly. We're having some issues. So we say, Well, maybe I think it's this problem.
So we do a little bit of research or and we tried. When we disable this program, are we disable a service and then our issue has gone away. So we say, OK, this service is what's causing the issue. But I can't just leave this service off. This service needs to be functional, So maybe our next step is we need to install a patch or we may need to buy Ram.
So once our theory is confirmed, we don't just
your hands up in the air and congratulate ourselves and move on. No, our problem is not solved yet. We still need to keep going. Once our theory is confirmed, we need to move on. We need to determine our next steps so that we can implement those in our in our next steps.
So if our theory is not confirmed, this is raw meat where we may get a little bit discouraged. But
hey, at least we get to do some more detective work, right? A little bit of consolation. So if it's not confirmed, we need to go back and we need to establish a new theory. Uh, don't think of a incorrect theory as a failure. Just think of it as the term as ruling something out. We've
tested the theory. It didn't work. Well, hey, now we can rule this out. This is not the problem.
So we can move on to other things. We can research other solutions. So we go back to our establishing a theory step. Additionally, we may say if, for example, were on a help desk or four in a situation where we do need to escalate this up to the next level.
Say, we've tried everything in our toolkit. We've tried all of the possible solutions
that we can implement. All of our theories are not working, and we need to move this on. This is becoming an issue that's a little bit big, bigger than the state than our our current level. We may be at, like it's here, wanna tear to level, and we need to escalate this up because this looks like it may be a server issue or this
this person really needs to get some work done. So I need to push this up
then that's what escalation means Escalation is essentially just taking our issue. We can't figure it out. Our theories aren't working, so we're gonna bump it up to the next level of support.
again, testing our theory before we test any of our changes. Before we make any setting modifications we want to back up. And once our theory, if it is the correct theory for good, then we'll need to determine our next step in order to implement our plan. And then if the theory is not confirmed, if it's not in the correct theory
we need to establish a new theory or we need to escalate.