Don't wait for a prototype to get traction. Hardware founders should first engage potential customers and demonstrate a profound understanding of their specific problems. This expertise builds the necessary trust for customers to commit, even before a physical product is ready.

Instead of building its final passenger jet, Boom first developed a smaller, sub-scale prototype to prove its Mach 2.2 technology. This startup-like, sequential approach proves the core concept at a much lower cost, making the capital-intensive project more manageable and fundable.

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.

To successfully launch new business lines, established companies should act like startups again. Airbnb found success by piloting new services in just one city, perfecting the model with a small user base, and only then scaling. This shrinks the problem and accelerates learning.

Before committing large sums to a volatile market, companies should launch a small business like a portable feed mill. This allows them to learn the real operational challenges and unwritten rules with minimal financial exposure before scaling.

Don't build a perfect, feature-complete product for the mass market from day one. It's too expensive and risky. Instead, deliver a beta to innovator customers who are willing to go on the journey with you. Their feedback provides crucial signals for a more strategic, measured rollout.

Instead of a full launch, enable only the sales team most vocal about a new product to sell it. This controlled experiment tests real-world demand and cannibalization risk with minimal investment and market disruption before committing to a wide release.

Hardware startups must not wait for physical prototypes to get customer feedback. Steve Blank advocates for creating 'digital twins'—advanced, interactive simulations—that customers can use. This allows for rapid iteration and customer discovery, mirroring the agility of software development.

The software-centric Minimum Viable Product (MVP) model is ill-suited for hardware. Instead of aiming for a 'viable' product, focus on a 'testable' one. This allows for controlled pilot deployments to gather real-world data and iterate before committing to expensive, hard-to-change physical designs.