InsightFab
Knowledge Base/Effective Ways to Conduct Supplier Performance Review Meetings (QBR)
Supply Chain Quality6 min read

Effective Ways to Conduct Supplier Performance Review Meetings (QBR)

This article provides practical insights into conducting effective Supplier Performance Review (QBR) meetings, emphasizing their role in problem-solving rather than mere reporting. It stresses the importance of delving into the 'why' behind performance metrics, using compelling data like a DPMO of 6210 to drive meaningful discussions and actionable improvement plans with suppliers.

That day, when the DPMO report came out, the supplier's face turned pale.

I still remember two years ago, our production line was in chaos with delivery dates due to defects in a critical material. That time, we held a QBR (Quarterly Business Review) with that supplier, and I still remember how heavy the atmosphere was in the meeting room. At the start of the presentation, we showed this quarter's DPMO (Defects Per Million Opportunities) report, and the number was 6210. Do you know what that means? The supplier's sales representative immediately turned pale, and even our PM, who usually loves to joke, was speechless. That meeting, we discussed for a full three hours before barely finding a few directions for improvement. To be honest, without that "shock therapy," I doubt they would have realized how serious the problem was.

Where's the Problem?

A lot of times, we conduct QBRs like we're "turning in homework." Suppliers come to report a bunch of numbers, you listen and nod, and then next time you have another meeting, the numbers might be better, or they might be worse. But do you truly know the "why" behind these numbers?

To be frank, the core of a QBR is not "reviewing reports," but "solving problems." It should be an opportunity for you and the supplier to sit down, lay your cards on the table, and pinpoint production line pain points. If you just display data without in-depth analysis, how is that different from looking at a dashboard by yourself? What you need is not a pretty chart, but a clear course of action.

So the key is, you must make the QBR a "dialogue," not a "one-way presentation."

How to Do It in Practice?

To make QBRs effective, you need to do your homework and know how to "ask questions." Here are a few points I think are extremely important:

  1. Data must be "meaningful": The data you provide cannot just be a Cpk of 1.08 or a DPMO of 6210; it must be linked to "actual production pain points." For example, you could say: "This month, the wafers you supplied caused 15 tool downs in the Etch step of our process, leading to a loss of 200 wafers." This way, the supplier will feel the impact.
  2. Prepare a "question list" in advance: Don't wait until the meeting to start thinking. I usually, a week in advance, compare the abnormal incidents I have on hand with the supplier's quality reports from the past three months, item by item. Identify items where the numbers are "abnormal" or "continuously deteriorating," and then write down specific questions.
  3. Focus on "a few key issues": QBR time is limited; don't try to cover everything. I usually select 2-3 problems that have the "greatest impact" or are the "most urgent" for discussion. For example, if your wafer yield drops from 99.8% to 99.5%, it might seem like a small difference, but this could lead to you shipping thousands fewer products in a month; that's critical.
  4. Demand a "concrete action plan": The supplier promised improvement? Great, then "how will it be done?" "Who is responsible?" "When will it be completed?" "What are the expected goals?" All of these must be written down. If they just say, "We will optimize the process," that's just nonsense.

In other words, you must guide the supplier to dig from the "phenomenon" to the "root cause," and then formulate "quantifiable" solutions.

The Most Common Pitfall

The most common mistake I've seen is "fear of conflict." Many engineers find it awkward to have a falling out with suppliers, so they let issues be glossed over. Let me tell you, I've seen it happen too many times in my 15 years in this industry. Once, a new engineer at a QBR stood by and watched as a supplier pushed the blame for their own poor quality issues onto our process parameter settings. The engineer stammered and eventually let it go. What was the result? The problem remained unsolved the next month, and he got scolded terribly.

Frankly, QBRs are not for hearing good things, nor for making friends. They are for "uncovering problems" and then "solving them together." If you're not firm enough, not assertive enough, ultimately it's you and your production line that will suffer.

One Thing You Can Do Today

Before your next QBR, list 3 supplier problems you most want to solve and prepare specific data to substantiate them.

Want to try it yourself?

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

Go to Tools

More in this category

Part Approval Process (PAP): How to Substitute PPAP

This article highlights a critical challenge faced by a semiconductor manufacturer: a supplier's component Cpk report of 1.08, a quality level fundamentally unacceptable for their industry, creating a significant impasse. It reveals the substantial divergence between the stringent part validation standards of the semiconductor sector and the traditional automotive PPAP, particularly concerning yield requirements.

Writing Purchasing Quality Specifications (PQS): Clearly Stating Your Requirements to Suppliers

This article uses a jarring anecdote of a production line machine's 1.08 CPK and 6210 DPMO report, coupled with a supplier's "Your specifications said so" defense, to underscore a crucial point: quality failures often stem from inadequately defined requirements. It emphasizes the critical importance of a clear, quantitative Purchasing Quality Specification (PQS) in preventing issues caused by vague standards and lazy template reuse.

Establishment of a Supplier Evaluation System: From Candidate to Qualified Supplier

Many companies struggle with suppliers that are highly recommended but ultimately fail to meet quality standards. This article shares a hard-earned experience where a batch of new wafers in their factory suffered a drastic drop in yield, with alarmingly low Cpk values, highlighting the critical need for a robust supplier evaluation system. It emphasizes that every detail, from equipment and process stability to personnel quality, must be rigorously assessed to avoid seemingly promising but ultimately costly "landmine" suppliers.