DEV Community

VIRA.space
VIRA.space

Posted on Originally published at vira.space

Reimagining MVP for Hardware: Lessons from Space Startups

Lean Startup principles suggest rapid iteration, but hardware like satellites can't be patched once launched. The concept of a 'minimum viable product' (MVP) must adapt for hardware startups, especially in space. As outlined in the EU Space Academy's course, it's crucial to validate the problem, buyer, and business model on the ground before investing in physical builds. Unlike software, where feedback loops can happen quickly, hardware MVPs face unique constraints such as tooling choices and procurement lead times.

The course highlights three product formats: pure hardware, pure software, and hybrid IoT products, each with distinct risk profiles. For example, Earth Automations, with its hardware-heavy autonomous robot, faces long lead times, while Spottitt operates purely on software analytics using existing data. Understanding your product's format is essential for applying MVP principles effectively.

A hardware MVP must be fully functional, not just a stripped-down version. The course emphasizes that an MVP should pass the feasibility, viability, and desirability tests, using relatable examples like Juicero to illustrate the pitfalls of assuming a product is desirable based on technology alone. The Wavemapper case study exemplifies the iterative process of discovering market fit through customer feedback rather than repeated physical iterations. To mitigate risks, startups should conduct formative and summative testing before committing to hardware builds, ensuring the MVP loop runs through interviews and mock-ups instead of physical revisions.


Originally published at vira.space.

Top comments (0)