The Manufacturing Quality Role Is Evolving: What It Means for Operations

By the time a defect is found, the labor, machine time, and material are already in it. Here’s what operations leaders gain when quality shifts from evaluating finished products to proactively engineering standards.

An automotive supplier producing side-view mirror housings believed it had thousands of good parts ready to move forward. The housings had already been molded and sent on to paint. Only then was a surface defect found, which root cause analysis traced back to the molding step.

The result: 5,000 plastic housings that had to be scrapped. The plant was short the parts it needed to meet its delivery commitments, and every one of the scrapped parts already had labor, machine time, and material in it that was lost.

For operations leaders, that kind of problem says everything about why the quality function is changing in manufacturing organizations today.

When a defect is discovered at the end of the line, the business has already paid for it. Worse, those responsible for catching it were often looking in the wrong place: at the output, after the damage was done.

It’s the central problem with the traditional quality-as-enforcer model, and it’s exactly what is driving quality toward a fundamentally different role in manufacturing. It is no longer sufficient to just detect defective parts. Rather, the plant quality function must actively participate in preventing the production of the defective parts.

How Is the Role of Quality Evolving in Manufacturing?

In today’s manufacturing environment, quality can no longer sit primarily at the end of the line inspecting product. Instead, leading organizations are shifting quality’s focus towards a standards engineering and enablement role helping build quality requirements into process design. To be globally competitive, plants must be proactive, not reactive to problems.

That shift matters to operations leaders for several reasons:

• It reduces late-stage surprises and costly rework
• It gives operations a more stable, repeatable process
• It frees up leaders to focus on improving execution rather than firefighting
• It makes consistent performance achievable across shifts and sites

Why Is End-of-Line Quality No Longer Enough?

In the traditional model, engineering defines the product and process, operations runs the process, quality evaluates the product, and anything that fails gets sent back. Quality is the referee.

The problem with that model is timing. By the time quality measures the part, it cannot undo the cost of producing it. A defect found downstream after painting, assembly, or packaging is an issue that directly impacts operations, and in many cases, customers.

At The Luminous Group, we see this tension getting worse as manufacturers face pressure to reduce batch sizes and cut work-in-process (WIP) inventory. Amid these pressures, the impact of discovering quality spills late in the game is much larger. A defect that would have been low to moderate risk in a high-WIP environment can become a supply disruption in a lean one.

Inspection still matters, but inspection alone doesn’t protect you from the cost of discovering failure too late. At that point, the inventory you thought you had is gone.

What Does This Evolution of Quality’s Role Look Like in Practice?

From a practical perspective, the focus is less on final products and more about controlling process inputs. Instead of asking “did this part fail?” after the fact, the question becomes: “what in the process needs to stay in control so the part is built correctly every time?”

Consider an example from a plant we worked with that was experiencing warped injection-molded plastic parts. Quality was measuring warpage on the finished parts—some were deflecting 3 millimeters, others 1.5 millimeters—but that measurement only confirmed failure. It offered no way to prevent the next batch from warping the same way.

After running a design of experiments, quality helped identify that coolant flow into the mold was the causal variable. This allowed them to design the standard around the coolant flow rate, establishing a minimum rate of 7 gallons per minute. They were then able to implement flow rate monitoring across 21 presses to standardize that control plant-wide.

Quality moved from measuring warpage to partnering with operations and engineering to design the standard that prevents it. Quality became part of the solution by focusing on preventing the problem.

This also surfaces an important nuance for operations leaders: a finished-part specification is not the same thing as a workable process standard. Saying the surface can only have a 0.5-millimeter profile doesn’t help if warpage happens over the next 24 hours after molding. By then, potentially hundreds of parts (or more) have already been made. The standard has to be tied to something that can be monitored in real time and acted on before the defect multiplies.

That is what quality’s evolving role actually looks like: pushing one level deeper than the finished-part requirement, into the process conditions that ensure the part is built correctly the first time. Proactive quality reduces the variation in process inputs to reduce the variation in the product produced.

A Proof Point From Fuel Injector Manufacturing

Modern stop-start systems, where the engine shuts off at idle and restarts the moment of acceleration, demand fuel injector quality roughly 100 times higher than the quality control they had been achieving. While the theoretical requirements were clear, the experience wasn’t smooth in earlier cars because the quality capability wasn’t there yet.

Quality engineers at one supplier closely studied the key parameters that needed to be controlled, working directly with machine manufacturers to build closed-loop feedback systems that could improve the quality of parts.

Within four years, they had achieved that 100X quality goal. The quality function was evaluating product specifications and linking them back into process controls, even tying them back to machine design and development.

What Do Operations Leaders Gain When Quality Moves Upstream?

The operations leaders we talk to often describe feeling caught in the middle. They follow the process and still get blamed for scrap, because the process they were handed is only capable of producing acceptable output 98% of the time. Following the standard may not mean consistently hitting quality targets when the standard itself is insufficient.

This is a system problem that the traditional quality-as-enforcer model can’t address.

When quality moves upstream into the process, the standards, and the design of controls and gages, the process becomes more resilient. Operations isn’t constantly penalized for variation that was built into the system before production ever started.

The practical payoff is significant:

• Fewer fire drills. When the process is under control, teams spend less time reacting to failures that were never going to be caught in time.
• Less firefighting, more improvement. Operations should be working on the process and continuous improvement. That isn’t possible when daily fire drills keep leaders stuck in reaction mode.
• Better inventory reliability. Parts that look good actually are good. WIP and batch reductions do not become supply crises.
• More consistent execution. When quality partners with operations and engineering early on to identify the process characteristics that drive results, operations gets a process that is repeatable and holds up under day-to-day operating conditions.
• Improved operational metrics. For operations leaders tracking metrics like overall equipment effectiveness (OEE), first-pass yield, and cost of quality, the upstream model directly moves the numbers that matter.

There’s also a useful distinction worth pointing out here between working in the company versus working on the company. The shift we’re seeing now is partly about giving operations leaders back the time and system reliability to do the latter.

How Does This Help Standardize Execution Across People, Shifts, and Sites?

Moving quality’s role upstream improves consistency by helping ensure standards reflect actual performance drivers and make the right action clear and intuitive for whoever’s doing the work.

To improve execution, standards must connect to process inputs that impact quality outcomes, including:

• Machine settings
• Material inputs
• Timing and sequence of process steps
• Environmental conditions
• Verification methods

It’s also important to note that operators will work around standards that are unclear, or when they don’t understand the reason behind them.

This is where quality’s upstream role connects directly to execution quality on the floor. When quality helps define standards that are tied to the actual cause of failure—and when those standards are designed so that the right action is intuitive and operators understand the “why”—the standard is more likely to hold across shifts and sites.

How Do Manufacturers Make This Shift?

For this change to work, operations has to be the one making the case for change.

That may sound counterintuitive, since we’re talking about quality’s evolving role. What’s critical to recognize is that it’s not about quality expanding its authority or adding more oversight to operations. Rather, it’s about building a three-way operating model where operations, engineering, and quality each bring something different to the table:

• Engineering contributes process and design knowledge
• Operations brings the realities of production
• Quality helps connect requirements to controllable standards and identify where variation is entering the system

For operations leaders who are unsure whether the traditional quality model is holding them back, the place to start is by looking at customer complaints and internal scrap. If the data shows recurring problems that the existing process is not catching early enough, that is strong justification for change.

Beyond buy-in, four things have to be in place:

1. Quality has to get deeply involved in the process. That means running design of experiments, understanding the relationship between product and process characteristics, and contributing to the design of standards that are actually usable on the floor.
2. Engineering needs a seat at the table. This is not a quality-versus-engineering story. Process engineering contributes deep knowledge of how the line runs; design engineering ensures requirements are achievable from the start. Quality’s role is to translate requirements into controllable standards, work that is done with engineering.
3. Operations has to feel safe making the change. If teams believe that quality will introduce a half-finished initiative and leave operations with the fallout, they will not get on board. Quality is uniquely positioned to provide that assurance because quality is the function that receives customer complaints. They can say, credibly, that they want to solve this problem together.
4. Leaders must incentivize quality-minded decisions. If supervisors and plant leaders are rewarded primarily for throughput or units produced, quality goals will lose every time under pressure. In practice, that means people will keep the line moving even when the process is unstable, because the incentive system tells them production comes first. If companies want operations to embrace this shift, production metrics and quality metrics have to be aligned. Otherwise, the organization is asking teams to improve quality while rewarding them for doing the opposite.

This last point is a leadership issue as much as a process one, since trust is vital when we’re talking about changing how work gets done at scale.

Building Processes That Perform by Design

To improve productivity and profitability across plants, manufacturers need standards that do more than describe the result they want. They need standards that control the process, prevent known failure modes, and make good output repeatable at scale.

Quality’s evolution is the mechanism for getting there. When quality functions as a standards engineering and enablement partner rather than a final-stage referee, it reduces the gap between the process as documented and the process as it actually runs.

It’s also worth calling out the assumption that quality and productivity are at odds as a false choice. The traditional quality model reinforces this idea that more checks mean more slowdowns, but the upstream model inverts it.

When the process is under control, yield goes up, rework goes down, and throughput becomes more predictable. Rather than being a drag on productivity, improving upstream quality is what makes improving your metrics achievable.