The Death of the MVP in Hardware

In software, the "Minimum Viable Product" (MVP) is a celebrated milestone. Push code, see what breaks, patch it later. It’s a philosophy of speed and iteration.

In hardware, that philosophy is a death sentence.

Atoms > Bits

When you ship a physical product, there is no "patch Tuesday." There is no hotfix. If a hinge fails, if a battery overheats, or if a finish peels, you are looking at a recall. Recalls kill companies.

The cost of an iteration in software is nearly zero. The cost of an iteration in hardware is:

1. Tooling modifications ($10k - $100k)
2. Inventory write-offs (the bad units involved)
3. Brand trust (irreparable)

The "Minimum Viable Experience"

Instead of an MVP, hardware startups should aim for a Minimum Viable Experience (MVE).

An MVE acknowledges that detailed specs might change, but the core promise of the device must be robust from Unit 1.

1. Robustness is not optional

A "buggy" app is annoying. A "buggy" medical device or consumer appliance is dangerous. Your "minimum" bar must include safety, thermal stability, and mechanical integrity.

2. Finish is the feature

In a digital world, we forgive ugly UIs if the utility is high. In the physical world, we judge quality by weight, texture, and seam lines. If your "MVP" feels cheap, your brand is defined as cheap forever.

How to execute an MVE

We advise our clients to:

1. Front-load validation: Spend more on EVT (Engineering Validation Test). Break prototypes in the lab so they don't break in the field.
2. Cut features, not quality: It is better to ship a device that does one thing perfectly than a device that does five things poorly.
3. Respect the BOM: Don't design a $500 experience for a $50 BOM. Align your unit economics early.

Conclusion

Stop trying to "move fast and break things" in hardware. Move deliberately and build things that last.