Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
· Home
· Content
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account


The five ITIL books can be obtained directly from the publisher's website:

Or as downloadable PDFs: HERE

Current Membership

Latest: MandyNeal
New Today: 25
New Yesterday: 31
Overall: 234809

People Online:
Visitors: 146
Members: 1
Total: 147 .



Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement

How to set up
IT Change Management
Process Info-Graphic

NOTE: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


Select Interface Language:

Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Proactive Problem Management Implementation
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Proactive Problem Management Implementation

Post new topic   Reply to topic    ITIL Forum Index -> Problem Management
View previous topic :: View next topic  
Author Message

Joined: Jul 25, 2012
Posts: 1

PostPosted: Wed Jul 25, 2012 9:46 pm    Post subject: Proactive Problem Management Implementation Reply with quote

Hi. Our company has a pretty good foundation and process in place for Reactive Problem Management so I have been asked to help move organizations along with more Proactive Problem Management.

Has anyone been involved with this before and possibly already have a project plan or training presentations that they'd be willing to share that I can possibly tweak for my needs. This would be very helpful to me so I am structured and think about all the steps.

I'm trying to not be tool focused since I'm with a big company and it won't be possible that everyone can use the same toolsets so I was hoping for something more around the basic Proactive PM activities like trending analysis, compliance metrics, etc.

Thanks in advance for any info. I'm sure I missed a lot of details because I was anxious to get this request out there.
Back to top
View user's profile
Senior Itiler

Joined: Mar 04, 2008
Posts: 1894
Location: Helensburgh

PostPosted: Thu Jul 26, 2012 4:24 am    Post subject: Reply with quote

It's good not to be "tool focussed" for problem management in all circumstances. Pro-active problem management is about having a strategy to focus on service components and infrastructure in alignment with the business' use (and intended future use) of the services, in order to anticipate what might be detrimental to the services in the future.

In fact, don't even think about tools until you have established policies and objectives.
"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
Back to top
View user's profile Send e-mail

Joined: Aug 03, 2012
Posts: 24

PostPosted: Sat Aug 04, 2012 3:42 am    Post subject: Reply with quote

Is the questions related to which metrics to measure to identify the best use of your resources towards resolving the problems proactively, so that you can create the process and procedures to foster the identification of the specific areas to focus your resources?

My thought is if you are doing problem management correctly, your reactive problem management should already have the ability to proactively identifying your problems.

You are reviewing your incidents on a regular basis, correct? Do you review the previous day incidents? A weekly roll-up discussion and trending with the Incident Manager and respective Program Managers?

Back to top
View user's profile

Joined: May 22, 2014
Posts: 9

PostPosted: Mon May 26, 2014 4:32 pm    Post subject: Reply with quote

This is sounding quite good basically this is how it grows and i believe that taking it to another level is how the moment works.
What you have highlighted is something that works for that particular time period and that is how it has to be which is fine enough to understand.
Back to top
View user's profile

Joined: Apr 28, 2014
Posts: 27

PostPosted: Tue Jun 24, 2014 5:53 pm    Post subject: Reply with quote

Proactive probelm management. Hmm something of a descriptional oxymoron.

But having done thing at enterprise scale I can advise what it looked like for us.

The goal is basically to spot trends and patterns within complex systems and use them to take preventative actions before the incidents / problem occur.
We plotted out our P1 problems (created from P1 incidents) on a linear graph and used root cause codes to identify them individually. Then we performed some simple analysis of the data.

This sounds simple but the more complex the systems you support the more complex that analysis becomes.
We had reasonable success with this and measured by service we were able to reduce like for like P1 incidents.
Back to top
View user's profile

Joined: Sep 22, 2014
Posts: 1
Location: United States

PostPosted: Tue Sep 23, 2014 4:52 pm    Post subject: Reply with quote

Problem management has proved to be an elusive process which is not easy to implement. One reason for this is that the process can be understood in different ways. One solution is to have problem management solving all difficult cases but this may well lead to the situation where the problem management team is actually just the second level of the service desk.

A different solution is to concentrate on the proactive approach or risk management. Aale Roos will explain how this works and what the logic in this approach is.
Back to top
View user's profile Visit poster's website

Joined: Dec 16, 2014
Posts: 10

PostPosted: Wed Dec 17, 2014 12:55 pm    Post subject: Proactive problem management, hmmm.. oxymoron indeed. Reply with quote

The question comes down to 'why implement proactive problem management'? e.g. what is the outcome the person who asked you to do this wants?

My guess is that they're ultimately hoping to further decrease incident levels (or at a business level decrease costs or increase customer sat).

If this is the case, and you should confirm the true expected outcome - not just what they asked you to do, then step 1 when we go into a business is to look at their problem model. We see two problem models on a regular basis:

1: Problem management as a function, and 2: Problem management as a process.

Problem management as a function:
This is where the business creates a 'team' or 'role' and calls that person a 'Problem Manager' or a 'Problem analyst'. This is great for reactive problem management with regards to managing RCA for P1 incidents. It means that the person can focus on RCA for the big issues within the environment, but terrible for RCA around repeat incidents within Service Operations (this is what people generally refer to proactive problem management - e.g. identifying trends from repeat incidents).

If you are using this model you should look at expanding your Problem "function" to be a Problem "process" and include all "incident managers" within the process.

Problem management as a process:
This is where the team leaders / managers of the functions (e.g. Service Desk, technical support, application support) take off their 'Incident management' hat and put on their 'Problem Management' hat from time to time. This ultimately puts responsibility AND accountability into the hands of the people with the power over their staff to direct their focus each day.

What this basically means is that the people who are dealing with Incidents on a day to day basis, now also have another thought when they resolve an incident or identify a potential incident, that thought being "Should I raise a problem" or probably closer to "is this likely to reoccur".

If the true outcome from an operational level is a decrease in incident levels then this is the way to go.

This way you can develop a 'standard operating procedure' for managing 'minor problems' that can be (and should be) dealt with by the resolver group. This also puts the accountability of reducing incident levels (and provides incentive to the managers) to deliver the expected outcomes of Problem Management.

Taking the 'problem as a process' approach delivers a much better return for the business. My only caution is that when taking this approach, it is best to do so with a reasonably mature Problem Process in place.
Back to top
View user's profile
Senior Itiler

Joined: Jun 05, 2015
Posts: 59
Location: Hyderabad ,India

PostPosted: Sat Jun 06, 2015 4:00 pm    Post subject: Reply with quote

Keep Analyzing the facts for previous months years ,check the incident trend .You will automatically move from Reactive to Proactive . I see nice replied on top of mine as well .I hope you already got answer to your question

All the very Best
Back to top
View user's profile Send e-mail
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management All times are GMT + 10 Hours
Page 1 of 1

Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003

Forums ©


Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.