How to review a week of false rejects without blaming the operator first
Sort by cause, not by person. Change the largest class. Use a week’s record, not an impression.
When you review a week of false rejects, sort by cause first: old master, light changed, material texture, threshold too tight. Do not sort by operator first. After the sort, change the largest class. Do not criticise the person who clicked the most.
Why it is judged this way
After an operator is criticised, the next week they flag fewer alarms, and the method is a bypass. The false rejects stay in the product. Draw the causes as a few simple boxes. The quality meeting talks only about the fullest box.
What to compare
| What you see | What to call it | What not to do |
|---|---|---|
| Most are old masters | Change the revision routine | Criticise the operator |
| Most are texture | Loosen the texture by zone | Loosen the whole image |
| There is no record | Record first, then meet | Name people by feeling |
At job change or when a roll is opened
- Export the week’s items that were judged false rejects.
- Sort them into the four causes.
- Change only the largest class.
