How important is it to get it right the first time?
In nature, species evolve over eons. It’s important to note that with changes gained there is always something lost. Nature often has a way of letting go of what is no longer necessary. That too, also takes a very long time. Everything around us is in the natural world is proof positive of a loosely coupled review, approve and verification process.
“The fossil record implies trial and error, the inability to anticipate the future, features inconsistent with a Great Designer (though not a Designer of a more remote and indirect temperament.)” ― Carl Sagan, Cosmos
Imagine, for a moment, what the dollar cost would be if one were to begin a program with the objective of creating homo sapiens starting with single-celled organisms? Carl Sagan had it right when he suggested a “… Designer of a more remote and indirect temperament.”
I have yet to meet a business partner, CFO, CEO, or a CIO with that kind of patience! In the software development world we strive to get it right the first time. Money is the usually the motivating factor that is used to start quality improvement programs. Expectations are then set to unachievable levels causing a failure to launch sustainable quality practices.
While it’s a certainty that the dollars saved from quality improvement initiatives should and will not be ignored, it is also important that money should not be the main focus. When it comes to problem solving, money is not the most compelling reason for changing the way things are. In fact, money often stagnates clear thinking, logical thought and creative processes of innovation and change. It often gets you temporary results that do not stand the test of time. To be really good at review, approve and verification you have to be really good at staying focused on innovation and change.
Note to leaders who just read that and thought, “Good to know, let’s start a new quality improvement organization with zero budget and or, resources, leave the rest of the organization well-funded and disinterested and see what we get!” A bad, if not silly (by which I mean, really silly) idea.
In my next few blogs I am going to discuss the known and hidden benefits derived as a result of following lean six sigma review, approve and verify series of workflows that you can build into your current SDLC process.
qualitasrebus 