I'm trying to emphasise the focus on quality in the article. If you're fearful of breaking it this is not good. We need to be confident that we can make changes without screwing it up.

Too many people create poor first attempts and leave it at that (the example I used was a process which breaks once per month, indicating there is room for improvement that would save Fred time), claiming later "if it ain't broke". I think this is a recipe for disaster because it reflects an attitude that lacks a desire to improve.

However, there are times when it "ain't broken" and it is good enough, and in those situations I agree with other comments that you wouldn't want people wasting time looking to make micro-optimisations. Ultimately I am making the point that people need to have the right attitude toward improvement and quality overall.