Worn tooling, loose components, blocked filters, inadequate lubrication, and other forms of equipment deterioration can gradually affect process stability and product quality. By the time the machine finally breaks down, the factory may already have produced hours, or even days, of defective products.

Preventive maintenance helps factories identify and address these risks before they turn into costly production emergencies. It replaces unpredictable breakdowns with planned inspections, cleaning, servicing, and component replacement.

Join us as we explain how preventive maintenance can reduce defects, unplanned downtime, excess inventory, delayed shipments, and emergency repair costs. We also discuss how it works alongside 5S, process control, and factory automation to support more consistent manufacturing performance.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Summary

• 00:00 – Why preventive maintenance matters
  Adrian introduces this CMD Gold episode and explains why factories with experienced employees and expensive machinery can still suffer from defects, delays, and lost production capacity.
• 01:10 – What happens when factories rely on reactive maintenance
  Renaud describes the typical cycle in a poorly managed factory: machinery is installed, operated until it fails, and then repaired under intense production pressure without the necessary spare parts or preparation.
• 03:06 – What preventive maintenance means
  Preventive maintenance replaces unexpected breakdowns with planned inspections, cleaning, servicing, and component replacement. Some downtime remains, but it occurs at a controlled and convenient time.
• 04:29 – Is preventive maintenance more expensive?
  An unexpected equipment failure can produce defective parts, disrupt production planning, create material shortages, leave workers idle, and shorten the useful life of the machinery. These costs are often far greater than the cost of planned maintenance.
• 07:42 – Daily, weekly, and usage-based maintenance
  Operators can perform simple daily checks such as cleaning filters and looking for oil leaks. Technicians can conduct more detailed weekly inspections, while other components should be serviced or replaced according to operating hours or production cycles.
• 11:52 – Why factories resist planned maintenance
  Production managers may be reluctant to stop machinery while orders are waiting. This can create conflict between production and maintenance teams and encourage factories to operate equipment until it fails.
• 13:05 – Maintenance skills and automation
  More advanced automation creates more potential points of failure and requires better-trained technicians. Factories should automate progressively and make sure each new system is reliable before adding further complexity.
• 15:32 – Capacity, inventory, and customer benefits
  Reducing unexpected downtime increases usable factory capacity. It can also allow the manufacturer to hold less protective inventory, offer shorter lead times, improve labor productivity, and deliver more reliably.
• 18:17 – Preventing defects and supporting process control
  Worn or damaged machinery may continue producing bad parts before anyone realizes something is wrong. Preventive maintenance, 5S, and process monitoring reinforce one another by revealing deterioration before it causes a major failure.
• 20:12 – Planned maintenance or emergency repairs
  Maintenance is unavoidable. A factory can either perform it according to a documented plan or wait until equipment breaks and employees, production schedules, and customers are already affected.

Takeaways

• Every factory pays for maintenance. Preventive maintenance determines when that cost is incurred and limits the disruption it causes.
• Machines can produce defects before failing. Equipment deterioration is therefore a quality risk as well as a downtime risk.
• Operators and technicians have different responsibilities. Operators can complete basic daily checks, while trained personnel handle more detailed servicing.
• Maintenance can be time- or usage-based. Replacement intervals may depend on days, operating hours, production cycles, or measured deterioration.
• Production pressure is a major obstacle. Factories frequently postpone maintenance because they do not want to stop a busy machine.
• Automation increases maintenance requirements. More advanced equipment introduces additional failure points and demands stronger technical capabilities.
• Good maintenance increases effective capacity. More reliable equipment improves output without necessarily requiring additional machinery.
• 5S, process control, and maintenance work together. Clean, controlled processes make developing problems easier to identify.

Further Reading

• Preventive Maintenance Plan Template
• Is Investing In Process Automation In The Factory Worth It? + Implementation Best Practices [Podcast]
• Two Preventive Maintenance Examples: Go for More Structure
• Are Preventive Maintenance and Process Control the Same Thing?
• Manufacturing Cycle Time (Part 1): Machining Optimization
• Why Inconsistent Component Variation Is Bad for Assembly & Product Quality
• 10 Key Factors That Affect Supplier Production Capacity
• 3 Key Process Improvement Tools You Need To Start Using: Flow Chart, FMEA, Control Plan

The post Preventive Maintenance: How to Reduce Factory Downtime and Quality Problems appeared first on QualityInspection.org.

That is because technical validation confirms whether a product performs as designed. It does not always reveal whether the product feels intuitive, comfortable, responsive, or easy to use in real-world conditions.

Adrian and Paul Adams examine the gap between engineering compliance and user experience. They discuss how packaging can accidentally activate a product, why a safe surface temperature may still feel uncomfortably hot, and how controls, materials, setup instructions, and response times can make a technically sound product feel faulty.

The episode also explains why product teams should test early prototypes with independent users, observe how they interact with the product, and continue using it long enough to uncover frustrations that a specification or checklist may never capture.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Summary

• 00:00:45 – How can a technically correct product still fail users?
  A product may meet every specification and pass all its technical tests while still feeling awkward, confusing, uncomfortable, or unreliable to the customer.
  Users do not experience engineering reports or test results. They experience how the product responds, how it feels in their hands, and whether they can understand and operate it easily.
• 00:02:02 – A specification is a checklist, not the complete product experience
  Specifications are effective for measurable requirements such as dimensions, voltages, timings, tolerances, and material hardness.
  However, requirements such as whether a grip feels comfortable, whether a product seems too heavy, or whether a control feels intuitive are much more subjective. These qualities cannot always be captured accurately with a single number.
• 00:03:27 – When packaging made a working product appear faulty
  Paul describes a battery-powered product that operators accidentally switched on while placing it into its packaging.
  By the time customers opened the box, the battery could be depleted. Their first impression was that the product was defective or had not been charged properly, even though it had functioned correctly during production.
  
• 00:04:35 – When the first solution created another usability problem
  The initial solution was to require users to hold the power button for two seconds.
  This prevented accidental activation during packing, but test users then reported that the product would not turn on. They expected it to respond immediately, as similar products did.
  The technical requirement had been met, but the behavior did not match user expectations.
• 00:05:40 – Fixing the packaging instead of compromising the product
  The team restored the short press required to turn on the product and instead modified the packaging.
  By removing two of the finger openings, operators and users could only lift the product from positions away from the power button.
  This prevented accidental activation without making the product feel unresponsive.
• 00:06:38 – Passing a safety requirement does not guarantee comfort
  A product may remain well below the maximum external temperature permitted by its safety specification but still feel unpleasantly hot during normal use.
  Paul gives the example of a kitchen product designed to remain at approximately 40°C, despite a permitted limit of 60°C. The product has a significant safety margin, but someone carrying it across a kitchen may still become uncomfortable and want to put it down.
  The product passes the requirement, but the experience may still be poor.
• 00:09:13 – Why usability is harder to validate than engineering
  Engineering problems often have clear answers. A circuit works, or it does not. A component is within tolerance or outside it.
  Usability is less clear. A product may feel comfortable to one user, too light or flimsy to another, and too heavy for someone else.
  The intended users, environment, physical abilities, expectations, and method of operation all influence whether the design provides an acceptable experience.
• 00:11:57 – Why user experience is underinvested during NPI
  Usability testing is often neglected because it can be difficult to specify, measure, budget, and validate.
  Companies developing new products may be willing to invest in engineering tests with objective pass-or-fail results, but hesitate to spend money creating early prototypes for subjective user trials.
  As a result, products may progress through development without enough evidence that intended users can operate them comfortably and intuitively.
• 00:14:13 – Why usability feedback often arrives too late
  Many teams wait until tooling, fixtures, and pre-production builds are complete before placing realistic products in users’ hands.
  At this stage, changing the shape, material, weight, controls, packaging, or internal design can be expensive and may delay production.
  A product can therefore pass every NPI checklist and phase gate while still failing when customers begin using it.
• 00:15:50 – Do not rely only on the people who designed the product
  Product owners and engineers already understand how the product is intended to work. This knowledge can prevent them from noticing instructions, controls, or behaviors that would confuse a new user.
  The product should be given to people who have never seen it before, ideally without detailed guidance.
  Observing what they try to do, where they hesitate, and what they misunderstand provides more useful evidence than asking the development team to evaluate its own design.
• 00:16:21 – The intended user changes what “good” means
  A powerful cordless vacuum cleaner may work extremely well but still be too heavy for an elderly user to lift, store, or operate.
  Similarly, Paul recalls a technically successful smartphone that was so smooth and slippery that he repeatedly dropped it and replaced it after a month.
  Neither product necessarily failed its specification. The problem was that its physical design did not suit the real user or operating conditions.
• 00:18:26 – What product teams should examine during usability testing
  Paul identifies several areas where technically compliant products commonly create a poor experience:
  – Response timing and delays
  – Missing or unclear visual and audible feedback
  – Buttons that are difficult to find or press
  – Controls that cannot be used while wearing gloves
  – Labels and serial numbers that are difficult to locate or read
  – Setup processes that are not intuitive
  – Instructions that assume too much prior knowledge
  – Materials, shapes, and weights that become uncomfortable during use
  These details may look minor during development but can strongly influence customer satisfaction and product reviews.
• 00:20:25 – Feedback must be clear, appropriate, and noticeable
  A product may beep, flash, or display a signal exactly as specified, but that feedback may still be ineffective.
  The sound may be too loud, too quiet, too high-pitched, too long, or simply irritating. A light may be difficult to see, and a delayed response may make users believe that nothing happened.
  Product feedback should be validated with representative users rather than selected only according to the development team’s judgment.
• 00:24:01 – Setup should be intuitive, and instructions should be easy to follow
  New or innovative products may not behave like products users already understand.
  The setup process should therefore be intuitive, or the instructions should explain it in language that ordinary customers can follow without specialist knowledge.
  Sending early products and draft instructions to independent users can reveal confusing steps before the product reaches the market.
• 00:25:33 – Product owners need to live with the product
  Using a product briefly is not enough to understand its complete user experience.
  Product owners should use realistic prototypes repeatedly and over an extended period. Daily use reveals frustrations that may not appear during a short test, including inconvenient controls, awkward storage, confusing routines, unnecessary delays, or features that become irritating over time.
  Other representative users should also live with the product because the product owner may be biased by their knowledge of the design.
• 00:27:35 – Test realistic prototypes as early as possible
  Early prototypes do not always need to contain every final feature.
  A prototype may be created specifically to test weight, grip, controls, setup, packaging, or another important aspect of the experience.
  The earlier these questions are tested, the more freedom the development team has to improve the design before tooling and production make changes expensive.

The Main Lesson

Technical specifications are essential, but they cannot fully define whether a product will be comfortable, intuitive, reassuring, or enjoyable to use.

A product may perform exactly as designed while still appearing faulty because its response is too slow, its feedback is unclear, its packaging activates it accidentally, or its controls do not behave as users expect.

It may also comply with safety limits while still feeling uncomfortable, or provide strong technical performance while being too heavy, slippery, difficult to set up, or inconvenient for its intended users.

These problems are difficult to identify using engineering reviews and checklists alone. Product owners and engineers already know how the product works and may unconsciously compensate for confusing behavior.

You should therefore test realistic prototypes with independent, representative users (or live with them themselves) as early as possible. They should observe users without providing unnecessary instructions and examine response timing, feedback, controls, labeling, setup, materials, weight, accessibility, and prolonged daily use.

The goal is not simply to prove that the product works.

Product teams need to feel it, use it, and live with it before approving it for production.

Further Reading

• The New Product Introduction Process Guide
• Prototype Development in China service from Sofeast
• NPI Deliverables Review service from Sofeast
• How To Define Your Quality Standard For Prototypes?
• How To Reduce Risks When Developing New Products? [Video]
• What Is Pre-Production Prototype Testing and Why Is It Critical for Product Success?
• Final Prototype of your New Hardware Product: When Will You Get There?

The post Why Technically Correct Products Still Fail Users appeared first on QualityInspection.org.

The first step is to determine whether the failure comes from the product design, the materials and components, or the manufacturing process itself. Buyers also need to distinguish between understandable issues during early production and repeated mistakes that reveal a supplier has weak controls, poor documentation, or no effective quality system.

In this episode of China Manufacturing Decoded, Adrian and Renaud explain how to investigate recurring production problems, what evidence a supplier should provide after claiming an issue has been fixed, and when transferring production may be the safest option.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Summary

• 00:00:59 – What to do when production problems keep appearing
  A listener asks how companies should respond when manufacturing has already started, but each shipment continues to reveal new quality problems.
• 00:02:14 – Is it a design problem or a manufacturing problem?
  The first step is to identify where the failure originates. Products that cannot withstand normal use may have design or component-selection problems, while units that arrive damaged or dead on arrival are more likely to indicate workmanship or manufacturing failures.
• 00:04:40 – Validate new products before scaling production
  Innovative products should be tested with representative users before a large launch. Reliability testing can simulate expected use, but real-world pilot batches may reveal behaviours, environments, and failure modes that the development team did not anticipate.
• 00:07:00 – Why problems appear during early production
  Issues during the first production runs may indicate that the product did not undergo sufficient pilot builds, troubleshooting, verification, or process qualification before mass production began.
• 00:08:29 – When repeated factory mistakes become a serious warning sign
  Occasional production problems can happen. However, repeated basic mistakes after a product has been manufactured for some time suggest that the supplier lacks effective systems, checks, and controls. A capable factory should detect material, component, machine-setting, and workmanship problems close to their source before they reach the finished product or the customer.
• 00:10:15 – Can supplier audits reduce this risk?
  A quality system audit or initial factory evaluation can reveal whether a potential manufacturer has basic controls, records, and processes in place.
  Buyers must also understand what type of supplier they are working with. Some manufacturers can manage product industrialization and production ramp-up, while others expect the customer to provide detailed technical and project management guidance.
• 00:12:38 – What evidence proves that a problem has been fixed?
  A supplier’s promise that “it will be better next time” is not enough.
  The supplier should investigate the problem, identify its root cause, contain any affected materials or products, implement corrective actions, and validate that the solution works without creating unintended consequences.
• 00:15:38 – Using fixtures to improve consistency
  If a manual operation is producing inconsistent results, a fixture or jig may make the task easier and more repeatable.
  The supplier should provide evidence that the fixture exists, demonstrate how it is used, update the relevant work instructions, and confirm that the new process has been validated.
• 00:16:13 – Make processes easier, better, faster, and cheaper
  Process improvements should first make the task easier for the operator. Easier operations are usually performed more consistently, often become faster, and may ultimately reduce labour and quality costs.
• 00:19:09 – Corrective action versus more inspections
  Some inspection is necessary because defects must be detected before corrective action can begin. Additional inspections may also be needed temporarily when a serious problem appears.
  However, buyers often focus on inspecting finished products without investing enough effort in improving the process that created the defects.
• 00:21:37 – When inspections become supplier babysitting
  If inspectors check everything indefinitely, the manufacturer may begin relying on the buyer’s inspection team to determine whether production is acceptable.
  This removes responsibility from the supplier and discourages them from developing their own effective quality system.
• 00:22:02 – Containment and corrective action must run together
  Extra inspections can act as a temporary filter while the supplier investigates and removes the root cause.
  The buyer may manage the inspection and containment side, while the supplier works on the corrective action. Both activities should continue until there is reasonable evidence that the problem will not return.
• 00:23:12 – Common factory weaknesses to investigate
  Recurring problems often come back to a relatively short list of weaknesses:
  1. Poor incoming material and component controls
  2. No formal first-article approval
  3. Inadequate checks during production
  4. Unclear work instructions
  5. Poor understanding of likely defects and critical characteristics
  6. Insufficient mistake-proofing
  7. Inadequate use of fixtures, jigs, and tooling
  Blaming an individual operator is not a root-cause analysis. The real question is why an untrained or unsupervised operator was allowed to perform an uncontrolled process on the product.

The Main Lesson

Production problems do not automatically mean that a supplier is incapable. New products and early production runs can reveal issues that were not identified during development or pilot manufacturing.

The critical distinction is how the supplier responds.

A capable manufacturer should be able to detect problems close to their source, produce inspection and process records, investigate root causes, implement corrective actions, update working documents, and demonstrate that the solution has been validated.

More inspections may reduce the immediate risk of defective products reaching customers, but inspection alone does not improve the manufacturing process. Used for too long, it can encourage the supplier to depend on the buyer to manage quality for them.

Buyers should therefore use inspection for short-term containment while ensuring that the supplier works on permanent process improvement. If repeated basic mistakes continue, records are unavailable, production is moved between facilities without approval, or the supplier cannot demonstrate effective corrective action, transferring production may be the safest option.

Further Reading

• When and Why a Product Failure Analysis is Required
• QC During NPI: Build Quality In Before Mass Production
• Corrective Actions and Preventive Actions (CAPA) Guide
• Production Transfer: A Roadmap (Assembly Operations Only)
• Use a Corrective Action Plan After a Failed Inspection
• Supplier Quality Management: KPIs and Improvement Tools

The post Recurring Production Problems: When to Fix the Supplier and When to Walk Away appeared first on QualityInspection.org.

Then the team assembles everything inside the final enclosure, switches the product on, and discovers problems that did not exist before.

This is a common but often underestimated stage of new product development. Once separate components and subsystems are brought together, they create a new operating environment. Heat accumulates, airflow is restricted, electromagnetic interference may appear, mechanical clearances tighten, and access to important test points can disappear.

In this episode of China Manufacturing Decoded, Adrian and Paul Adams examine why apparently successful components can fail when integrated into a complete product. They also explain how staged integration, early testing, accessible debugging points, and realistic user testing can prevent these problems from derailing a project.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Summary

• 00:00:21 – Why individually working parts can fail together
  Electronics, firmware, power systems, wiring, mechanical parts, and the enclosure may all work independently. Combining them creates new interactions and operating conditions.
• 00:02:28 – Why everything seems to work on the test bench
  Bench testing gives engineers plenty of space, controlled power, monitoring equipment, test probes, and easy access to the product’s electronics.
• 00:07:40 – What changes when product integration begins
  Integrating systems too early, before each one has been properly validated, can make it extremely difficult to determine which subsystem is causing a fault.
• 00:08:39 – Products must be designed so engineers can debug them
  PCBs need accessible test points and connections that allow engineers to monitor signals, update firmware, and investigate faults after components have been installed.
• 00:10:16 – Integrate one subsystem at a time
  Adding several PCBs, sensors, motors, or other systems simultaneously makes troubleshooting unnecessarily difficult. A staged build allows the team to identify exactly when a problem appears.
• 00:13:45 – A technically compliant product can still fail
  A product may meet its written specification and applicable safety limits but still provide a poor or even alarming user experience.
• 00:15:00 – How heat buildup creates hidden product problems
  A kitchen appliance discussed in the episode remained within its assumed technical limits, but its surface became too hot for users to handle comfortably. This illustrates why regulatory or specification compliance should not be treated as the only measure of success.
• 00:20:19 – The first assembled product is only a mini milestone
  Building the first complete, functioning unit is an important achievement. However, it should be treated as the beginning of integrated system testing rather than proof that the design is finished.
• 00:21:39 – Solving an enclosure airflow problem
  Paul describes a recent project where heat had nowhere to escape from the enclosure. Adding an airflow path and a very small fan reduced the temperature substantially. This issue would not have appeared while the heating subsystem was being tested by itself on the bench.
• 00:23:53 – A five-step product integration playbook
  Paul concludes with five practical rules for managing integration:
  1. Integrate the product in stages.
  2. Test important risks early.
  3. Keep debugging access available.
  4. Test the product as customers will actually use it.
  5. Treat the enclosure as an active part of the complete system.

The Main Lesson

Testing components separately is essential, but it does not prove that the finished product will work correctly.

The enclosure affects airflow, temperature, signal behaviour, component positioning, accessibility, and the way users interact with the product. It should therefore be considered part of the system rather than simply a cosmetic shell added at the end.

Teams should also avoid treating the first complete build as a finished product. It is the first opportunity to observe how all of the subsystems interact under realistic conditions.

Problems found at this stage may still require changes to the electronics, firmware, component selection, internal layout, materials, ventilation, or enclosure design. Discovering and correcting those issues before tooling and production is far less damaging than finding them after products reach customers.

Further Reading

• How Many Prototypes Are Needed Before We Get ‘Perfection?’
• Transitioning to Manufacturing from Product Development | 2 Options
• Prototype Success Is NOT Production Readiness
• Why a Good Prototype Can Still Fail in Production
• Final Prototype of Your New Hardware Product: When Will You Get There?
• How Many Prototype Iterations and Safety and Reliability Tests Do We Need?
• Handover to Manufacturing: What Not to Do and Best Practices
• Test to Failure: Why You Need This Reliability Test

The post Every Component Works. So Why Does the Assembled Product Fail? appeared first on QualityInspection.org.

The real value of events such as the Canton Fair and Global Sources comes from knowing what to ask, what to observe, and which suppliers deserve further investigation.

In this episode of China Manufacturing Decoded, Adrian and Renaud explain how buyers can assess suppliers during an initial booth conversation. They cover how to identify possible trading companies, ask about in-house processes, judge production capacity and customer fit, and avoid being treated as an unprepared “tire kicker.”

They also explain why trade show conversations should only be the beginning of the qualification process. Promising suppliers still need background checks, factory visits, and proper due diligence before you place an order.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Summary

Trade shows remain valuable because they allow buyers to examine physical products, compare many potential suppliers quickly, and ask questions in real time. They are also useful for spotting market trends and emerging technologies. However, products displayed widely at events such as the Canton Fair may also be easily accessible to competitors, so buyers should look for opportunities to differentiate rather than copy what everyone else can see.

Preparation is essential. Buyers should research exhibitors beforehand, arrive with a clear description of what they need, and ask suppliers about their main products, factory location, in-house processes, target markets, customer types, and production capacity. These questions can help reveal whether the exhibitor is a genuine manufacturer or a trading company, whether it controls critical production processes, and whether its size and capabilities are suitable for the buyer’s expected volumes.

Suppliers are also assessing visitors. To avoid being dismissed as a “tire kicker,” buyers should explain their company, market experience, product maturity, and realistic sales forecasts. Exaggerated promises about huge future orders are unlikely to be taken seriously. It is better to discuss credible volumes across the first few years and explain how a smaller initial order could lead to larger business later.

Finally, a professional booth and attractive samples do not prove that a supplier is reliable. Promising conversations should be followed by background checks, factory visits, and more detailed discussions with technical and operational staff before any order is placed.

Further Reading

• How To Get More Out of a China Trade Fair Visit
• How To Find Suppliers in China
• 27 Questions To Ask During a China Factory Visit
• Are Suppliers on Alibaba and Global Sources Trustworthy?
• Sourcing from China 101, Part 2: How to Identify Potential Chinese Suppliers?

Found some possible suppliers? We can help check them:

• Supplier Legal Records Check
• Certificates & Reports Verification
• Supplier Bank Account Verification

The post How to Assess Suppliers at Trade Shows Before You Trust Them appeared first on QualityInspection.org.

But by that stage, the products have already been made.

If a large part of the batch has the same problem, inspection can identify the failure, but it cannot undo the time, materials, and production capacity already spent.

A stronger approach is to define how quality will be controlled before production begins.

Here we’ll explain three types of quality control plans:

1. A product quality control plan that defines inspection, testing, acceptance criteria, responsibilities, and what happens when products fail.

2. A process control plan that identifies critical production steps and explains how quality will be checked while the products are being made.

3. A QC plan for a new product that addresses additional risks involving approved samples, test fixtures, components, tooling, pilot runs, reliability, and compliance.

The discussion also explains why buyers need to define their own quality standards rather than assuming the supplier will do it for them.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Sections:

• 00:00 Introduction to this rewind episode
• 01:56 What quality control plans are and why they are needed before production
• 04:06 Why there is more than one type of QC plan
• 04:43 Type 1: The product QC plan and contract-related quality terms
• 05:28 Defining testing, inspections, AQL limits, compliance, and responsibilities
• 06:41 What happens if serious issues are found after shipment?
• 07:11 Why even smaller buyers should document quality expectations
• 08:06 Type 2: The process control plan
• 09:04 Mapping production processes and critical steps
• 10:20 Turning the control plan into work instructions and checks
• 11:02 When process control plans become important
• 11:54 Why final inspection alone is often too late
• 12:27 Controlling quality through incoming components and sub-suppliers
• 13:50 How to check whether suppliers can follow process control plans
• 15:03 Type 3: The QC plan for a new product
• 16:27 Quality, reliability, and compliance requirements
• 17:35 Golden samples and approved prototypes
• 18:00 Testing stations, jigs, fixtures, and functional checks
• 19:07 Intended use, reliability expectations, and compliance needs
• 19:52 Component manufacturing, assembly, tooling, and work instructions
• 21:35 Pilot runs and pre-production approvals
• 22:35 Why new products force buyers and suppliers to think harder
• 22:59 Supplier optimism and the “we’ll fix it later” risk
• 24:16 Why quality standards need to be clear and useful
• 25:08 Why buyers often skip proper QC planning
• 26:42 Why defining requirements is the buyer’s job
• 27:40 Which QC plans apply to which buyers and products?
• 28:22 QC planning for all buyers vs larger or higher-risk buyers
• 29:26 Why process control is worth considering for new products
• 30:12 Why every buyer still needs at least a basic quality standard
• 31:12 What off-the-shelf and private-label buyers should focus on
• 33:02 2026 outro and key lesson recap

Further Reading

• Quality Control Plan: Defining Expectations Before Production
• How To Set Up A Process Control Plan [11 Steps]
• Golden Sample in Manufacturing
• What Is A PP Sample?
• How to set product specifications?
• You NEED to do product qualification BEFORE mass production!
• How Incoming Quality Control Inspections Fit into an Overall Quality System

The post Why Final Inspection Is Too Late: 3 QC Plans To Use Before Production appeared first on QualityInspection.org.

Some are worried about tariffs. Others want to reduce China-related risks, move closer to their customers, protect their IP, or stop relying on a single supplier that has too much control over their production.

So the idea comes up: should we move production to a new factory?

Maybe Vietnam looks attractive. Maybe Mexico seems closer to the US market. Maybe another supplier in China can do the job. Or maybe the company decides it should own the manufacturing process itself.

But a factory move is not automatically an improvement.

If the current production setup has a poor layout, weak process controls, too much inventory, unreliable equipment, or a poorly understood supply chain, moving to a new building may simply copy those same problems into a different location.

That was one of the main points made by David Collins, CEO of Manufacturing Transformation Group, in a recent discussion with Renaud Anjoran on the China Manufacturing Decoded podcast.

Before choosing a country, a supplier, or a building, companies need to ask a more basic question:

What problem are we really trying to solve?

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Sections:

• 00:00 – Introduction: setting up a new factory
• 01:43 – Who David Collins and Manufacturing Transformation Group are
• 05:04 – Why more companies are considering factory relocation
• 05:50 – China, Vietnam, Mexico, and the real trade-offs between locations
• 08:10 – Why some companies want to own manufacturing again
• 09:32 – Don’t just move the mess to a new factory
• 11:45 – The first question: what are you trying to accomplish?
• 12:02 – Supplier location, workforce skills, logistics, and infrastructure
• 14:18 – Why a real BOM and cost model are essential
• 15:27 – Feasibility studies and idealised factory planning
• 16:07 – Why automation is not always the right answer
• 17:34 – Comparing factory setup scenarios and locations
• 18:16 – Why labour cost should not be the only driver
• 20:48 – IP risks and supplier dependency
• 22:15 – Learning from the problems in your current factory
• 23:46 – Project management during a factory move
• 24:03 – Greenfield vs brownfield factory projects
• 26:09 – Layout planning, implementation, and local specialists
• 27:13 – On-the-ground project management and construction risks
• 28:33 – Equipment commissioning and factory acceptance testing
• 29:50 – Choosing equipment that fits your real needs
• 31:41 – Equipment maintenance, spare parts, and supplier risks
• 32:40 – Why factory setup is a once-in-a-decade decision
• 34:12 – Disciplined planning and avoiding old mistakes
• 36:45 – Closing thoughts

Further Reading

• How To Plan for Transferring Production To a New Factory: 45 Point Checklist
• Transfer Manufacturing From One Chinese Factory To Another With Fewer Risks
• How To Diversify Manufacturing Sources Out of China and Cut Risk
• Sofeast can help you > Electronic Production Transfer from China to India OR Malaysia
• Supply Chain Risk Management, Part 5: Moving Manufacturing to Vietnam, Thailand, Malaysia, or India (Pros & Cons)
• Production Transfer: A Roadmap (Assembly Operations Only)

The post Planning A Factory Move? First Decide What Problem You’re Solving appeared first on QualityInspection.org.

That sounds like a plan. It is not. Here’s why…

It may be a reasonable estimate for a simple mold: one straightforward plastic part, one cavity, no sliders, no undercuts, no difficult surface finish, and standard pre-hardened steel. But most real products are not that simple.

A consumer electronics or IoT product might include several molded parts, each with its own tool, complexity, steel requirements, tolerances, surface finish, and review process. One difficult housing, cover, bracket, or internal frame can become the critical path for the whole project.

The bigger issue is that many buyers misunderstand when the tooling clock starts. It usually does not start when the purchase order is placed or the deposit is paid. Before the toolmaker can start machining, the design often needs to go through a DFM review, questions need to be answered, changes may need to be approved, and the final tool design must be confirmed.

In episode 331 of China Manufacturing Decoded, Adrian spoke with Paul Adams, Head of New Product Development at Agilian Technology, about why the common 8–12 week tooling estimate often creates false expectations. They discussed what really affects tooling lead times, including DFM readiness, part complexity, steel selection, toolmaker capacity, T0/T1/T2 trials, customer response speed, and China’s holiday calendar.

Before you approve tooling, you need to understand which parts are complex, whether the design is really ready, what steel is being used, when machining actually starts, how trial parts will be reviewed, and what buffer is needed if changes are required.

Otherwise, the “8 to 12 weeks” you remember may quietly become 14 to 16 weeks, or longer.

The takeaway is simple: do not treat a tooling quote as a project plan.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Sections:

• 00:00:31 – The “8 to 12 week tooling timeline”
• 00:02:28 – What tooling includes and why it matters
• 00:04:21 – Tooling cost and why first-time founders get caught out
• 00:06:08 – Where the 8 to 12 week figure comes from
• 00:07:23 – Why real consumer electronics products are more complex
• 00:08:35 – When the tooling timer really starts
• 00:11:10 – Why design readiness and DFM review are critical
• 00:13:26 – How part complexity affects tooling lead time
• 00:13:50 – Steel selection: P20, H13, and tool life
• 00:15:40 – Responsiveness during T0, T1, and T2 trials
• 00:16:26 – Why being in China can speed up tooling decisions
• 00:19:03 – Planning around Chinese New Year, Golden Week, and May Day
• 00:21:47 – How to create a tooling schedule that works
• 00:22:05 – Reviewing the DFM report properly before cutting steel
• 00:24:00 – Building a tooling specification and critical path plan
• 00:25:34 – Understanding T0, T1, T2, and rework cycles
• 00:27:45 – Why you should always build in a schedule buffer
• 00:28:56 – Why many tooling delays come from the customer side
• 00:30:15 – Final advice: understand the full tooling process

Further Reading

• Tooling Management for Plastic Injection Molds in China
• Plastic Injection Mold Tooling Management & Risk Reduction [Podcast]
• Common Design For Manufacture Improvements On Plastic Injection Molded Parts
• Injection Mold Tooling Roadmap: How to Get from Smart Design to T1 Samples
• What are Plastic Injection Mold Tooling Revisions? (3 examples)
• How To Make Faster Injection Mold Tooling [7 Tips]
• Plastic Injection Molding Pilot Runs: What You Need To Know
• The Four Levels of Plastic Injection Molding Suppliers in China

The post Why Injection Mold Tooling Often Takes Longer Than You Were Quoted appeared first on QualityInspection.org.

However, that approach is risky.

A final inspection can detect defects, but it usually cannot explain all the upstream decisions that created them. By that point, the product requirements may be vague, suppliers may already be selected, components may already be approved, tooling may already be made, and the production process may already be running.

That is why QC needs to be built into the NPI process.

Before mass production starts, buyers and manufacturers should define clear product requirements, qualify suppliers and components, plan incoming and in-process controls, prepare inspection and testing methods, review process risks, and use pilot runs to prove that the QC system actually works.

In this episode, Adrian and Renaud discuss the quality control processes that should be implemented during NPI and why preventing defects early is usually far cheaper than finding them later.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Sections:

• 00:01:14 Why many companies treat quality control as an end-of-line activity
• 00:02:08 Why final inspection is reactive, not preventive
• 00:04:01 How to build quality into the product and process earlier
• 00:04:44 Why everything in product development can affect quality
• 00:06:08 Product requirements as the foundation of NPI quality control
• 00:07:09 Supplier qualification, design risks, inspection, and testing
• 00:08:29 Quality gates, validation, reliability, compliance, and performance
• 00:09:36 Manufacturing process controls and why they need to be planned
• 00:12:02 Using AI to help document product requirements
• 00:13:00 Examples of turning user needs into measurable specifications
• 00:15:41 Cosmetic standards, boundary samples, and critical measurements
• 00:18:21 Qualifying suppliers, components, and materials
• 00:19:53 Turning requirements into inspection and testing processes
• 00:22:18 Applying QC controls during prototype and pilot batches
• 00:23:04 Work instructions, jigs, fixtures, and process risk reviews
• 00:25:05 Mistake proofing example: preventing drilling errors
• 00:26:28 Eliminating risks where possible, controlling them where not
• 00:27:12 Why prevention is stronger than end-of-line inspection
• 00:28:04 Final takeaway: quality-forward NPI reduces production risk

Further Reading

• NPI process guide
• NPI deliverables review service from Sofeast
• 7 must-do NPI tasks before a successful launch
• Why skipping part qualification in NPI will cause problems
• 3 key process improvement tools
• Pilot run best practices
• DFM and Industrialization support from Agilian
• You NEED to do product qualification BEFORE mass production!

The post What QC Processes Should Be Set Up Before Mass Production? appeared first on QualityInspection.org.

1. A component is swapped for a cheaper or more available alternative.
2. Firmware is cleaned up before production release.
3. Production is transferred from a prototype shop to a mass production factory.

Each change may look reasonable on its own. The new component may appear equivalent on the datasheet. The firmware update may seem like routine tidying. The new factory may appear capable of making the same product. But each one can change the configuration that was originally validated.

That is why a working prototype is not the same thing as a production-ready product.

In this episode, you’ll learn why component changes, firmware changes, factory transfers, tolerance shifts, and process differences need to be controlled before production starts. We also cover practical safeguards, including configuration control, phase gates, production-representative builds, factory audits, pilot runs, and validation tracking.

Listen to the audio here or on Apple Podcasts · Spotify · Amazon Podcasts · Deezer · iHeartRADIO · TuneIn.

Episode Sections:

• 00:00 – Introduction: why working prototypes still fail in production
• 01:32 – Failure pattern 1: component swaps and hidden validation risks
• 06:26 – Failure pattern 2: firmware tidy-up before production release
• 08:53 – Failure pattern 3: transferring from prototype shop to production factory
• 13:20 – How to bridge the prototype-to-production gap
• 13:48 – Why a structured NPI process matters
• 14:51 – Production-representative builds, EVT, DVT, tooling, and PVT
• 16:49 – Controlled ramp-up instead of jumping straight to mass production
• 17:32 – Configuration control: validation only applies to what was tested
• 20:29 – Practical decision framework for managers
• 22:03 – Setting a configuration baseline from DVT onward
• 23:05 – Using NPI phase gates and change assessment before moving forward
• 24:29 – Factory process audits: why an audit is not just a factory tour
• 27:09 – Pro tips: quality standards, NPI discipline, and validation tracking
• 30:39 – Factory transfers and why pilot runs are essential
• 33:05 – Final recap: what changed, what was validated, and what is now unknown

Further Reading

Get help with your project from Sofeast. These services cover the topics discussed today:

• New Product Introduction Support
• NPI Deliverables Review
• DFM Review for Manufacturing in Asia
• Reliability Engineering & Testing
• Process Management Audit (PMA)
• First Article Inspection

The post Why a Good Prototype Can Still Fail in Production (Part 2): Three Failure Patterns to Watch appeared first on QualityInspection.org.