Quality or Quantity?

Here is a widely told joke in the computer industry that goes like this: 

A man is flying in a small airplane and is lost in the clouds. He descends until he spots an office building and yells to a man in an open window, “Where am I?”

The man replies, “You are in an airplane about 100 feet above the ground.” The pilot immediately turns to the proper course, spots the airport, and lands. His astonished passenger asks how the pilot figured out which way to go. The pilot replies, “The answer the man gave me was completely correct and factual, yet it was no help whatsoever, so I knew immediately he was a software engineer who worked for Microsoft, and I know where Microsoft’s building is in relation to the airport.”

As long as information is in-formation (i.e. half-baked) it is to be considered as misleading piece of THIS (you may rearrange this) 

Besides just figures (such as Pass Fail Ratio aka ‘facts’), it is the job of the QAE to ensure the severity of the mathematics which is going to be ignored (i.e. fail ratio). It is not ‘how many’ failed it is - always – ‘which’ failed.

Understand of severity is synonymous with, yes, experience. And experience is the result of misunderstanding. Multiple times.

For QAE (Quality Assurance Engineers), focus ought to be quality and not quantity.