InsightFab
Knowledge Base/New Product Introduction (NPI) Quality Control: The Gate Review System
Quality Assurance6 min read

New Product Introduction (NPI) Quality Control: The Gate Review System

This article recounts a real-world scenario where a new process introduction resulted in a Cpk report of only 1.08, causing immediate silence and distress. The author emphasizes that such issues are preventable with proper "Gate Review" implementation, analyzing how engineers often rely on intuition, leading to critical problems being missed at early stages and escalating later. This article highlights the importance of "Gate Review" in preventing costly issues.

That day, when the Cpk report came out, the whole room fell silent for three seconds

I still remember several years ago, when our factory was about to introduce a new process. Everyone was swamped, from process equipment and material validation to backend testing, working frantically every day. Finally, the first batch of wafers was completed, and the eagerly awaited Cpk report was released. In the conference room, the screen prominently displayed a number: 1.08. The entire room truly fell silent for three seconds, you know? The atmosphere was so heavy that I was careful even to breathe. The boss's face instantly dropped. I knew, it was over; this batch of new products would be delayed again. But did you know? If we had properly implemented "Gate Review" then, this kind of mess would never have happened.

Where the Problem Lies

To put it plainly, when introducing a new product, there are numerous hurdles to clear, from the R&D phase, process development, yield improvement, all the way to mass production. However, many times, we engineers rely too much on our "gut feeling." We think it's "good enough" and rush the product to market. What's the result? Either material issues, unstable process parameters, or problems with the judgment logic at the testing stations. These problems aren't caught at the corresponding "gates" and are carried all the way to the end, only to explode then. By that point, the cost of rectification is huge. Gate Review, in essence, helps you set up these "gates," like checkpoints. Each stage must meet specific quality standards to be released to the next. Didn't pass? Then go back and redo it!

How It's Actually Done

So, how exactly does Gate Review work? It's quite simple: break down the entire New Product Introduction process into several key quality thresholds.

  1. Design Verification Gate (Gate 1): A product you design isn't useful if it's only theoretically feasible. This stage ensures the design itself is robust. For example, simulation results must meet target specifications, and manufacturability considerations must be taken into account.
  2. Process Verification Gate (Gate 2): This is when experiments are run. The yield target for small-batch pilot production must be met, and the stability of key process parameters, with Cpk values, must reach at least 1.33 to pass. If a number like 1.08 appears, it certainly means Gate 2 was not properly executed.
  3. Reliability Verification Gate (Gate 3): A product isn't good just because it works right after being made; it also needs to be durable! This stage requires passing various reliability tests, such as high temperature/high humidity, thermal cycling, and life testing, to confirm the product can withstand your promised warranty period.
  4. Mass Production Readiness Gate (Gate 4): This final gate ensures that all preparations before mass production are in place. From Standard Operating Procedures (SOPs), anomaly handling procedures, and equipment maintenance plans, to even supplier material readiness, everything must be confirmed to be sound. DPMO must also be controlled within the target range, for example, requiring below 300 DPMO for mass production release.

Therefore, the key is that each gate must have clear "release criteria" and be reviewed by a cross-functional team, not just based on one department's input.

The Most Common Pitfalls

I'm telling you, the most common pitfall is "rushing deadlines." The boss says the project is important and needs to go into mass production quickly, so everyone starts making various "accommodations." Cpk for Gate 2 didn't meet the standard? No problem, let's just release it to Gate 3 and figure it out later. What's the result? By Gate 3, reliability tests reveal a host of issues, bringing everything to a halt. At this point, going back to investigate Gate 2 issues is like starting over, which only further delays the entire introduction timeline.

Another pitfall is "inadequate review." During meetings, everyone is on their phones, signing off quickly without actually scrutinizing the reports. To put it bluntly, it's mere "formalism," without truly grasping the spirit of Gate Review. Frankly, if Gate Review is done merely to appease the boss, then the system is as good as non-existent and only wastes everyone's time.

One Thing You Can Do Today

Re-examine your current New Product Introduction process and see if there are clear quality gates.

Want to try it yourself?

Every tool mentioned in this article is available on InsightFab — just upload a CSV to analyze.

Go to Tools