The situation
A founder I spoke with had been manufacturing a consumer hardware product through suppliers in China for several years.
He didn't come from a hardware background, so he leaned on people with more experience to establish the supply chain. He had trusted contacts who helped select factories, manage production, and work through issues as they came up.
The arrangement worked. They had completed several production runs and continued increasing the quantity as they validated changes to the product. Most of the founder's interaction with manufacturing still happened through a small number of people remotely.
The plan
As the company prepared for another production run, the founder planned a trip to China to visit the people and suppliers he had been working with.
The purpose was largely relationship driven. He wanted to meet them in person, spend time together, and strengthen the relationships as the company prepared for future orders.
The timing gave him another opportunity. Production had been delayed, so when he arrived, his product was still being built. He was able to follow it through parts of the manufacturing process and spend time with the people doing the work.
Where uncertainty remained
From home, the manufacturing process had been fairly simple from his perspective. He would communicate what he needed to his main contact, who coordinated the factories and came back with finished product.
On the factory floor, he saw everything happening behind that interaction.
There were engineering teams supporting different parts of the process, equipment being set up and calibrated, custom fixtures being built, inspections being performed, and testing happening throughout production. He started seeing how many individual steps had to work correctly for finished product to come out the other side.
That also made some of the delays and manufacturing problems easier to understand. There were more places for something to go wrong than he had been able to see while managing the process remotely.
What needed to be proven first
Their production testing wasn't catching one of the failure modes, which was contributing to fallout during the build. The founder came away with a stronger appreciation for defining the testing and validation process before continuing to scale production.
He also watched operators struggle with soldering the battery into a tightly packed assembly. Their approach was putting nearby components at risk of damage. Because he had experience assembling the product himself, he suggested changing the direction they approached it from. The factory adopted the change and reduced the problem.
Other discoveries happened away from the production line. He sat with an engineer at his battery supplier and worked through how to get more from the limited space available in the product. At another supplier, he could evaluate enclosure samples in person and make a design decision while new samples were being produced.
Even communication changed. He learned that one of the people he had worked with for years struggled with email. They switched to voice messages, and conversations that had previously stretched over days began moving much faster.
The pattern
When you manufacture remotely, a lot of the process can become compressed into updates, samples, quotes, and finished units. That can make it difficult to see the decisions, constraints, testing, and failure points behind those outputs.
At Hardware Velocity, we look at how the product is being built and tested, where failures can occur, and what needs to be resolved before committing to a larger build.