We scan new podcasts and send you the top 5 insights daily.
Moving from software to physical goods is a 'night and day' difference for a PM. Key challenges include long development cycles, the inability to push updates post-launch, and the need to translate designs for human builders on a manufacturing line, not just developers.
Unlike software’s iterative nature, hardware decisions are "one-way doors." Choosing a component is a multi-million dollar commitment. The risk is amplified because giants like Apple can absorb the entire global supply of a single part, forcing smaller companies into costly redesigns overnight.
Even with a successful playbook from a company like Zoom, a marketing leader must adapt significantly when moving to a new context. Selling a physical product globally introduces complexities like homologation, customs, inventory, and channel sales that require eating 'humble pie' and learning the new business from the ground up.
Software companies struggle to build their own chips because their agile, sprint-based culture clashes with hardware development's demands. Chip design requires a "measure twice, cut once" mentality, as mistakes cost months and millions. This cultural mismatch is a primary reason for failure, even with immense resources.
Unlike software, Halter's livestock management hardware required a five-year development cycle to solve fundamental technical challenges like power, connectivity, and animal training before the company could even begin to scale.
Unlike software, hardware iteration is slow and costly. A better approach is to resist building immediately and instead spend the majority of time on deep problem discovery. This allows you to "one-shot" a much better first version, minimizing wasted cycles on flawed prototypes.
Unlike pure software, building software for a physical product imposes immovable deadlines dictated by hardware manufacturing and shipping lead times. This forces software teams to abandon flexible, continuous iteration in favor of a highly-focused, delivery-oriented mindset to ensure the software is ready when the hardware is.
Unlike software's daily compilations, hardware development allows only a few "compiles" (builds) in total. This necessitates a more conservative, upfront process focused on reliability and planning, as you can't ship over-the-air updates to fix physical products.
To ensure a smooth transition from development to production, an operations or manufacturing SME must be part of the design process from the start. Otherwise, products are developed without manufacturability in mind, leading to expensive, reactive fixes and subjective quality control during scale-up.
Boom Supersonic accelerates development by manufacturing its own parts. This shrinks the iteration cycle for a component like a turbine blade from 6-9 months (via an external supplier) to just 24 hours. This rapid feedback loop liberates engineers from "analysis paralysis" and allows them to move faster.
Hardware innovation culture is fundamentally different from software. Founders must be intrinsically motivated by the slow, deliberate, and expensive process of creating physical things. The reward is not quick iteration but conquering the immense difficulty of a process where mistakes are very costly.