Product development, engineering, and toy R&D from South China.
I’m Leon, a product development and R&D professional based in South China.
My career spans more than a decade across electronics engineering, intelligent hardware, technical project management, and physical product development. In recent years, most of my work has focused on toys, juvenile products, and ODM/OEM development for international markets.
I am not purely a product manager, and I am not purely an engineer.
My work sits somewhere between product, engineering, manufacturing, and problem solving.
What I do best is help turn an idea into a product that can actually be engineered, costed, prototyped, tested, tooled, and manufactured.
From Engineering to Product Development
My career began with electronics engineering, device software, and intelligent hardware.
My early work involved electronic systems, device software, Linux, Android, system integration, hardware platform adaptation, and customized electronic products.
That engineering background gave me a habit that still shapes how I work today:
Do not stop at what a product is supposed to do. Understand how it will actually work.
Later, my work expanded into intelligent hardware, connected devices, mobile applications, field-deployed systems, and multidisciplinary technical projects.
Over time, I moved from solving individual engineering problems to managing the entire product development path:
- What should this product actually do?
- Is the idea technically realistic?
- Which technical architecture makes the most sense?
- Which decisions could make the cost spiral out of control?
- What should be validated first?
- What is most likely to go wrong after tooling begins?
- Which supplier claims should be questioned further?
- What could become a problem during mass production?
That transition eventually brought me into toy and juvenile product development.
What I Do Today
Today, much of my work involves ODM and OEM product development.
I have worked across projects involving:
- Product concepts and feature definition
- Industrial design review
- Mechanical structure
- Electronics
- Electronic systems, firmware, and device software
- Mobile apps and connected products
- Audio and music integration
- Prototype development
- Supplier coordination
- BOM and cost review
- Tooling and mold development
- Testing and compliance preparation
- Production troubleshooting
- Mass-production handoff
I have worked with multidisciplinary teams across industrial design, mechanical engineering, electronics, software, purchasing, suppliers, testing, and manufacturing.
I have also worked directly with overseas customers and international brands, helping translate product ideas and business requirements into solutions that engineering and manufacturing teams can actually execute.
Where I Add the Most Value
For me, the most valuable part of the work is usually not producing a drawing, writing code, or creating a specification.
It is making decisions across disciplines.
A product may look simple from the outside, but real development usually requires balancing:
appearance, function, structure, electronics, software, cost, safety, tooling, supplier capability, schedule, and production risk.
Many of the most expensive mistakes in product development happen at these intersections.
A small cosmetic change may require a new mold.
A seemingly simple electronic feature may increase cost, testing complexity, power consumption, or failure risk.
A prototype that works successfully does not necessarily mean the product is ready for mass production.
A supplier may say something is “necessary” when, in reality, it is simply the process they are most comfortable using.
A low quotation may become expensive after tooling changes, rework, delays, failed testing, or quality problems.
These are the kinds of product development problems I find most interesting.
Product Feasibility
One of my strongest skills is quickly identifying whether a product idea is realistic.
When reviewing a new concept, I naturally think about questions such as:
- Can this feature actually be implemented?
- Is the mechanism unnecessarily complicated?
- Can the target cost support the current design?
- Is the supplier using the right process?
- Are there hidden tooling costs?
- Is the product likely to face testing or compliance issues later?
- Which problems may be acceptable in a prototype but dangerous in mass production?
- Which issues should be solved before money is committed to tooling?
The earlier these questions are answered, the cheaper they usually are to fix.
Engineering & Manufacturing Problem Solving
A large part of real-world R&D is dealing with problems that were never in the original plan.
A supplier cannot achieve the required effect.
A material behaves differently from expectations.
An electronic module suddenly creates a new compliance issue.
A mechanism looks fine in CAD but does not work reliably in a physical sample.
A production process introduces unacceptable variation.
A quotation does not make sense.
Prototype schedules begin to slip.
In these situations, I usually combine technical investigation, supplier discussions, testing, documentation, and alternative-solution research to find a practical path forward.
I have spent years doing exactly this kind of work.
Bridging Overseas Product Ideas and Chinese Manufacturing
Another important part of my experience is communication.
Overseas customers, designers, engineers, suppliers, and factories often describe the same product in completely different ways.
The customer focuses on the user experience.
The designer focuses on appearance.
The engineer focuses on implementation.
The supplier focuses on process limitations.
The factory focuses on consistency and production efficiency.
Good product development requires translating between these perspectives.
I often act as that bridge.
My work frequently starts with a vague requirement: understanding what the customer really wants, identifying the technical implications, and then turning that requirement into something suppliers and engineering teams can execute.
Experience Across the Full Development Cycle
I have participated in and managed dozens of physical product development projects.
The exact workflow varies, but many projects follow a path similar to this:
Idea → Product Definition → Engineering → Prototype → Testing → Revision → Tooling → Pilot Production → Mass Production
Once you have worked across the full development cycle, the way you evaluate early-stage decisions changes.
You stop asking only:
Can we make this?
And start asking:
Can we make it consistently?
Can we make it at the target cost?
Can it be tested reliably?
Can the factory assemble it efficiently?
Can the design tolerate normal mass-production variation?
Will the product still work reliably once the first prototype is no longer being handled by the engineer who built it?
That perspective is a major part of what I bring to ToyRD.
Why I Created ToyRD
There is already an enormous amount of information online about manufacturing in China.
The problem is that much of it tends to fall into a few categories:
- Generic sourcing advice
- Factory marketing content
- Retail-focused product development articles
- Simplified summaries that skip engineering reality
- AI-generated explanations based mainly on other online explanations
ToyRD exists for a different reason.
I wanted a place to document the practical side of real product development:
- Why mold quotations change
- Why suppliers miss prototype deadlines
- Why a design that looks simple can become expensive
- How BOM decisions affect product cost
- Where engineering and manufacturing teams misunderstand each other
- What usually goes wrong between prototype and production
- How to think about an ODM project before committing significant money
The goal is not to make manufacturing sound easy.
The goal is to make it easier to understand.
What ToyRD Is — and Is Not
ToyRD is an independent personal knowledge project.
It is not a factory.
It is not a trading company.
It does not represent my employer, past employers, customers, suppliers, or any other organization I have worked with.
When I discuss development problems, supplier behavior, engineering decisions, tooling, cost structures, or project lessons, I deliberately generalize or anonymize identifying details.
Some examples may combine patterns from multiple projects rather than describe one specific commercial project in full.
The purpose is to explain how product development works, not to expose confidential business information.
A Practical View of Product Development
I do not believe there is a universal formula for developing a good product.
Every project has different constraints.
But after years of working across engineering, product development, suppliers, and manufacturing, I have found that a few principles repeat themselves:
Resolve expensive uncertainty as early as possible.
Do not confuse a working prototype with a manufacturable product.
Understand why a supplier recommends something before accepting the recommendation.
Cost, engineering, compliance, and production should not be treated as separate conversations.
A good product decision is usually a balance between multiple constraints, not the optimization of one.
These are the kinds of ideas I continue to explore on ToyRD.
Work With Me
From time to time, I also help product teams, founders, and brands think through development problems involving toys, juvenile products, intelligent hardware, and China-based manufacturing.
Typical areas include:
- Product feasibility reviews
- Supplier quotation and BOM reviews
- Prototype and engineering reviews
- ODM/OEM development strategy
- Manufacturing risk identification
- Technical troubleshooting
- Product development planning
- Technical communication between overseas teams and Chinese suppliers
If you are developing a physical product and want an independent technical and manufacturing perspective before committing more time or money, ToyRD may be useful.
Independence & Confidentiality
I’m Leon, the author of ToyRD.
ToyRD is an independent personal knowledge project and does not represent my employer, customers, suppliers, or any organization I have worked with.
The experience shared here comes from real product development and manufacturing work. To respect commercial confidentiality and professional relationships, I intentionally remove, combine, or generalize details that could identify specific companies, customers, suppliers, or projects.
What matters to me is documenting the decision-making methods, engineering logic, and manufacturing lessons behind real projects — not telling the story of any one specific company.
This approach allows me to discuss real product development problems more openly while maintaining the professional boundaries that should remain in place.
ToyRD
Real-world product development, engineering, and manufacturing notes from South China.
For collaboration or project review requests, please use the contact page.