Why Version 1 Shouldn’t Be Perfect (And What to Do After You Launch)

Some product manufacturers treat launch as the end of the journey. It isn’t. In episode 325 of China Manufacturing Decoded, Adrian and Renaud break down a powerful idea from Tony Fadell: “Builders build, ship, then solve what breaks.” They explore what really happens after a product hits the market, and why chasing perfection before launch can actually kill your chances of success. You’ll learn: Why over-engineering delays launches (and increases risk) How Version 1 should really be defined: simple, lovable, and complete What real-world users reveal that prototypes never can How to collect meaningful feedback without damaging your reputation Why early adopters are critical for innovative products How smart teams build Version 2 while Version 1 is still launching Developing a new product in 2026? You'll have food for thought from this one!   Sections 00:13 — Episode overview 00:37 — Tony Fadell’s quote 01:37 — Why perfection is a trap 04:28 — Engineering vs speed trade-off 06:30 — Launch early vs over-engineering 07:46 — De-risking with Version 1 10:30 — “Simple, lovable, complete” 13:43 — Launch isn’t the finish line 15:04 — Real-world user behaviour 17:06 — Nest example (unexpected insights) 19:36 — Managing reviews & early releases 21:27 — Choosing the right early users 24:02 — Misinterpreting “ship early” 25:47 — Lessons from product reliability 26:56 — Why post-launch work matters 28:28 — Continuous product development 30:25 — Key takeaways Related content Tony Fadell's LinkedIn post How to Manufacture a New Product with the Customer Journey in Mind Buy the book: Build: An Unorthodox Guide to Making Things Worth Making A Logical Development Roadmap for New Hardware Products   Get in touch with us Connect with us on LinkedIn Contact us via Sofeast's contact page Subscribe to our YouTube channel Prefer Facebook? Check us out on FB