Milan Cerovic | Strategies for Succeeding at New Product Development

Being an Engineer · 7 Apr 2023 · 50m · Episode 14

What this episode covers

Milan Cerovic, VP of R&D at Wrap and former NPD manager at Taser (now Axon), shares strategies for successful new product development, emphasizing the importance of clear requirements and early prototyping. He discusses his work on the BallWrap 150 and the origin of Taser's body-worn cameras, highlighting how physical prototypes helped define user needs and functionality. Cerovic advises engineers to balance industrial design with mechanical engineering, use tools like SolidWorks and KeyShot for visualization, and maintain organized, focused workflows to avoid common pitfalls like scope creep and poor communication.

Other shows on the same ground, closest first.

  • Product Startup · 25m

    149: How to Professionally Prototype your Invention Idea

    Mike Morton, former Senior Principal Industrial Designer at Dell, HP, and Sunbeam, explains the critical role of prototyping in product development. He details the progression from rough mock prototypes to refined mechanical and pre-production samples, emphasizing that early, iterative testing prevents costly errors in tooling and manufacturing. Morton advises startups to involve manufacturers early in the design process to ensure designs are manufacturable and to use short pilot runs to validate the production line before full-scale launch.

  • Product Startup · 27m

    216: 5 Key Tips For Starting Your Product Development Journey

    Wade Harmidy, a Six Sigma Black Belt project manager at MAKO Design + Invent, outlines five critical strategies for hardware startups to increase their chances of success during the early product development phase. He emphasizes the importance of defining a clear product vision, understanding the end user, and adhering to Minimum Viable Product (MVP) principles to reduce waste and accelerate time to market. Harmidy also stresses the necessity of setting realistic timelines to avoid cutting corners and planning for the big picture, including manufacturing and business goals, from the outset.

  • Embedded.fm · 1h 05m

    269: Ultra-Precise Death Ray (Repeat)

    Alan Cohen, a systems engineer at Massachusetts General Hospital and author of 'Prototype to Product: A Practical Guide for Getting to Market', discusses the 'eleven deadly sins' of product development. He emphasizes that detailed planning and requirements gathering are essential for managing risk and avoiding costly surprises, arguing that the cost of changes increases exponentially over time. Cohen advocates for an 'iterative waterfall' approach that balances agile iteration with structured gates, and highlights the importance of building strong, motivated teams to execute these plans effectively.

  • The Amp Hour · 1h 12m

    Interview with Eric Ries - Transorted Testing Tachydidaxy

    Eric Ries, author of The Lean Startup, discusses applying lean manufacturing principles to product development, emphasizing rapid experimentation and the Minimum Viable Product (MVP). He explains how hardware companies can use mockups, soft tooling, and service contracts to iterate quickly and validate customer demand before committing to expensive hard tooling. Ries argues that internal risks and bureaucratic silos are the primary barriers to speed, not technical constraints, and that companies must pivot their management systems to handle uncertainty.

  • Product Startup · 38m

    164: The 3 Prototyping Phases for New Product Development

    Tim Uys, Head of Design at Mako Design + Invent, outlines the three critical phases of prototyping for hardware startups: mock, mechanical, and refined prototypes. He explains that starting with low-cost 3D printed mockups allows for rapid iteration of form and ergonomics, while mechanical prototypes use higher-fidelity methods like CNC machining to validate complex functions and material strength. Uys emphasizes that a final refined prototype is essential for securing manufacturing partners and investors, as it proves the product's viability and reduces the risk of costly errors during mass production.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by Being an Engineer. The episode itself belongs to its publisher.