Making the Right Call When Building a Medical Device: Insights from Bruce Huici

Why the decision matters

Medical device development forces you to make hundreds of decisions before you ever reach a patient. Material selection, feature prioritization, manufacturing approach, regulatory pathway—each one compounds. Get the early calls wrong and you can spend years trying to work around them.

As the founder and CEO of Hallstat, where I have developed multiple patent-issued and patent-pending technologies in healthcare. My background as a nurse and medical device entrepreneur gives a dual perspective: I understand what clinicians need at the bedside and what it takes to actually bring a product to market. That combination matters when the stakes are this high.

Start with the problem, not the solution

The biggest mistake in medical device design is starting with what you want to build instead of what needs solving. You have an idea for a sensor, a delivery mechanism, a workflow improvement. But unless you've watched the problem play out in real settings, you're guessing.

Spend time in the environment where your device will be used. Talk to the people who will touch it: nurses, technicians, physicians, patients. Watch the full workflow, not just the moment your device is supposed to help. A product that solves one step but creates friction elsewhere usually fails.

Ask what happens when things go wrong. The best devices account for human error, time pressure, and less-than-ideal conditions. If your design only works when everything else is perfect, it won't work.

Choose your complexity ceiling early

Every feature you add increases development time, regulatory burden, manufacturing cost, and user training. It also adds failure points. The temptation is to pack in everything that might be useful. The smarter move is to define the minimum set of capabilities that solves the core problem well.

This is not about building a cheap product. It's about building a product that does one thing reliably instead of ten things poorly. You can always add features in version two if the market demands them. You cannot easily strip out complexity once it's embedded.

Decide early whether you're building for a niche clinical application or a broad market. A device designed to do both usually serves neither well. The feature set, price point, and regulatory strategy are completely different.

Regulatory strategy is not something you layer on later

Many founders treat FDA clearance or approval as a final hurdle. In reality, your regulatory pathway should shape design decisions from day one. The classification you're targeting determines what kind of testing you need, what predicate devices you can reference, and how much clinical data you'll have to generate.

If you're aiming for a 510(k) clearance, you need a strong predicate with well-documented equivalence. If you're pursuing de novo or PMA, expect years of clinical trials and significantly higher costs. Knowing which path you're on changes what you prioritize in development.

Work with regulatory consultants early, not when you're ready to file. They can help you structure your development process so that the data you collect actually supports the submission you'll need. Retrofitting that documentation is expensive and slow.

Manufacturing decisions lock you in

Prototyping is forgiving. Manufacturing is not. The materials, tolerances, and assembly methods you choose determine your unit cost, your scalability, and your supply chain risk.

A design that works beautifully in small batches can be a nightmare at scale if it requires manual assembly steps, hard-to-source components, or tight tolerances that drive up scrap rates. Talk to manufacturers before you finalize the design. They will tell you what drives cost and what creates bottlenecks.

Dual-source critical components if you can. A single supplier going out of business or facing a shortage can shut down your entire production. It happens more often than founders expect.

Test for the real world, not the lab

Bench testing and clinical validation are both necessary, but they're not sufficient. You also need to test how the device behaves in the hands of tired, distracted users working in chaotic environments.

Run usability studies with people who match your actual end users, not your engineering team. Watch where they hesitate, what they misinterpret, and what they skip. Those moments reveal design flaws that no amount of technical testing will catch.

Pay attention to edge cases. What happens if someone uses the device on a patient outside the intended population? What if they ignore the instructions? What if the device is stored improperly? A robust design anticipates misuse and fails safely.

Balance innovation with reliability

Cutting-edge technology is appealing, but medical devices live or die on reliability. A device that works 95% of the time is not good enough when the other 5% involves patient harm.

If your innovation depends on a component or material that has limited field data, build in redundancy or fallback mechanisms. Clinicians need to trust that the device will perform the same way every time. Unpredictability kills adoption faster than anything else.

Sometimes the best design choice is the boring one. Proven materials, established manufacturing processes, and simple mechanisms reduce risk. Innovation should go into solving the clinical problem, not into making the solution complicated.

Know what you're optimizing for

You cannot optimize for everything at once. Lower cost, faster time to market, broader indications, easier usability—each one involves trade-offs. Decide early what matters most for your device and your market, then make decisions that align with that priority.

If you're entering a crowded market, speed might matter more than perfection. If you're targeting a high-risk application, reliability and regulatory rigor come first. If you're building for resource-limited settings, cost and simplicity override feature richness.

The worst outcome is a device that tries to be everything and ends up mediocre across the board. Make the hard calls early, and stick with them.