China Manufacturing Decoded

Rushing a new hardware product into mass production can feel like the fastest route to market. But both buyers and suppliers have commercial reasons to skip NPI steps, and those shortcuts can create much more expensive problems later.

In episode 348 of China Manufacturing Decoded, Adrian and Renaud look at why manufacturers often prefer to move into mass production, where they make their money, rather than spend months on engineering work, small pilot runs, process development, and repeated validation.

They explain when moving quickly can be relatively low-risk for a familiar, established product, and why the same approach becomes dangerous when a product is new, highly customized, or requires new manufacturing and testing processes.

The buyer side matters too. Launch deadlines, promises to customers, funding constraints, cash-flow pressure, and the need to start generating revenue can all tempt companies to commit to large production quantities before the design and manufacturing process are truly ready.

The result can be custom components, tooling, labor, and thousands of finished products already committed before a serious problem is discovered.

Ultimately, the better question isn't simply, “How quickly can we start mass production?” It's: “How quickly can we reach mass production that is predictable and consistent?”

 

Topics Discussed

Why Chinese manufacturers are commercially motivated to reach mass production

When moving quickly into production may carry relatively low risk

Why new and customized products need their own manufacturing and testing processes

How to assess whether a supplier is really capable of supporting NPI

The dangerous assumption that a manufacturer of similar products can automatically develop yours

Why buyers also knowingly skip NPI steps

How deadlines, customer commitments, and funding pressure influence decisions

The financial risk of committing components and materials too early

What happens when problems appear after thousands of units have already been produced

Why progressive pilot runs reduce manufacturing risk

The difference between reaching mass production quickly and reaching stable mass production

When adapting an existing product can reduce development and industrialization risk

 

Related content

Sofeast – Transitioning to Manufacturing from Product Development | 2 Options

Sofeast – The NPI Process: Trouble Awaits If You Skip Its Steps!

Sofeast – Planning For Effective Pilot Runs

Sofeast – Discussing the NPI Process for Effective Product Development

Get in touch with Sofeast Connect with us on LinkedIn

Contact us via Sofeast's contact page

Subscribe to our YouTube channel

Prefer Facebook? Check us out on FB

Poor communication can quietly derail a hardware project long before anyone realizes there is a problem.

In episode 347 of China Manufacturing Decoded, Adrian and Paul investigate how information moves from the customer’s Product Requirements Document through design, engineering, purchasing, production, and suppliers, and how misunderstandings or unspoken assumptions at any of those handoffs can eventually turn into expensive hardware problems.

Unlike software, where an error can often be corrected relatively quickly, a misunderstanding in a hardware project might not become obvious until a prototype has been built, tooling has been made, components have been ordered, or production is already underway.

They'll discuss why communication needs to be a two-way process rather than simply passing instructions downstream. Teams need to question unclear requirements, confirm what they have understood, expose assumptions, and send questions back upstream before work continues.

Finally, they also look at the problems caused by changes during development and pre-production. Even seemingly minor changes can affect tooling, components, inventory, cost, lead times, and scrap, making formal change control essential.

 

Topics Discussed

Why hardware projects are particularly vulnerable to communication problems

How assumptions creep in as requirements move between teams

Why simply acknowledging receipt of a requirement is not enough

How a Product Requirements Document should act as the project's single source of truth

Why technical terminology, units, and language differences can cause costly misunderstandings

How two-way requirements reviews help expose problems earlier

Why suppliers should question unclear requirements rather than blindly following them

Which internal teams should be involved in regular project communication

Why mid-project engineering changes can have major downstream consequences

How formal change control protects cost, quality, and delivery schedules

 

Related content

Sofeast - Importing from China? Use this product specifications template.

Sofeast - Good and Bad Methods of Communication with your Chinese Supplier [Podcast]

Sofeast - Why Hardware Projects Stall: Avoiding ‘Failure to Launch’ [Podcast]

QualityInspection.org – Product Requirements Document: Underpinning Hardware Product Development

 

Get in touch with Sofeast Connect with us on LinkedIn

Contact us via Sofeast's contact page

Subscribe to our YouTube channel

Prefer Facebook? Check us out on FB

What should you really be designing a new product for?

In this CMD Gold episode, we revisit episode 99, where Renaud Anjoran and reliability expert Andrew Amirnovin explore Design for X (DfX), the practice of designing a product around specific objectives that go far beyond simply making it function.

They examine 12 areas where products can be deliberately optimized, including shorter development times, crowdfunding, manufacturing, assembly, quality, packaging, reliability, maintainability, ergonomics, fewer SKUs, and sustainability.

Along the way, they explain why simplifying products, reducing part counts, using proven components, mistake-proofing assembly, considering the real-world use environment, and involving the right specialists early can prevent costly problems later.

The key message is that DfX is not about maximizing every possible objective. Different products have different priorities, and some objectives involve trade-offs. What matters is identifying the right ones early enough in development that you still have the freedom to make changes.

 

Show Sections

00:13 – Introduction: Revisiting Design for X

01:46 – Design for shorter development and time to market

04:26 – Designing for crowdfunding

07:12 – Design for Manufacturing and Design for Assembly

11:43 – What should product designers consider from the start?

15:57 – Fewer parts, standard components, and mistake-proofing

19:23 – Modularization and simplifying assembly

23:35 – Design for quality

30:52 – Why packaging must be considered during product design

34:06 – Design for reliability

42:58 – Design for maintainability

46:48 – Design for ease of use and ergonomics

47:07 – Design for fewer SKUs

47:53 – Design for sustainability

48:41 – Which DfX objectives matter most?

49:24 – How to implement Design for X in practice

50:53 – Using expert design reviews

51:23 – Adrian's present-day takeaways

 

Related content

Agilian - DfX, Industrialization & NPI Support

Sofeast - The New Product Introduction Process Guide

QualityInspection.org – How Good DFM and DFA Help with Production Cost & Quality

QualityInspection.org – The Design for Reliability Process for Launching Reliable Products

QualityInspection.org – Don’t Leave Packaging Until the End

Agilian – Why Test Components and New Products to Failure During NPI?

Get in touch with Sofeast Connect with us on LinkedIn

Contact us via Sofeast's contact page

Subscribe to our YouTube channel

Prefer Facebook? Check us out on FB

When you send a manufacturer your CAD files, drawings, specifications, and requirements, you might expect them to review everything and simply come back with a price and lead time.

But an experienced manufacturing team will often respond with something else first: questions. Lots of them.

In episode 345 of China Manufacturing Decoded, Adrian is joined by Agilian's Paul Adams to explain why those questions are an important part of preparing a product for manufacturing, not an unnecessary delay.

They discuss what manufacturers are trying to understand about your product, including its function, operating environment, mating parts, tolerances, materials, production volumes, surface finishes, and inspection criteria. Paul also explains how seemingly small assumptions can become embedded in a product specification and ultimately lead to higher costs, excessive rejection rates, rework, tooling modifications, delays, or products that do not perform as expected.

You'll also learn what information buyers should provide when requesting a quotation, why detailed 2D drawings remain so important, how experienced manufacturers' questions differ from superficial ones, and how the questions you ask can help you assess the capability of a potential manufacturing partner.

As Paul puts it: smart questions at the start are cheaper than solving problems at the end.

 

Show Sections

00:13 - Introduction: Why do experienced manufacturers ask so many questions before quoting?

02:39 - Why manufacturers need to ask questions before giving firm answers

07:37 - What manufacturers need to understand about your product

10:29 - Mating parts, fit, and tolerance stack-ups

12:45 - Why inspection and cosmetic criteria must be specific

16:25 - What happens when important questions are skipped?

20:26 - How assumptions lead to failures, rework, and extra cost

24:51 - What buyers should provide when requesting a quotation

27:10 - Why detailed 2D drawings, finishes, welding, and CTQs matter

30:13 - How experienced manufacturers ask better questions

35:28 - Managing component lead times during development

38:59 - Smart questions at the start are cheaper than problems at the end

41:36 - Why silence from either side is a warning sign

43:01 - Using questions to evaluate a manufacturer’s capability

45:37 - Key takeaway: good questions reduce manufacturing risk

 

Related content

How To Get A Quotation For Manufacturing Your New Product?

The New Product Introduction Process Guide

DfX, Industrialization & NPI Support from Agilian

Plastic Injection Molds: 8 Tips For When Requesting Quotes

Questions to Ask Your Tooling and Plastic Supplier to Reduce Risks

Get in touch with Sofeast Connect with us on LinkedIn

Contact us via Sofeast's contact page

Subscribe to our YouTube channel

Prefer Facebook? Check us out on FB

Adrian is joined by Lee Bryan, founder and CEO of Arcus Compliance, to examine a common assumption among companies manufacturing products in China: if the supplier says a product is compliant, provides a CE certificate, or says they have made similar products before, can you rely on that?

The discussion covers increasingly automated regulatory enforcement, why compliance needs to be considered during product development rather than after launch, how AI can help companies understand regulatory requirements, why supplier certificates should be independently verified, how compliance can become a competitive advantage, and what happens when a V2 product introduces component or design changes. Lee's core advice is simple: trust, but verify. Arcus currently identifies Lee Bryan as its founder and CEO.

 

Show Sections

00:00:13 - Introduction: Can you prove your product is compliant? and guest, Lee Bryan of Arcus Compliance

00:04:58 - Why product compliance enforcement is increasing

00:08:47 - The real risks of getting compliance wrong

00:10:01 - Why checking compliance after launch is too late

00:16:11 - When should compliance enter the product development process?

00:17:36 - Compliance challenges for SMEs versus large companies

00:21:52 - Building compliance into product development

00:22:58 - Can AI help you understand regulations?

00:26:18 - Can you trust your Chinese supplier on compliance?

00:28:05 - Why certificates and test reports must be verified

00:29:35 - Turning compliance into a competitive advantage

00:33:56 - Does a V2 product need to be tested again?

00:37:19 - What should be checked before tooling and mass production?

00:41:14 - The key takeaway: compliance responsibility sits with you

00:41:49 - Lee's book, The Compliance Edge

 

Related content

Why YOU Need a Product Safety Program

11 Common Electronic Product Certification And Compliance Requirements

Reliability vs. Compliance: Both Matter Equally for Your New Product Launch

Importing into the EU: Product Compliance is More than Test Reports

How To Verify that a Component’s FCC or CE Certificate is Legitimate?

Visit Lee's site: Arcus Compliance and connect with him

Read Lee's recent book for free: The Compliance Edge (PDF download)

Get in touch with Sofeast Connect with us on LinkedIn

Contact us via Sofeast's contact page

Subscribe to our YouTube channel

Prefer Facebook? Check us out on FB