Grey problem

In IT, a grey problem (or, gray problem) is a problem where the causing technology is unknown or unconfirmed. Common grey problems are:

  • Intermittent errors;
  • Intermittent incorrect output, or;
  • Transient performance problems.

Because the causing technology is not clear, IT departments often find it difficult to allocate the problem to a Technical Support Team (platform team).

Background

Combining frequency and causing technology information can provide a view of the complexity of a problem and so indicate how difficult it will be to investigate (see Figure 1).

The problems in each quadrant have certain characteristics:

Quadrant 1
In a typical IT department 80 to 90% of problems are solid faults that are easily tracked down to a causing technology. The appropriate technical or platform support team efficiently deals with these problems every day.
Quadrant 2
Some recurring problems are due to a Known Error, or are obviously being caused by a particular hardware or software component. These problems are handled by technical support people working with suppliers.
Quadrant 3
Every so often a one-off problem occurs, and the cause of these may never be found.
Quadrant 4
The technical ownership of these issues is unclear and so they are referred to as “grey problems” i.e. not black and white.

Impact

Grey problems have a significant impact on IT service, and:

  • Form the bulk of ongoing recurring problems
  • Create a disproportionately high IT support workload
  • Give a pointer to more serious problems to come
  • Cause the business to adjust practices around the problem

ITIL perspective

ITIL Service Operations implies that grey problems should be handled through a Problem Solving Group under the direction of the Problem Management function. In practice, even those IT organisations that have adopted ITIL rarely have a procedure to handle a grey problem, leaving it to bounce between Technical Support Teams as each denies that their technology is to blame.

See also

Further reading

  • Offord, Paul (2011). RPR: A Problem Diagnosis Method for IT Professionals. Advance Seven Limited. ISBN 978-1-4478-4443-3.
  • Grey problem case study
  • Presentation to the British Computer Society

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.