hn.today

Stop Blaming Hardware for Not Validating

pawelbrodzinski.substack.com4 points0 comments
Screenshot of Stop Blaming Hardware for Not Validating

Hardware founders often build prototypes that look and work too much like finished products, spending money before they know whether customers want them. The same scrappy validation tactics used in software apply: aim to spend roughly 10% of the planned build budget, which forces a rethink rather than a simple feature-cutting exercise. Choose the one assumption that is both most uncertain and most capable of sinking the business, then test it directly. Tesla, for example, used a Lotus body for its first car so engineers could concentrate on the battery - the central uncertainty in making an electric car viable.

When hardware is costly or difficult to install, validation need not begin with a full device. Landing pages, preorders, scaled-down versions, and combinations of off-the-shelf parts can reveal demand and support further funding. A prototype can also be far simpler: PDA pioneer Jeff Hawkins tested whether people would adopt a handheld organizer by carrying a wooden block and pretending to use it. A soil-monitoring service could start with a person testing samples and texting farmers, revealing whether the information changes their behavior before any sensor is built. Prototypes are disposable experiments, not miniature products: they need not scale, withstand the elements, or be economically viable. Their purpose is to generate useful evidence about customer interest, behavior, and technical feasibility.

Read on pawelbrodzinski.substack.com0 comments on Hacker News

Summary generated by AI from the linked article. hn.today is not affiliated with Hacker News or Y Combinator.

More in Startups

The daily digest

Today's best Hacker News stories, summarized and screenshotted, one email a day.