What Big Medical Device Companies Can Learn From Startups About Voice of Customer
How medical device startups accelerate customer feedback loops and what established companies can adopt to keep pace.
What Big Medical Device Companies Can Learn From Startups About Voice of Customer
At my small medical device startup, customer connection is our lifeline. Most days, I’m speaking with clinicians, listening to their needs, and acting on them within the week. When I need clinical feedback, I can reach a qualified clinician within 24 hours. In Medical Alley, I often compare notes with peers at large medical device companies—organizations with thousands of employees, regulatory teams, and global operations. Our cycle times for Voice of Customer (VoC) differ by an order of magnitude. Some of that gap is regulatory; most of it isn’t. This piece focuses on the part that isn’t.
Where the Speed Gap Actually Comes From
Startups operate under a lighter regulatory load early in the lifecycle, with fewer product lines, audits, and post-market obligations. That advantage is real and worth acknowledging. However, the larger story is the operating model—something large companies can change without altering regulations.
Out of necessity, startups have built habits that scale:
- Listening continuously rather than periodically
- Bringing compliance into the room from the start
- Defining the customer as the entire care team
- Treating the FDA as an early collaborator rather than a final reviewer
How VoC Tends to Work at Scale
In conversations with peers at large companies, a common pattern emerges: research is often used to defend decisions rather than challenge them. Large surveys provide breadth—useful for boardroom presentations—but rarely answer “why.” Many organizations invest significantly in human factors, clinical validation, and patient journey mapping; the greater challenge is translating those insights into product decisions on a meaningful timeline.
Two structural patterns tend to slow the feedback loop.
- First, the working definition of “customer” often narrows to high-volume clients and named opinion leaders because they are easier to access. Other roles—such as scrub nurses, purchasing managers, reimbursement teams, and patients—appear in research but less frequently influence decisions.
- Second, functions like R&D, Marketing, Regulatory, Clinical Affairs, and Commercial engage at different stages, and the customer voice weakens at each handoff. Some companies address this through integrated teams and product lifecycle systems, but many still rely on fragmented processes. Compliance and legal are often involved late, creating a culture of avoidance. While some reviews are required by regulation, others are artifacts of sequencing—issues that disappear when compliance is engaged from the beginning.
What Startups Do Differently
Continuous discovery, not project-based discovery
At startups, VoC is an ongoing conversation, not a quarterly initiative. A half-hour conversation with one clinician each week—synthesized by the team—can surface problems faster than a hundred-person quarterly survey. This approach has limitations, including small sample sizes and anecdotal bias, and works best as a complement to structured research, not a replacement.
Jobs-to-be-Done applied to the entire care team
We define the market by the job, not the product category. The difference between “cardiovascular stents” and “surgeons trying to reopen a blood vessel in neonates” is the difference between optimizing an existing solution and uncovering a new one. This lens forces consideration of every role on the care team and encourages the use of proxy users (e.g., coaches, allied health professionals, or internal staff with clinical backgrounds) when direct access is limited.
Compliance inside the room, not outside it
The traditional Product Trio—product manager (or advocate), designer, and lead engineer—becomes a quartet in regulated environments, with a regulatory or compliance partner involved from day one. Approvals that take months at the back end can take days when protocols, consent processes, and data plans are developed collaboratively. The standards don’t change; the sequencing does.
Regulators as early collaborators
Startups often use Pre-Submission meetings as learning opportunities, not just risk mitigation steps. Early feedback from regulators can reshape a product before costly development begins. Both startups and large firms use Pre-Subs; the difference lies in the intent behind them.
How Large Companies Can Translate This
Rather than overhauling the enterprise, start small. Select one product line and empower a cross-functional team to operate using this model for a single project over one quarter. Measure cycle time—from customer insight to product decision—against your current process.
Once a pilot demonstrates results, three shifts can amplify impact:
A product-centric QMS
A lean Quality Management System enables cross-functional teams to share a unified view of the product and route customer feedback directly to R&D, reducing reliance on cumbersome documentation workflows.
A partnership-driven commercial model
As purchasing decisions shift toward outcomes rather than features, sales teams become continuous sources of customer insight rather than one-time points of contact.
Innovation accounting
Measure validated assumptions, not just features delivered. Each assumption should be explicitly stated (e.g., “clinicians will adopt this workflow change within two cases”), tied to observable behavior, and tested against real evidence. A team that delivers twelve features but validates zero assumptions is not making meaningful progress.
The Limits of Internal Incubators
Programs like J&J’s JLABS and similar innovation hubs are valuable hedges, but they are not substitutes for transforming the core business model. While incubators can produce strong science, they do not inherently change how the parent organization approaches VoC. That transformation must happen within the core business.
The Objections You’ll Hear
“We’re regulated—we can’t move that fast.”
Startups operate under the same regulatory frameworks. The constraint is the operating model, not the rulebook.
“Compliance won’t allow it.”
They will—if they are involved from the start. They are more likely to resist when brought in at the end.
“Our IRB is too slow for frequent touchpoints.”
Most workflow conversations do not require IRB review. Those that do can be structured to align with an ongoing cadence rather than disrupt it.
“We’re too large to operate this way.”
That is precisely why you begin with a pilot, not a full-scale transformation.
One Thing You Could Pilot Next Month
Select one product line. Assign a product manager (or advocate) to conduct a recurring 30-minute conversation with a clinician in the use environment, followed by a 30-minute synthesis session with a designer, engineer, and compliance partner. Capture one product decision per session.
Run this every two weeks for one quarter, then compare the cycle time to your previous process.
You don’t need executive approval to begin. One product manager, one recurring meeting, one customer.
