Karma day : Savoring our design mistakes

As seen on Column Two (a very influential blog on me lately) and follows some trends of karma I saw today.
Savoring our design mistakes

Jared Spool discusses what to do when design mistakes are made, starting with a first post and then a followup. To quote:

Assuming the developer had the best of intentions (and why *shouldn't* we assume that? --- after all *we* do, don’t we?), the developer who produces a non-optimal user experience has actually done the team a favor by making obvious an important design requirement. Every time a team member bumps into a boundary of what good experience should be, we learn something we didn't know before.

I think this is a much more mature approach than another notable guru, who called these types of design mistakes "lazy, stupid and evil". At the end of the day, it's about building bridges and working well with others, and not about taking the high ground or demonising others...