Part 1 of 2:

Picture this: You have been headhunted to take up a position as senior test manager in a fast growing company. At 10AM on your first day on the job, you are presented by your new boss with two customer returns. The customer, a global electronics company, has scheduled a call for 12 noon with your VP of Quality, whom you have yet to meet. You are told that she wants to talk to you before the meeting and is asking for details on whether any more shipped parts could have the same problem.

The two parts in hand, you head to the test development lab and ask the most senior looking test engineer you can find to datalog these to the same test program as was used to test them originally. Within 45 minutes he rings you to say that he has the parts tested adding that only 3 lots had this issue and the other lot just shipped last week. He can have an engineer update the test program within the next three weeks to help capture the issue if it happens again. Just then the VP of Quality rings you, you tell her what you just heard and she thanks you and you just say that you are making sure that the checks are in place to spot this in the future.

You put the phone down and call the test engineer. How could such detailed information be available on such a high runner so quickly? You were expecting the whole issue to take days at least to resolve. Is this engineer some sort of genius, or even, dare you think, a spoofer?!

“How soon can you update the program, three weeks seems like a long time?” you ask. He says that the program will be updated within the next three weeks but adds that he can make sure the issue is detected anyway even without updating the program. In fact he has already ensured that this is in place and any lot in the meantime exhibiting the issue will be put on hold.

You look forward to his explanation, scheduling a meeting that afternoon with him as within the next fifteen minutes you have a training class for a system you never heard of that your new company uses for managing yield called “yieldHUB”.

Your experience over the years is that it takes days to check through raw data to detect scenarios related to RMAs. How can they do it so quickly here in this fascinating new company you just joined?