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: ejek15
New Today: 2
New Yesterday: 42
Overall: 231616

People Online:
Visitors: 125
Members: 1
Total: 126 .



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 - Securing knowledge transfer
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Securing knowledge transfer

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

Joined: Oct 24, 2006
Posts: 7

PostPosted: Wed Oct 25, 2006 7:35 pm    Post subject: Securing knowledge transfer Reply with quote

Hi everybody!

In Incident and Problem Management work arounds are developed by support groups and SHOULD - according to ITIL - be made available to SD staff. When incidents occur, the SD staff searches the knowledge DB for work arounds, finds the work around and solves the incident.

Now let's suppose we have people that don't like writing detailed solutions on how to fix an incident. When an incident is assigned to them, they just solve it and write "It works again" in the incident record.

How do you make people write better descriptions on how they solved their incidents and what steps other people have to take in order to do the same??

Thanks in advance for your advice!

Back to top
View user's profile
Senior Itiler

Joined: Sep 21, 2006
Posts: 63
Location: USA

PostPosted: Wed Oct 25, 2006 10:18 pm    Post subject: Reply with quote

First, approach the support groups as a whole and emphasize and explain the importance of complete, accurate, and understandable tickets. Make clear what your expectations are regarding the tickets. What things should be addressed? What level of detail is required? And most of all: why should we do this? (answer: to support collaboration, reuse of knowledge, and for accountability) Also, show them examples of good and bad tickets.

Then monitor your tickets for a while. Take samples. Based on your findings, approach individuals who are still doing a lousy job. Explain the whole thing to them again. Let them see what it would mean to them if they were looking for a solution and only find tickets that say 'issue fixed'.

Continue to monitor ticket quality and bring it up in job evaluations with the individual employees. Both to praise the good folks, as well as to identify the people who are still underperforming. For the latter, make sure to make clear that ticket creation will be an item for their next job evaluation as well. That way they know they're being 'watched'.
Back to top
View user's profile

Joined: Oct 24, 2006
Posts: 7

PostPosted: Thu Oct 26, 2006 12:37 am    Post subject: Reply with quote

Hi Marcel,

thanks a lot for your reply. It helps a lot!

Back to top
View user's profile
Senior Itiler

Joined: Mar 15, 2006
Posts: 68
Location: Thailand

PostPosted: Thu Oct 26, 2006 5:10 pm    Post subject: Reply with quote


Also please consider there would be few incidents for which the Technical Support would have provided workaround/solutions earlier. In these cases it would be of help if there is a way for your SD to relate the incident tickets with one another.

I completely agree with Marcel's solution.

This is what we are doing in our organisation and results are starting to show up..


Back to top
View user's profile

Joined: Oct 07, 2006
Posts: 5

PostPosted: Sat Oct 28, 2006 3:02 am    Post subject: Reply with quote


During our implementation of Incident & Problem mgmt in my organization, we do experience similar issue with some analyst/engineer not providing sufficient information about their finding. As a result we've introduce Kepner Tregoe methodology to all our analyst/engineer and also design a set of question that they need to answer before opening/closing the incident/problem ticket. This will help to keep value information during the root cause analyst and also provide a clear understand the root cause/solution before closing the incident/problem ticket. Hope this help you with your ITIL implementation.
Back to top
View user's profile

Joined: Sep 27, 2006
Posts: 29

PostPosted: Mon Oct 30, 2006 7:57 pm    Post subject: Reply with quote

Hi Burki,

During our implementation of Incident Management, we faced a similar issue with the team members. Hence, we brought out a quality check into picture which covers every aspect - for example: documentation, priority, frequency of updating tickets, resolution, etc..

We also used to conduct weekly meetings to discuss the process violations happening.

There was a good amount of resistance from the people initially, but with proper training and making the team understand the inmportance and value of this objective - we finally achieved what we were looking for.

Hope this helps.

"Look at Frustration as a positive thing. It is the frustration that drives you to improve"
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.