“Prototype success” is the trap.
How the right questions turn failure into success
In EVT, your 3D‑printed + BreadBoard build “works.”
Everyone relaxes. And that’s exactly where expectations go to die.
The first product I ever developed was a small autonomous fan for camping tents.
Solar powered, clipped to the tent zipper, turned on automatically when it got too hot inside.
Our tests showed we could extend sleep by ~4 hours during hot festival mornings. We planned to sell it for 9,99€ to hungover teenagers at music festivals. At 21, it felt like we’d cracked it.
Electronics on a prototype PCB? Done.
3D‑printed casing? Done.
Off‑the‑shelf fan? Working.
EVT “passed.” We thought we were almost at the finish line.
We couldn’t have been more wrong.
The real problems showed up the moment we tried to make it a manufacturable product:
Sourcing the smallest, quietest fan that actually fit our footprint at low volumes and sane costs.
Redesigning electronics so assembly wasn’t a cable-routing nightmare.
Creating a clipping mechanism that drunk teenagers could use, in the dark, without cutting themselves.
Making the enclosure compact, robust, and still easy to repair, refurbish, and eventually recycle.
Finding manufacturers who could hit cost, quality, and timelines… and backup suppliers when they couldn’t.
Adapting the design to different manufacturing technologies and volumes without starting from scratch.
Planning for audits, certifications, and all the fun compliance acronyms.
We hadn’t designed for any of that!
So even with a working prototype and a patent… the product still hasn’t seen the light of day.
That’s the difference between a feature that works and a product that wins.
If you’re a manufacturing / ops leader, “EVT success” is not the signal to relax.
It’s the signal to start asking harder questions:
Can we build this at target yield, with real‑world suppliers, at the planned volume?
Is the architecture as simple as it can be… and no simpler?
Have we designed for usability, assembly, service, repair, and end‑of‑life, not just for the demo table?
Do we actually have the time, budget, and partners lined up for DVT, PVT, and beyond?
And this is where experience actually matters.
Seasoned manufacturers kill products before they ever see a prototype. Not because the problem isn’t real. Not because the solution wouldn’t be valuable. But because they can already see the graveyard down the line.
So the real question becomes:
How do we ask the right questions before we spend months and hundreds of thousands on development?
What are those questions?
And where is the line between “over‑planning” in the abstract and “charging ahead blind” into failure?
I’ve tested both sides of that line.
I tried discovery questionnaires with 100+ questions.
On paper it looked rigorous. In practice: too much effort for our customers, not enough time, spiked anxiety, and pushed back kick‑off dates.
With a medical device client, we suggested a technical audit to their technology before “just making it smaller.”
They refused. They only wanted miniaturization. And we accepted the job without the audit.
End result: more than €1M and 2 years invested in a product built on wrong assumptions.
So no, you don’t need 100 questions.
But you do need a small set of non‑negotiable ones, asked early, and answered honestly.
For me, they cluster into four buckets.
1. Function: What should the product do and how do we test it properly?
If your test protocol is biased, your product will fail.
If you don’t invest in test software, jigs, or benches, you’ll miss critical behaviors and workflows.
If you’re not clear on non‑negotiables vs “nice to haves,” priorities will stay vague and either timelines slip or budgets explode.
2. User: Who will use the product and what actually matters to them?
If you start development without real conversations with real users, you’ll build a beautiful solution to a fictional problem.
Your bias (“this is obviously great”) is the fastest way to ship something impressive that nobody wants.
3. Safety & Compliance: What certifications will the product, company, and suppliers need to sell?
This is where many teams blow up.
Certification can instantly disqualify your preferred manufacturer.
It can mean months or years of bureaucracy, factory audits, and redesigns of electronics and mechanics.
It often means multiple rounds of failed qualification before you get a passing design.
4. Business Requirements: What does success look like in time, cost, and volume?
When must the product be ready to hit real sales cycles and market windows?
What unit price do you actually need?
What are the expected orders in years 1, 2, and 3?
Inside many clients, sales, marketing, engineering, and procurement each carry their own private version of these answers. Because of that, the product gets a 12‑month roadmap, but no one checks that it misses a critical trade show. Engineering and procurement push for the cheapest BOM, when a slightly higher unit cost would still protect margin that the sales team need, and buy robustness and defensibility. That gap is exactly where competitors step in, copy the idea, and execute better.
My goal here is simple: help you ask the right questions at the right time.
If you want a quick reality check on where you stand:
Comment “Scorecard” and I’ll share a 2‑minute industrialization scorecard tailored to your industry, so you can see what’s missing before pilot yield collapses.
Remember: Acting early is cheaper than fixing late.