How about a similar thing on the source-code control side?
A test coverage tool will mutate your codebase, e.g. changing a '<' operator into a '<='. It does this in order to check that one (and ideally just one) test fails as a result.
To this conventional mix, add the idea that if we find a code mutation which does not cause any tests to fail, then the mutated code is automatically committed back into our repo.
This script should be runs over production code unpredictably, several times per week.
It will teach your development team to write thorough tests, with great coverage! Or else!!!

Late last year, the Netflix Tech Blog wrote about five lessons they learned moving to Amazon Web Services. AWS is, of course, the preeminent provider of so-called "cloud computing", so this can essentially be read as key advice for any website considering a move to the cloud. And it's great ad...