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

Current Membership

Latest: MichalVar
New Today: 53
New Yesterday: 88
Overall: 139954

People Online:
Visitors: 65
Members: 2
Total: 67 .

Languages
Select Interface Language:


Major ITIL Portals
For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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.


The Itil Community Forum: Forums

ITIL :: View topic - ITIL - Defaulting Urgency/Impact in User Interface
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

ITIL - Defaulting Urgency/Impact in User Interface

 
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk
View previous topic :: View next topic  
Author Message
Aluria
Newbie
Newbie


Joined: Apr 24, 2007
Posts: 1

PostPosted: Wed May 14, 2008 9:13 pm    Post subject: ITIL - Defaulting Urgency/Impact in User Interface Reply with quote

I am not sure if this is the correct forum for this question, but my group has been asked to change our Tool, CA Service desk, to always default both urgency and Impact to a specific option (in this case 5 - the lowest). This is because users complain they don't want to have to remember to set those 2 fields and we make them required (we drive priority by Urgency/Impact).

My question is this the right thing to do. I beleive it isn't as it wouldn't force users to tell the support group the correct Urgency / Impact, and often times it would end up with the tickets being reset later in the process.

Any giudance is appreciated. Thanks.
Back to top
View user's profile
rickyticky
Newbie
Newbie


Joined: Feb 28, 2007
Posts: 4

PostPosted: Wed May 14, 2008 9:32 pm    Post subject: Re: ITIL - Defaulting Urgency/Impact in User Interface Reply with quote

We take the same approach for our Self Service(SS) ticketing. However, we tell them up front that the Self Service tickets are for low priority events. Also, that does not mean that your Service Desk team can't review the SS tickets and raise the priority where needed.
Back to top
View user's profile
UrgentJensen
Senior Itiler


Joined: Feb 23, 2005
Posts: 458
Location: London

PostPosted: Wed May 14, 2008 10:46 pm    Post subject: Reply with quote

Hi Aluria,

I tend to agree with RT. I have never given customers the ability to choose priority for themselves. In fact I'd go so far as to say it defeats the purpose of service management because you're taking away it's ability control demand and supply to IT.

Cheers,

UJ
_________________
Did I just say that out loud?

(Beige badge)
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Wed May 14, 2008 11:52 pm    Post subject: Reply with quote

Hi,

Users are being asked to to state urgency and impact from which will be derived priority, and they ought to where they can it is as much part of there job as reporting the incident.

Now sometimes these cannot be realistically be determined at the point of incident because the reported incident is a symptom of something bigger. When this happens, the service desk or support may (or may not - it all depends) be able to see the implications right away. That is why you need flexibility to update the information and recalibrate the incident.

Sometimes the user will (inadvertently or otherwise) exaggerate the urgency or impact. Again recalibration required.

The whole prioritization should be underpinned by customer requirement and evaluation of worth and this can include the customer asserting the capability - or otherwise - of users to inform on priority.

The practical point of the question is whether setting defaults will lead to better (and quicker) correct prioritization of incidents. I would suggest that the answer is very organization dependent and also largely affected by the type of services involved and the skill set of the users who might report incidents.

Forcing users to fill in these two fields will help if the users have a reasonable understanding of the implications, but not if they will just be guessing. One possibility is to provide a "don't know" value and to treat such entries to rapid evaluation by the service desk.

Of course much depends on users understanding that better information leads to quicker restoration of service.
_________________
"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
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> The ITIL Service Desk 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 http://www.nukecops.com

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.