In Reply to Parent Post by forestfan 1000
so what do i think should be on a form, well i always work on a basis of : what, why, how,when, who,
so on that theory i suppose we have to determine a fault has been found,
why the fault has arisen , how is it to be corrected, when is is to be completed by, and by whom. that is my interpretation of it, so if you think im way of the line im going throw it all in the bin,
thanks for your help
Just me playing devil's advocate here (because I love that job...I really should have that
title on my business card!
) what constitutes a "fault"? Is it possible to varying degrees of "faultness"?
Not knowing about your organization or products/services, let me just that at my company we can make bad product...but the level of bad product resolution is determined on (a) amount of bad product made and (b) characteristics of the bad product.
If only x amount of product had a characterisitic y, then we might simply disposition the product accordingly and get on with our lives.
If, however, x amount of product had a charasteristic z or X amount of product (where X > x) had characterisitic y, then we might require root cause analysis, and so on.
To help us out, we have a guidelines matrix that tells us the possible bad things that could happen and to what level it must happen in order for us to take the appropriate action. Afterall, no point in killing a mosquito with a flame-thrower, right? Just as you wouldn't go after an alligator with only a toothpick.
Keep in mind, as well, that when you do the root cause section, people know to look for the true reason behind the abnormality...not just the symptoms. The old adage of "ask 'why' five times" is a good rule of thumb. Why? "Operator unaware of new process." Why? "Operator not trained." Why? ... well, you get the idea.
Qualitygoddess is absolutely correct in ensuring user-friendliness of the process, too! Prior to my starting, the form used here was 3 pages in length! No one wanted to report bad product. The form was then modified to 1 page to keep the users happy while ensuring the tools were there to adequately address the abnormality. It is now 2 pages in length and electronic. It suits the needs of Business Management System, allowing for abnormalities in the Environmental or Safety side of things, has a fishbone diagram (in case the 5 'why' approach doesn't work), and has drop-down menus that change depending on the selections checked-off at the beginning of the form.