>> http://edition.cnn.com/2008/US/06/06/crash.ap/index.html
>
> Has been discussed on ARocket recently, not surprisingly.
>
> Russell says:
>
> 1.    Document identified problems
> 2.    Ensure appropriate responses are appropriately
> promulgated.
> 3.    Yeah, right.

This sort of thing is why I'm pushing at my organization for
a periodic "morbidity and mortality" meeting.  The bottom
line is that in any organization, nobody knows everything.

We have a fairly good system of problem solving, with a
regimented documentation procedure.  The flaw is that the
problem solving is done by one group of engineers while
the design of the next generation of products is done by
another.  My hope is that I can organize a bi-monthly
meeting of about one hour in length where a "headline"
version of the problems found since the last meeting is
presented, and a 10-minute presentation by the lead
engineer on each completed problem is given.

We'll see if that happens. :-)

Mike H.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist