Repeat Problems

[Liono]

Has anyone ensured a formal process of identifying, communicating and resolving ‘known and repeat problems?

[Mark-OLoughlin]

Hi,

that should be part of your problem management process!!

Any reason why you focus on "known and repeat problems"

Key thing is information and being able to first of all report on what are your known problems so you can do something about them and also the ability to trend problems to see what are the repeat problems and using RCA to determine what can be done to resolve them.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant

[Diarmid]

Hi,

strictly speaking you should not get repeat problems. That would mean that you thought you had resolved a problem (fully tested kind of "thought") and then discovered there were more incidents to resolve. This is a breakdown in your problem management process.

What you will expect is repeat incidents related to a problem which has not yet been resolved. This is where "known problems" (or known errors) comes into play. If this is what you meant, then Problem Management is the process by which repeat incidents (among other things) are tackled to resolution.

If in fact you want to do something about repeat problems then you need to review your problem management process(es). Process review or process improvement, would the formal process for doing this.
_________________
"Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718

[Mark-OLoughlin]

Hi,

from experience I have seen repeat problems. Issie is generally down to the resolution to fix the problem didn't actually fix the problem and hence the repeat problem.

Repeat incidents are generally what you get though.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant