Design Change and Process Change Management — A Practical Guide for Change Control Throughout the Product Lifecycle

In the product manufacturing process, changes are ubiquitous—customer requests for specification modifications, supplier material replacements, production line process bottlenecks, regulatory updates bringing new requirements... Each change is a quality risk game. Many companies habitually respond to changes passively, often leading to "fixing one issue and creating another," or even batch quality incidents. Design change and process change management are the core capabilities that transform changes from "uncontrolled random events" into "controlled improvement opportunities."

1. The Essential Differences Between Design Change and Process Change

Understanding the differences between the two is the first step in effective change management. Many companies confuse design changes with process changes and handle them with the same procedures, leading to insufficient management precision—either over-controlling simple process adjustments or under-assessing the process impact of design changes.

A design change (Engineering Change, EC) refers to modifications in the product design itself, including changes in product structure, dimensions, materials, performance parameters, and functional characteristics. The source of design changes usually comes from changes in customer requirements, correction of design defects, cost reduction optimization, or regulatory compliance. For example, in the automotive industry, a common ECR (Engineering Change Request) might involve a customer requesting the material of a bracket to be changed from 45# steel to aluminum to reduce the vehicle's weight—this is a typical design change. It directly rewrites the product definition, necessitating synchronized updates to the BOM, drawings, and performance standards.

A process change (Process Change, PC) involves modifications to the product manufacturing methods and processes, including changes in machining operations, process parameters, tooling and fixtures, equipment settings, and work standards. The driving force behind process changes usually comes from capacity improvements, quality enhancements, new equipment introductions, or material substitutions. For example, to improve machining efficiency, the production department proposes increasing the cutting speed of a certain operation from 800 RPM to 1200 RPM—this is a process change. The manufacturing parameters change while the part design remains unchanged.

The fundamental difference between the two is that a design change alters "what the product is," while a process change alters "how the product is made." However, there is a close relationship between the two—design changes often require corresponding process adjustments to be implemented (such as revalidating welding processes after material changes), and process changes may also trigger a re-evaluation of the design (such as when a new process cannot achieve the original design tolerances, requiring design concessions).

In actual management, situations with unclear boundaries are not uncommon. For example, a supplier replaced the injection molding raw material under the guise of "process optimization," resulting in a decrease in the final product's strength—on the surface, it appears to be a process change, but in essence, the change in material properties affects the product design definition and should be classified as a design change. Because of such gray areas, the change management system must have a flexible classification mechanism rather than a simple binary division.

2. The Complete Change Management Process—from Initiation to Closure

A robust change management system should cover the entire lifecycle of a change, from identification to closure. Whether it is a design change or a process change, the following six-step process can be followed:

Step One: Change Identification and Initiation. Any employee who identifies a change requirement should be able to initiate the change process through a standardized "Change Request Form." The form should clearly record: the type of change (design/process), the reason for the change (customer requirement/internal improvement/supplier change/regulatory requirement), a brief description of the change, and the recommended urgency. The key in this step is to lower the initiation threshold, encouraging frontline personnel to propose change requirements rather than opting for "fix it first and deal with the consequences later." In practice, leading companies embed change initiation entry points in their quality management systems (QMS) and set up one-click filling templates to control the initiation time to within five minutes.

Step Two: Change Assessment and Grading. The change management department (usually the quality department or the technical department's change management specialist) receives the application and organizes a cross-functional team for preliminary assessment. The core of the assessment is to determine the risk level of the change, typically divided into three grades:

• Grade A (Major Change): Changes that affect product functionality, safety, regulatory compliance, or customer key characteristics. These require complete validation and customer approval.
• Grade B (Moderate Change): Changes that affect assembly, performance, or manufacturing stability. These require internal validation and, depending on the situation, customer notification.
• Grade C (Minor Change): Changes that only affect documentation, labeling, or non-critical appearance. These require internal filing only.

The division of risk levels should be based on the Failure Modes and Effects Analysis (FMEA) approach, determined collectively by the team rather than by individual subjective judgment. It is recommended that companies clearly list examples of criteria for each level in their change management procedure documents to reduce disputes during the review process.

Step Three: Plan Development and Validation. Develop detailed implementation plans and validation plans based on the change grade. Design changes require outputting revised drawings, BOMs, and technical specifications, followed by design reviews, prototype production, and functional testing. Process changes require updating process documents, PFMEAs, and control plans, and validating the process stability and Cpk values in small batches. The validation phase recommends using the "three-batch validation method"—producing three consecutive batches of products, sampling and testing key characteristics in each batch, and only proceeding to the next step if all three batches meet the criteria. This method effectively excludes the influence of random factors, ensuring that the process capability after the change is truly reliable.

Step Four: Cross-Functional Review and Approval. A change cannot be decided by a single department. A complete change review committee should include: design/process engineering (technical feasibility), quality (quality impact assessment), production (manufacturing feasibility), procurement (supply chain impact), and marketing/sales (customer communication). Each department signs off, taking responsibility for the impact of the change within their functional scope. Grade A changes also require written customer approval. For changes across regions or legal entities, representatives from associated factories or business units should be included in the review to avoid the situation where "one place changes, and others are unaware."

Step Five: Change Implementation and Breakpoint Management. This is the most vulnerable link in change management. The key to change implementation is breakpoint control—determining the exact moment in production when the old state switches to the new state. Common breakpoint methods include: switching by production batch, product serial number, production time, or work order number. Regardless of the method, it is essential to ensure that materials, work-in-progress, and finished products before and after the switch are clearly labeled and traceable, avoiding the mixing of old and new materials. A practical approach is to set up a "breakpoint checklist" at the switch point, where the team leader confirms each item: whether old materials have been completely removed, new materials are in place, operating system parameters have been updated, work instructions have been replaced, and operators have completed training.

Step Six: Change Verification and Closure. For a period after the change implementation (usually 30 days or one production cycle), the change management team should continuously track the change's effectiveness, verifying quality metrics (such as first-pass yield, defect rate, Cpk), customer feedback, and production stability. After confirming no abnormalities, formally close the change process and archive the relevant documents. At the same time, generate a change summary report, documenting key lessons learned during the change process, and incorporate it into the organization's knowledge base.

3. Common Pitfalls and Countermeasures in Change Management

Even with a complete change management process, some typical failure modes still exist in practice:

Pitfall One: Formalistic Change Assessment. Many companies treat change assessments as a formality—meeting participants leave early due to busy schedules, and review opinions are overshadowed by "time pressure." The countermeasure is to establish a quantified change assessment matrix, scoring quality impact, cost impact, delivery impact, and customer impact across different dimensions. If the total score does not meet the criteria, a new plan must be developed.

Pitfall Two: Neglecting Process Changes. Compared to design changes, process changes are often seen as "minor issues" by companies and do not require strict procedures. In fact, process changes can significantly impact product quality—a change in a welding temperature parameter may directly result in insufficient weld strength. The countermeasure is to establish a dual-track management system for design changes and process changes, ensuring that any change involving process control elements is managed, regardless of its size.

Pitfall Three: Inadequate Breakpoint Management. During change implementation, the mixing of old and new materials is the leading cause of quality incidents. A certain automotive component company once experienced a production line shutdown due to a design change where old version materials were not promptly handled, resulting in two different specifications of parts being mixed in the same batch. The countermeasure is to implement a "physical breakpoint method"—setting up clear physical isolation (such as a red isolation zone) at the switch point and using differentiated color labels for old and new materials to ensure 100% traceability of materials passing through the station.

Pitfall Four: Uncontrolled Supplier Changes. Companies may have a good internal change management system, but completely ignore supplier changes. Many quality incidents are rooted in suppliers changing raw materials or processes without notification. The countermeasure is to include change notification clauses in supplier quality agreements, requiring suppliers to provide written notification and obtain approval before making changes. Additionally, key supplier changes should be incorporated into the company's change management platform for unified control.

4. Systematic Tools for Change Management

To truly implement a change management system, the following supporting tools are essential:

ECN/ECO System Informatization. Traditional paper-based ECNs (Engineering Change Notices) are slow and difficult to trace. It is recommended to use a professional design change management system or the change management module in PLM to achieve the full electronic process of change request → review → approval → implementation → closure. The system should have features such as automatic notifications, timeout warnings, and change history tracing.

Integration of Change Management and FMEA. Each change may introduce new failure modes. During the change review, it is necessary to update the relevant DFMEA or PFMEA, assessing new potential failures and their severity, occurrence, and detection. Embedding change management into the dynamic maintenance process of FMEA ensures continuous risk identification and control. Specifically, the change review team should answer three questions: Has the new characteristic introduced by the change been covered by the FMEA? Have the ratings of existing failure modes changed due to the change? Are new control measures needed in the control plan?

Integration of Change Management and PPAP. For Grade A and B design changes and some major process changes, it is necessary to resubmit PPAP (Production Part Approval Process) documents to the customer before implementation, including updated control plans, process flow diagrams, measurement system analyses, and initial process capability studies. The change management process should include PPAP level determination and submission requirements. The automotive industry places particular emphasis on this—IATF 16949 standard explicitly requires organizations to submit PPAP for any product or process changes that affect customer requirements, otherwise, it may result in the suspension of supply qualifications.

Change Knowledge Base Construction. Each change is an opportunity for organizational learning. Establish a change experience database, archiving the background, plan, validation results, and lessons learned of changes according to product type and failure modes, for reference in future similar changes. This not only accelerates change decision-making but also enhances the organization's change management capabilities. For example, after a company experienced customer complaints three times in a row due to supplier material substitutions, the knowledge base analysis revealed a common issue—too short a validation cycle. The company then updated its management system, extending the validation cycle for material changes from two weeks to four weeks, effectively controlling similar risks.

5. From Compliance to Agility—Continuous Evolution of Change Management

Traditional change management emphasizes "compliance" and "approval," with rigorous processes but longer cycles. In a rapidly iterating market environment, how to balance the rigor of change control and the agility of response is a challenge every quality manager faces.

Excellent companies are exploring a "tiered authorization + fast track" model: for clearly defined Grade C and some Grade B changes, pre-authorize relevant functional leaders to approve, shortening the review cycle; simultaneously, establish a change database, using risk prediction models trained by historical data to assist in rapid decision-making. However, it is important to note that agility does not mean arbitrariness—the basic principles of change management (assessment, validation, traceability) should not be compromised at any level.

To evolve from compliance to agility, companies need to continuously improve in three areas. First, at the process level: establish differentiated change channels, allowing low-risk changes to "take the fast lane" and high-risk changes to "take the standard lane," adapting processes instead of applying a one-size-fits-all approach. Second, at the capability level: enhance the ability of frontline personnel to assess change risks through training and authorization, ensuring the right people make the right decisions at the right stages. Third, at the data level: accumulate historical change data, establish baseline indicators for change cycle, success rate, and anomaly rate, and use data to drive process optimization.

When change management evolves from "passive approval" to "proactive anticipation," companies can identify risks and prepare solutions in advance, elevating the value of change management from "preventing errors" to "empowering improvements." This is not just the work of the quality department but a reflection of the entire organization's system performance capability.

Change is the starting point for improvement, not the source of accidents.

Knowledge code: 8.4.1

Version: v20260705

Author: Quality Think Tank

Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously enhance their quality capabilities.