Hey Jo.. Many congratulations on being one of the gifted teachers who explain complicated things like this in the most interesting and amusing ways... Love your work... Subscribed
incidents are something that unexpectedly happened that involves temporary interruption that requires attention in order to restore back to its functionality
Hi Pia, thanks for the comment. This is certainly true for a lot of incidents, however not all incidents are unexpected. If we look at the purpose of proactive problem management it is to pre-empt incidents, identifying possible single points of failure, and prevent them from happening in the future (dependent on the organisational direction / budget etc). If we think of the problem management technique of the technical observation post then the entire purpose is to wait for the incident to happen to facilitate identifying the cause. Se we know that the incident will happen in advance, we just don't know what pre-empts the incident at that point in time. Problem management and Availability management will actively identify points of failure (potential or active) and decisions are made as to whether to prevent the incident in the future. Often that decision is based on budget in which case the expectation is that the incident will occur in the future because it has not been prevented. Sometime the exact time and date of the incident is known.
Wow, this is the best explanation about the difference between Problem x Incident i've ever seen. Super Thanks!!
This session deserves billion views and Likes ....
This is the best explanation I have found. Thank you!
The best video to understand Incident vs Problem.
Your last video was uploaded b4 2 years.
Wish to see more.
TY
Wow, a FANTASTIC explanation! Thank you!
You are great...the way you expose is great!!
very creative explnation. LOVE YOUU
one of the best explanation !
You are brilliant 👏
A very clear explanation of the difference between an incident vs problem.
Elegant... From an IT perspective, I see this as useful for daily life.
Wao,thanks for explanation.
This was a very comprehensive explanation. Thank you so much!
Amazing... Simple and clear 😃
Thank you so much for this simple easy and lucid explanation of diff between an incident & problem !!
Thanks Jo for this wonderful piece of knowledge sharing. For me its like having ice-creame. Smooth, delighful and long lasting experience !!
Most beautiful Explanation... From a non IT perspective... Jaz simply loving it
Great lesson :) I've never thought I'd say this, but it's a pleasure to listen.
Thank you for this very ilustrative explanation!!!
I really like your video.
Amazing video
Great explanation
An incident can never be a problem but problems though cause incidents.
Thanks, great explanation and clarification for incidents vs. problem.
Brilliant. And subscribed.
Awesome example
Nicely Explain...
I loved your watch strap too !
Thanks ever so much! :-)
Thanks Jo...beautiful explaination
You are an awesome explainer
Great explanation! Well done. Thanks.
Thank you ... useful information
fullpower examples Jo
Hey Jo.. Many congratulations on being one of the gifted teachers who explain complicated things like this in the most interesting and amusing ways... Love your work... Subscribed
Hi Jo, one more question is, once a PRB is raised what should be the next steps?
Thank you very much! Great explanation.
great video!
very good explanation. Thank you very much :)
Thank you so much. This was very informative :)
Thanks, i have a clearer understanding now
Best explained
loved it
Thank you it is really clear
Thank you so much.
So true. We really don’t need to know -Why ☺️ Masterstroke.
We do sometimes obviously, just not all the time :-)
Could pls explain the same in terms of IT service desk management....I know the basics however wanted to understand more
So can we say finding the root cause of incidents is a problem management??
Yes, Raja, that's exactly right :-)
Dear Jo I’ve sent an email just to ask your advice regarding an issue in the work environment
What is means by coms
incidents are something that unexpectedly happened that involves temporary interruption that requires attention in order to restore back to its functionality
Hi Pia, thanks for the comment.
This is certainly true for a lot of incidents, however not all incidents are unexpected. If we look at the purpose of proactive problem management it is to pre-empt incidents, identifying possible single points of failure, and prevent them from happening in the future (dependent on the organisational direction / budget etc).
If we think of the problem management technique of the technical observation post then the entire purpose is to wait for the incident to happen to facilitate identifying the cause. Se we know that the incident will happen in advance, we just don't know what pre-empts the incident at that point in time.
Problem management and Availability management will actively identify points of failure (potential or active) and decisions are made as to whether to prevent the incident in the future. Often that decision is based on budget in which case the expectation is that the incident will occur in the future because it has not been prevented. Sometime the exact time and date of the incident is known.
Hii Jo why you look so angry