Proactive improvement Yea, we think that proactive is good Fig. 6 C Don Clausing 1998
Proactive improvement Yea, we think that proactive is good! Fig. 6 © Don Clausing 1998
What is wrong here? Concept> design> Read Produce FRT ceehneloay stream C Don Clausing 1998
What is wrong here? Technology Stream Concept Design Ready Produce FRT Fig. 7 © Don Clausing 1998
Rework -how much is enough? R Design Complete 8. Producti n Buld/estFⅸ Buld/estFⅸ Build/est/FⅸX Produce Build/Test/Fix Fig. 8 C Don Clausing 1998
Rework – how much is enough? Design Complete Ready for Production Produce Build/Test/Fix Build/Test/Fix Build/Test/Fix Build/Test/Fix Fig. 8 © Don Clausing 1998
Build/test/fix-why Reactive problem solving Too little- limited scope of solutions Too late Design contains many unsolved problems Biggest problem is lack of robustness System works well in favorable conditions But is sensitive to noises -unfavorable conditions that inevitably occur 9 C Don Clausing 1998
Build/test/fix – why? • Reactive problem solving – Too little – limited scope of solutions – Too late • Design contains many unsolved problems • Biggest problem is lack of robustness – System works well in favorable conditions – But is sensitive to noises – unfavorable conditions that inevitably occur Fig. 9 © Don Clausing 1998
Proactive problem solving Must shift from emphasis on build/test/fix Must address effects of noises Erratic performance Leads to delusionary problem solving chases problem from one failure mode to another Fg.10 C Don Clausing 1998
Proactive problem solving • Must shift from emphasis on build/test/fix • Must address effects of noises – Erratic performance – Leads to delusionary problem solving; chases problem from one failure mode to another Fig. 10 © Don Clausing 1998