Comments on: IT Roles: Productivity and Availability https://smbitjournal.com/2011/02/it-roles-productivity-and-availability/ The Information Technology Resource for Small Business Sat, 18 Feb 2017 15:06:48 +0000 hourly 1 https://wordpress.org/?v=6.9.1 By: LGlasscock https://smbitjournal.com/2011/02/it-roles-productivity-and-availability/comment-page-1/#comment-1632 Tue, 24 Jul 2012 11:53:51 +0000 http://www.smbitjournal.com/?p=128#comment-1632 This is an article I wish managers would read. It made me understand my job a little better. I’ve been suffering from an overload of uncompleted tickets with constant interruptions, issues with actually “finishing” completely a task before being rushed on to the next and following-up on tasks, especially if waiting for information from the requesting party. It’s SAP for them when they input the request but it takes forever to get additional information from them. This gets so bad that it could be months before an issue is resolved. Of course, it often happens that the SAP issue is no longer required and the user can’t remember why they requested it in the first place.

My previous manager recently left and during the interim between when he left and the new one started I was able to reduce my ticket queue from 270 to 160 and now it’s down to 135 and that’s with working currently tickets at the same time.
The ticket mix was a combination of research issues, projects and software help desk items.

My previous manager thought it looked good to take tickets out of the unassigned queue and immediately assign them, even if this meant it could be a month before someone actually looked at it.

I don’t think this was the best way to manage the work or the IT personnel.

Combine this thread with the one titled “The less obvious IT acronym – ADD” that I read this morning and it really makes you think.

We only get a few minutes, if that, to actually concentrate on 1 issue before being redirected to the next issue regardless of whether or not the first one has been resolved. I used to be very good at handling multiple items at the same time but it’s deteriorated over the years.

I hate the IT Hunt line phone line since it always interrupts current concentration on an issue but then I don’t want users getting into the habit of calling me personally for everything little thing.

The paragraph in this article about the efficient management of the help desk “Having a never ending queue of support issues is exhausting for the support professionals and it also means that no amount of staff is ever in an �??idle�?� state awaiting high priority items. Because of this, high priority items are either not addressed as quickly as they should be or else in-process items are neglected.” hits home big-time. The last sentence applies to me and I don’t like it one bit.

Thanks for the post and I’m going to keep it to hand to my supervisor if/when the company starts getting on IT about the help desk issues.

]]>
By: Scott Alan Miller https://smbitjournal.com/2011/02/it-roles-productivity-and-availability/comment-page-1/#comment-868 Fri, 06 May 2011 17:19:37 +0000 http://www.smbitjournal.com/?p=128#comment-868 I think that you’ve missed the entire point of the article. First, there is no gripe, the point is to educate people as to two different types of IT roles. One is about availability, the second is about productivity. Many IT jobs are not about being available or reactive, only support jobs, but there are many, many engineering style IT jobs (the bulk of development, platform engineering, architecture, design, etc.) where availability is not important but productivity is.

The goal of this article is to help IT managers and business people understand the critical differences between these two types of workers and not mistake one for the other.

]]>
By: SMBSupport https://smbitjournal.com/2011/02/it-roles-productivity-and-availability/comment-page-1/#comment-846 Wed, 06 Apr 2011 13:30:45 +0000 http://www.smbitjournal.com/?p=128#comment-846 what is your gripe here?

if you have chosen IT services you need to be availalbe and reactive at all times and the pizza analogy is simply not suited for getting a fast efficient service

]]>