Clinical Need Identification

Observe procedures, analyze workflows, and uncover unmet clinical needs.

1

Observation First

  • Observe real clinical environments.
  • Watch procedures, workflows, and user behavior.
  • Look for frustration, inefficiency, risk, and workarounds.
  • Pay attention to what clinicians struggle with, not just what they say.
  • Sometimes the biggest opportunities are problems nobody has formally identified yet.
2

Think from First Principles

  • Ask what is fundamentally failing.
  • Separate symptoms from root causes.
  • Challenge assumptions and conventional wisdom.
  • Identify the true source of pain rather than treating secondary effects.
3

Understand the Entire Ecosystem

  • Evaluate workflow impacts.
  • Understand reimbursement pathways.
  • Assess economic incentives.
  • Study competitive products and existing alternatives.
  • Identify where meaningful opportunity windows exist.
4

Understand the Entire Ecosystem

  • Determine market size and attractiveness.
  • Confirm that customers will adopt and pay for a solution.
  • Assess whether investors, strategic partners, or internal stakeholders will support development.
  • Make sure the problem is significant enough to justify solving.
5

Revolutionary vs. Evolutionary Innovation

  • Evolutionary innovation improves existing products and platforms.
  • Existing products provide useful constraints and guidance.
  • Problems are often easier to identify and quantify.
  • Revolutionary innovation creates new categories or disrupts existing markets.
  • Requires greater vision and conviction.
  • Often solves problems users cannot yet articulate.
  • Creates entirely new opportunities and business models.
6

Define the Guardrails

  • Clearly understand platform constraints.
  • Establish technical, clinical, regulatory, and business requirements.
  • Know where the boundaries exist before attempting to push them.
  • Verify that constraints are real and not simply historical assumptions.
7

Define the Guardrails

  • Challenge legacy architecture when necessary.
  • Be willing to change multiple systems to solve an important problem.
  • Avoid protecting existing designs at the expense of meaningful innovation.
  • Sometimes fixing one critical issue requires rethinking the entire solution.
8

Needs Before Solutions

  • Never start with a technology looking for a problem.
  • Build a prioritized list of validated needs first.
  • Let needs drive concept generation.
  • Fall in love with the problem, not the solution.
9

Requirements Cascade

  • Start with clinical user needs.
  • Translate those into system requirements.
  • Translate system requirements into subsystem requirements.
  • Maintain traceability from every design decision back to an identified need.
  • Ensure engineering effort remains aligned with customer value.

Key Lessons

  • Observation is the foundation of innovation.
  • Root causes matter more than symptoms.
  • Opportunity size matters as much as technical feasibility.
  • Evolutionary products optimize existing markets.
  • Revolutionary products create new markets.
  • Constraints should guide innovation, not prevent it.
  • Great solutions emerge from deeply understood needs.
  • The strongest products maintain a clear chain from unmet need to final design.