QE Capability Advancement (3) | Defining the Responsibilities of QE, QC, Process, and R&D: Who Should Make the Final Call

A typical "three-no-man's-land" incident occurred in the injection molding workshop of a manufacturing company. A batch of appearance parts was deemed nonconforming during the final inspection—there were slight flow marks on the surface, and the inspector judged them as NG based on the appearance criteria. The production supervisor believed the flow marks were within the allowable range, citing that a similar situation was previously approved; the process engineer claimed it was not a problem with the process parameters but the mold's condition; and the R&D department responded that the drawing only specified "no obvious defects on the surface" without providing a quantified limit for flow marks. Each party had its own say, and the issue was ultimately resolved with "approve this time, discuss next time." Three months later, the customer complained about a similar appearance issue, and upon retracing the steps, it was discovered that over thirty similar disputes had occurred in the past three months, none of which were recorded, escalated, or resolved. When the boss asked, "Who should be responsible for this batch of goods?" all four departments replied, "I did my job according to my responsibilities." The most expensive lesson in unclear responsibility boundaries is not the argument but the silent disputes.

1. Key Principles: Separation and Attribution of Four Powers

Arguments over responsibility boundaries are essentially due to the mixing of four powers:

• Judgment Authority: The final decision on whether a specific product or batch is conforming or nonconforming.
• Change Authority: Approval to modify inspection standards, process parameter windows, drawings, and materials.
• Release Authority: Approval for concession acceptance, deviation release, and over-tolerance use.
• Stop Authority: Halting production and shipment when evidence is insufficient or risks are unacceptable.

The evidence requirements and consequences of these four powers are entirely different, so they must be granted separately. The underlying principles are as follows:

First, the Principle of Consequence Attribution. The person who bears the consequences of a decision's failure should have the final say. The consequences of inspection judgments are borne by quality, the consequences of process parameters by process, and the consequences of design and materials by R&D. Equal responsibility and authority is the only reasonable basis for boundary division.

Second, the Principle of a Single Final Decision-Maker. At any given time, each power can only have one final decision-maker. Phrases like "joint responsibility" or "joint decision" in documents mean there is no clear responsible person—when something goes wrong, no one can be held accountable, and no one will take it seriously beforehand.

Third, the Principle of Separation of Professional Authority and Final Decision-Maker Authority. A quality engineer (QE) can provide criteria and data and exercise the stop authority, but should not assume the change authority for process parameters. Making the QE responsible for others' decisions leads to blurred boundaries and the response layer consuming all the time; the correct approach is "process has the authority to change, QE has the ability to judge and the authority to stop."

Fourth, the Principle of No Record, No Authorization. Any verbal agreement must be supplemented with a written form within twenty-four hours; otherwise, it is considered an invalid decision, and the product is treated as "undetermined." This may seem strict, but it is the only way to transform tacit boundaries into institutional ones.

2. Practical Steps: Writing Boundaries into Criteria

Step One: List Powers and Assign Them to Unique Positions. For each key process, write the final decision-makers for the four powers into the responsibility matrix: judgment authority belongs to the QE or a qualified inspection supervisor; change authority is divided by object (inspection standards to QE, process parameters to process, drawings and materials to R&D); release authority belongs to quality managers and above, and in cases involving safety or regulatory characteristics, it should be escalated to the highest management or the customer; stop authority can be initiated by the QE, process engineer, or production team leader, with the person who stops being responsible for providing evidence, and no prior approval is required. Criteria: If the matrix contains the word "joint," it must be rewritten; if the stop authority requires prior approval to take effect, it is considered ineffective.

Step Two: Set Time Limits and Levels for Disputes. Disputes are divided into three levels: Level One is judgment discrepancies between positions, resolved within four hours; Level Two is departmental discrepancies, resolved in writing within twenty-four hours; Level Three is cross-departmental or customer-related discrepancies, resolved and communicated to the customer within three working days. Criteria: If a Level One dispute is unresolved within four hours, the batch of products must immediately be placed on hold, not to be stored or released; the target closure rate for Level One disputes is ≥95% on the same day, and the average closure time for Level Two disputes is ≤3 days.

Step Three: Use Data to Seal the Uncertainty in Judgment Authority. The root cause of repeated disputes over appearance and attribute judgments is the lack of quantified criteria. The solution is to prepare at least three boundary samples for each appearance characteristic (conforming boundary, nonconforming boundary, reference boundary) and re-evaluate the inspectors every six months. Criteria: The consistency of the inspector's judgment with the standard Kappa ≥0.75 (≥0.70 for customer standards); if below the threshold, the judgment authority for that characteristic is escalated to the QE and cannot be decided by the position.

Step Four: All Changes Must Go Through Parallel Verification. Whether it is a change in inspection standards, process parameters, or design, the transition period should record three consecutive batches (both old and new criteria are documented), and inventory and work-in-progress items should be counted. Criteria: For changes involving key characteristics, the process capability Cpk ≥1.33 (≥1.00 for non-key characteristics) is required to switch to the formal version; if the capability is below 1.00, it must be rolled back and escalated; if the change affects key or safety characteristics, the PFMEA and control plan must be updated before mass production, and "mass production first, document later" is not allowed.

Step Five: Use a Dispute Ledger to Revise Boundaries. Summarize the number of disputes, types, closure days, and recurrence rates quarterly, and directly write interfaces that have occurred more than three times into formal documents. Criteria: The recurrence rate of similar disputes ≤5%; interfaces that are not recorded in the ledger but have indeed occurred on-site are considered boundary loopholes and must be written into formal documents and re-communicated in the next quarter.

3. Five Common Misconceptions

Misconception One: Treating QE as an All-Purpose Responsible Person. To "quickly resolve disputes," the change authority for process parameters and the judgment authority for production are given to the QE. The result is that the process no longer actively optimizes, production no longer makes independent judgments, and inspectors are hesitant to make conclusions. All decisions are concentrated on one person, and the response layer's proportion inevitably exceeds 50%, while the responsibility has not truly shifted—when something goes wrong, everyone still has their own say.

Misconception Two: The Higher the Rank, the Final Say. Using hierarchy instead of evidence to turn technical decisions into administrative ones. The criteria are simple: if the decision record only contains a conclusion without referencing criteria and data sources, the arbitration is invalid and must be reconsidered at the data level.

Misconception Three: Verbal Agreement Counts as a Final Decision. Approvals given with a nod in meetings or a verbal agreement in the hallway are untraceable and lead to responsibility voids when they fail. Criteria: A verbal agreement not documented within twenty-four hours is considered non-existent, and the product is treated as undetermined.

Misconception Four: Suppressing Disputes as a Skill. The disappearance of disputes is more dangerous than the disputes themselves—without dispute records, there is no input for improvement and no basis for boundary correction. To evaluate a QE's boundary management capability, check if they can produce the quarterly dispute ledger, not whether they avoided arguments this quarter.

Misconception Five: Changing Only the Documents, Not Counting Work-in-Progress. The transition period between old and new standards is the most typical window for batch escapes: products already judged but not shipped, work-in-progress items, and in-transit items from suppliers are all judged by the old standards, creating a judgment vacuum on the transition day. Counting these three areas and verifying three consecutive batches is the minimum requirement.

4. Self-Check List

• I have clearly defined the unique final decision-makers for the four powers (judgment, change, release, stop) for each key process, and the matrix does not contain "joint responsibility."
• The stop authority can take effect immediately without prior approval; if a Level One dispute is unresolved within four hours, the batch is paused from further processing.
• Each appearance characteristic has ≥3 boundary samples, with a judgment consistency Kappa ≥0.75 (≥0.70 for customer standards); if below the threshold, the judgment authority is escalated to the QE.
• All changes are verified in parallel for three consecutive batches, and work-in-progress and inventory items are counted; key characteristics must have a Cpk ≥1.33 to switch to the formal version.
• I have a quarterly dispute ledger, with a recurrence rate of similar disputes ≤5%, and repeated interfaces have been written into formal documents.

Boundaries are not set by a single meeting but are gradually established through "every dispute leaving a record, and every record leading to criteria." It doesn't matter if the framework is a bit messy; what matters is that disputes are not silenced.

Equal responsibility and authority, disputes must be documented to establish boundaries

Knowledge code: 13.1.1

Version: v20260913

Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.