Pain Value Analysis & Problem Analysis

I'm learning Service Operations in ITIL. I encountered some really interesting ideas about problems and pain in IT, and wanted to share them. 

"...instead of just analyzing the number of incidents/problems of a particular type in a particular period, a more in-depth analysis is done to determine exactly what level of pain has been caused to the organization / business by these incidents / problems. A formula can be devised to calculate this pain level, typically, this might include taking into account the number of people of effected, the duration of the problem, and the cost to the business (ITIL Service Operation manual page 100)". 

I'm also learning how to best analyze how and why problems occur - and some tools for getting to the very root of a problem. The technique you use depends on the specific problem you have, but here's the list I'm learning: 

1. Kepler and Tregoe analysis 
2. Brainstorming 
3. 5-why's 
4. Fault isolation 
5. Affinity mapping 
6. Hypothesis testing 
7. Technical observation post 
8. Ishikawa diagram 
9. Pareto analysis 
10. Chronological analysis 

One of the reasons I so value these ITIL courses is because many of the problems we face in school IT have already been well-addressed and solved by other industries. I remain even more committed that learning and adopting ITIL and best-practices for managing IT in schools is the right way to go.