DEV Community

Saveyourproject
Saveyourproject

Posted on • Originally published at saveyourproject.com

Why your prototype works for you but not for anyone else

TL;DR — A prototype that works for you but breaks for everyone else usually isn't bad luck. It's four repeatable culprits: you designed for one assembly, your fasteners drift, the enclosure ignores real loads, and you never wrote down why it works. Fix those, and "works on my bench" becomes "works, period."

You built the thing, and it works. In your hands, on your bench, every single time.

Then a friend tries it, or it sits in the garage a week, or the temperature drops one night, and it just stops.

Frustrating doesn't really cover it.

Here's the reassuring part: that gap between "works for me" and "works for anyone" is almost always the same small handful of culprits. You're not missing some secret skill. Once you've met them a few times, you start designing around them without even thinking about it.

1. You built it for one. Now build it for two.

That first one fit because you were there — nudging, sanding, coaxing it together. The trouble is, all of that lived in your hands, not in the model.

So the second copy fights you.

If you can't make a second one without the fiddling, it isn't done yet. Bake the clearance into the CAD, then print one you promise not to touch up. That's the real test.

2. Your fasteners are quietly betraying you.

Press-fits creep. Hot glue lets go. Jumper wires back out. Double-sided tape taps out the first warm afternoon.

I know the boring fixes aren't the fun part — a screw boss, a captive nut, a bit of strain relief, a connector that actually clicks home. But boring is exactly what's still holding a year from now.

3. The enclosure is a load, not a lid.

It's easy to treat the box as an afterthought. But heat, dust, and vibration are real forces working on your build.

A board that runs cool in the open can slowly cook once it's sealed up. A connector that's happy on the bench can buzz itself loose in a drawer that gets opened every day.

Give the heat somewhere to go, mount the board instead of letting it dangle from its wires, and clamp down anything that moves.

4. Write down why it works.

Future-you is begging you.

Six months from now, v2 breaks and you won't remember which dimension was load-bearing, which resistor value you finally settled on, or why that one screw is longer than the rest.

One page of "why" notes — just the decisions that actually mattered — turns a miserable teardown into a five-minute fix.

You don't need a factory for any of this

It's really just one step past "it works," and it's a step anyone can learn.

(There's a whole other layer once you want to make ten of something, where sourcing and repeatability change the math. But that's a problem for after this one.)

So I'm curious: which of these four bites you the most? For me it's almost always #1 — designing for one, and forgetting the second one has to exist too.

I originally posted this on my own site, if you'd like it in one place: https://www.saveyourproject.com/blog/bench-to-real-use-reliability

Top comments (0)