"Ego-less" Reviews

Some software development texts praise "Egoless Reviews" and "Egoless Development". Here is the usual explanation:

• people often defend their positions, even when they realize they're wrong
• they think admitting an error would reflect poorly on them
• so, a product-review, should focus on the product, not on the producer (the person's review is a separate process)
• in summary, product reviews should be "ego-less"

There's an element of truth to the first three points. Product reviews are about the product, and are more effective if everyone is focused on that, and not on the producer. This means that the reviewer and the producer understand that mistakes might have been made, and that mistakes are the norm, and that's why the review is being held in the first place. The review should be guilt-free.

Of course, to term this "egoless" is wrong. Only someone who is self-confident (i.e., has strong ego) is willing to admit a mistake, knowing that it only goes so far. A mistake does not threaten his self in its essence.