Floehopper

thoughts on the bergy bits of life

The key is treating defects as simply information, not automatic triggers for action. For project management purposes, ignore individual defect reports and only deal in aggregates. Use a simple classification scheme, for example by scanning defects with regular expressions. Looking at, “48 A, 23 B, 17 C, 24 others” once a day is much less likely to induce panic than having the defect siren go off every ten minutes around the clock. In the cruise phase each defect is accompanied by the sound of evaporating money. On the runway defects are part of the price of feedback. To Fix Or Not To Fix?: Another Good Question