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

In the process of product manufacturing, 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 assessment. Many companies are accustomed to passively responding to changes, often resulting in "fixing one issue only to create another" or even batch quality incidents. Effective management of design changes and process changes is the core capability that transforms changes from "uncontrolled random events" into "controlled improvement opportunities."

1. The Fundamental Differences Between Design Changes and Process Changes

Understanding the differences between the two is the first step in effective change management. Many companies treat design changes and process changes as the same, using a single process to handle both, which can lead to insufficient management precision—either over-controlling simple process adjustments or under-assessing the process impact of design changes.

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 typically comes from changes in customer requirements, correction of design defects, cost reduction optimization, or regulatory compliance. For example, in the automotive industry, a common Engineering Change Request (ECR) 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 alters the product definition, necessitating synchronized updates to the Bill of Materials (BOM), drawings, and performance standards.

Process Change (Process Change, PC) involves modifications to the manufacturing methods and processes, including changes in machining operations, process parameters, tooling, equipment settings, and work instructions. The driving force behind process changes usually comes from capacity enhancement, quality improvement, new equipment introduction, or material substitution. For instance, to improve machining efficiency, the production department proposes increasing the cutting speed from 800 rpm to 1200 rpm for a certain operation—this is a process change. The manufacturing parameters change while the part design remains unchanged.

The fundamental difference between the two lies in: design changes alter "what the product is," while process changes alter "how the product is made." However, there is a close relationship between the two—design changes often require corresponding process adjustments to implement (such as revalidating welding processes after material changes), and process changes may also trigger a re-evaluation at the design level (such as when a new process cannot achieve the original design tolerances, requiring a design concession).

In actual management, the boundaries between the two are often blurred. For example, a supplier replaced the injection molding raw material grade under the guise of "process optimization," resulting in a decrease in the final product's strength. On the surface, this appears to be a process change, but in essence, it affects the product design definition due to changes in material properties 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 approach.

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

A robust change management system should cover the entire lifecycle of changes, 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 suggested urgency. The key at this step is to lower the initiation threshold, encouraging frontline personnel to propose change requests rather than opting for "fix it first and deal with the consequences later" due to cumbersome procedures. 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 Evaluation and Grading. The change management department (usually the Quality Department or the Technical Department's change management specialist) receives the request and organizes a cross-functional team for an initial evaluation. The core of the evaluation is to determine the risk level of the change, typically divided into three grades:

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

The classification 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 to reduce disputes during the review process.

Step Three: Plan Development and Validation. Develop detailed implementation plans and validation plans based on the change level. Design changes require the output of revised drawings, BOMs, technical specifications, and design reviews, prototype production, and functional testing. Process changes require updates to process documents, Process Failure Modes and Effects Analysis (PFMEA), and control plans, and validation of process stability and Cpk values under small batch conditions. The validation phase recommends the "three-batch validation method"—producing three consecutive batches of products, sampling and testing critical 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 genuine and reliable.

Step Four: Cross-Functional Review and Approval. A change should not be decided by a single department. A complete change review committee should include: Design/Process Engineering (technical feasibility), Quality Department (quality impact assessment), Production Department (manufacturing feasibility), Procurement Department (supply chain impact), and Marketing/Sales Department (customer communication). Each department signs off, taking responsibility for the impact of the change within their functional scope. A-level changes also require written customer approval. For changes across regions or legal entities, representatives from related factories or business units should be included in the review to avoid the situation where "one place changes, others are unaware."

Step Five: Change Implementation and Cutover Management. This is the most vulnerable step in change management. The key to change implementation is cutover control—determining the exact moment in production when the old state transitions to the new state. Common cutover 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 goods are clearly marked and traceable before and after the switch to prevent mixing of old and new materials. A practical approach is to set up a "cutover checklist" at the cutover point, where the team leader on-site 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. Within a certain period after the change implementation (usually 30 days or one production cycle), the change management team should continuously track the change's effects, verifying whether quality metrics (such as first pass yield, defect rate, Cpk) meet the criteria, customer feedback is positive, and production is stable. After confirming no abnormalities, formally close the change process and archive relevant documents. At the same time, generate a change summary report, documenting key lessons learned during the change process, and incorporate these 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 Evaluation. In many companies, change evaluations become a mere formality—participants leave early due to busy schedules, and review opinions are overshadowed by "time pressure." The countermeasure is to establish a quantified change evaluation matrix, scoring the 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 formulated.

Pitfall Two: Neglecting Process Changes. Compared to design changes, process changes are often seen as "minor issues" that do not require strict procedures. In reality, process changes can significantly impact product quality—a change in welding temperature parameters may directly lead to 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, regardless of its size, is managed.

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

Pitfall Four: Unmanaged Supplier Changes. Companies may have a good internal change management system, but supplier changes are often overlooked. Many quality incidents are rooted in suppliers changing 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, critical supplier changes should be integrated into the company's change management platform for unified control.

4. Systematized Tools for Change Management

To make the change management system truly effective, the following supporting tools are essential:

ECN/ECO System Digitalization. Traditional paper-based Engineering Change Notices (ECNs) are slow to circulate and difficult to trace. It is recommended to use a professional design change management system or the change management module in a Product Lifecycle Management (PLM) system to achieve the full electronic process from 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 essential to update the relevant Design FMEA (DFMEA) or Process FMEA (PFMEA), assessing the potential failures and their severity, occurrence, and detection in the new state. 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?

Alignment of Change Management and PPAP. For A-level and B-level 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 Analysis (MSA), 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 standards explicitly require organizations to submit PPAP for any product or process changes that affect customer requirements, otherwise, it may lead to a suspension of supply qualifications.

Change Knowledge Base Construction. Each change is an opportunity for organizational learning. Building a change experience database, where the background, plan, validation results, and lessons learned are archived by product type and failure mode, provides a reference for 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 material substitutions by suppliers, 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 in Change Management

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

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

To achieve the evolution from compliance to agility, companies need to continuously improve in three areas. First, at the process level: establish differentiated change channels to allow low-risk changes to "take the fast lane" and high-risk changes to "take the standard lane," adapting the process instead of applying a one-size-fits-all approach. Second, at the capability level: enhance the risk assessment skills of frontline personnel 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 metrics for change cycles, success rates, and anomaly rates, 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 and capability building.

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

Knowledge Number: 8.4.1

Version: v20260705

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