Skip to main content

Common incident management issues

The following post on the Security Procedure blog lists some common incident management issues. Incident management is a fundamental ITIL process.
Common incident management issues include:
  1. Extended resolution times
  2. Inconsistent service delivery/approach to resolution
  3. Incomplete fixes/Incidents needing to be re-opened
  4. Too many touch points required to resolve an issue
  5. Inefficient trouble shooting procedures
  6. Poor visibility of impact of incidents upon the business
  7. Routing errors/Multiple re-assignments
  8. Inappropriate prioritization of incidents
  9. Inefficient workload management
  10. Poor communication of outages and their impact
  11. Lack of a closed loop process i.e. no formal closure
  12. Continuously re-inventing the wheel
  13. Ineffective use of knowledge repositories
  14. Poor categorisation/classification of incidents
  15. Buck passing between functional/implementation groups
  16. Lack of visibility of incident status
  17. Temporary workarounds being left in place as permanent fixes
  18. Unnecessarily high levels of follow up/chase calls
  19. Availability of Help Desk staff
  20. Skill levels of Help Desk staff
  21. Single incident management process irrespective of nature and scope of incident e.g. Critical service impacting incidents treated in the same way as a user that has forgotten their password.
This list is from Rob Addy book’s Effective IT Service Management. The Major Incident Process described in this blog tries to address many of these issues, and is linked to problem management for quality.


Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi