I now use three screening standards for hardware product concepts. They're brutally simple, and they work particularly well when you're developing physical products for consumer or industrial markets.

The first test is the thirty-second explanation rule. Can you explain to a stranger what problem this product solves in half a minute? Not what it does or how it works, but what specific pain point it addresses.

Last month I met with a team developing a smart thermostat for industrial warehouses. They spent ten minutes explaining sensor arrays, predictive algorithms, and cloud connectivity before I stopped them. I asked what problem it solved. After an awkward pause, someone said "energy waste." That's not specific enough. Compare that to how Nest explained their home thermostat in 2011: "Your heating bill is high because you forget to adjust your thermostat when you leave. This learns your schedule and does it automatically." Problem, consequence, solution. Thirty seconds.

If your team can't pass this test, your product concept isn't clear enough yet. And if your own people can't explain it simply, your sales team never will, and your customers certainly won't understand why they need it. This applies whether you're making consumer electronics or industrial machinery. A confusing value proposition kills products before they launch.

The second standard is what I call the believability threshold. When you describe this product concept to someone in your target market, do they immediately think "yeah, that could work" or do they look skeptical? You're not asking if they'd buy it yet. You're testing if the basic premise makes intuitive sense.

I once evaluated a concept for warehouse safety equipment that used AI to predict accidents. Sounds high-tech, impressive even. But when we described it to warehouse managers, they all had the same reaction: "How would it know?" They couldn't visualize how the technology would actually function in their environment. The concept failed the believability test not because it was technically impossible, but because the gap between current reality and the proposed solution was too large for customers to bridge mentally.

Contrast that with a successful industrial product concept I saw last year: rugged tablets with genuinely long battery life for field technicians. Everyone immediately got it because the problem was obvious and the solution was straightforward. No mental gymnastics required.

The third filter is resource reality. Can your team actually build a viable version of this product with the resources you have access to in the next twelve months? Notice I said viable, not perfect. I'm not talking about your dream version with every feature. I mean a functional product that delivers the core value proposition.