Framework for software product management in life sciences

Software Product Managers

Irrelevant of the company or market, I see the fundamental software product manager’s (SW PdM) responsibilities as:

  • Identifying high-impact problems aligned with business goals

  • Defining solutions

  • Achieving outcomes

Life Sciences SW PdMs

Life science software PdMs must adapt their core responsibilities to a unique ecosystem where software typically supports a primary product rather than being the primary product itself. I built a framework to help myself navigate the complex life sciences space and adapt my PdM strategies. Understanding a product’s position within the life sciences framework has enabled me (and hopefully other SW PdMs) to elevate software to a strategic and critical enabler of innovation.

Framework

Understanding a software product's position across three key dimensions helps clarify the SW PdM role and responsibilities:

  1. Life sciences verticals (What is a company’s primary product?)

    • Biopharma == Companies developing therapeutic products (e.g. small molecules, cell/gene therapies, vaccines, etc)

    • Medical Devices == Companies making hardware products with software components.

    • Diagnostics == Companies selling tests or platforms to detect/analyze disease indicators.

    • Digital Health == Companies selling software for healthcare processes or data analysis.

  2. Software flavors

    • R&D and Discovery == Software for research and early development.

    • Clinical == Software for trials and patient processes.

    • Manufacturing and Operations == Software for production and quality control.

    • Commercial and Analytics == Software for market access and business intelligence.

  3. Regulatory status

    • Regulated: Software requires formal development processes and extensive documentation.

    • Non-regulated: Software has faster iterations and fewer formal requirements.

Impact on PdM role

A product’s position in this framework significantly affects a SW PdM’s:

  • Stakeholders

  • Development approach (e.g. release cadence)

  • Documentation (e.g. verification and validation requirements)

Previous
Previous

Creating a data culture in biotech

Next
Next

[WIP] Data platforms and lab automation