This is Clinical Product Thinking 🧠, a weekly newsletter featuring practical tips, frameworks and strategies from the front line of clinical product.
Welcome, friends, this is issue No. 057 of Clinical Product Thinking. Today we’re answering a deceptively simple question: what role does Clinical Product actually play?
Through writing Clinical Product Thinking, I’ve spent a lot of time thinking about the definition of Clinical Product Management.
Here is what I’ve landed on:
Clinical Product Management is embedding clinical judgement throughout the entire product lifecycle.
But that doesn’t answer the question: what should a clinical product person be responsible for?
That is hard because the boundaries between clinical, clinical product, product, safety, and operations are murky.
To help us, I recruited my good friend Danielle Brightman, the OG clinical product leader. She writes about clinical product at clinicalproduct.uk.
Let’s dive in.
So, what is clinical product?
As Dani describes, clinical product is embedded. It’s blocking by default, and it’s accountable for clinical integrity.
But those are characteristics. They don’t fully capture what the role is.
As Dani puts it, clinical product does these five things:
1. Setting the clinical direction
Clinical product doesn’t wait for requirements to arrive. It actively scans emerging evidence, market shifts, and changes in clinical practice to shape what should exist next.
This includes identifying when new treatments or care models are clinically viable and when they’re premature, unsafe, or operationally unrealistic.
2. Embedding clinical judgement throughout the product lifecycle
Dani says embedding Clinical Product is essential as their input is needed across:
Discovery and planning – grounding ideas in real clinical practice, evidence, and patient care realities
System and experience design – shaping requirements so what’s being built is clinically coherent, not just technically correct
Implementation – preventing “small” implementation details from creating unacceptable clinical behaviour
Testing and acceptance – validating that things behave safely in real-world clinical use
Deployment and monitoring – owning what happens after launch, including incident response and emerging risks
This is where the role differs most clearly from advisory, QA, or compliance functions: clinical product carries accountability across the whole arc.
3. Designing for the full clinical ecosystem
Clinical product optimises for outcomes, not isolated users.
Patient safety and effectiveness depend on the combined behaviour of patients, clinicians, health coaches, operations, customer support, and systems.
A feature that “works” for patients but creates unsafe escalation paths, unmanageable clinician load, or regulatory exposure is not ready to ship.
4. Exercising clinical risk ownership
Clinical product leads clinical risk thinking in day-to-day product work:
Identifying and articulating risks early
Maintaining and evolving hazard logs and risk registers (in collaboration with the CSO)
Providing clear, defensible clinical rationale for decisions
Supporting incident investigation and learning
Working with governance roles without outsourcing accountability
5. Acting as the point of clinical accountability in partnerships and scale
As products integrate with external partners or scale across teams, clinical risk diffuses.
Clinical product owns due diligence and integration decisions from a clinical perspective, ensuring that external dependencies don’t dilute safety or accountability.
What clinical product is not
A few clarifications, because the role is often confused with adjacent functions:
Clinical product is not clinical subject-matter expert (SME) work.
SMEs provide knowledge; clinical product provides judgment, including the judgment to say no. Confusion comes when SMEs provide product teams with their direct viewpoint. Teams don’t know which clinician to listen to. Specialist input should inform the Clinical Product Manager, who remains accountable for how that input is applied.
Clinical product is not regulatory or compliance.
Compliance ensures processes are followed. Clinical product makes clinical decisions. There’s overlap, but the accountability is different.
Clinical product is not QA.
QA tests whether the product works as intended. Clinical product determines whether what’s intended is clinically sound. The Clinical Product Manager does often have a role in acceptance testing, but that’s to ensure the product behaves safely in clinical use, not to validate that it meets functional specifications.
Clinical product is not medical affairs.
Medical affairs manages external clinical relationships. Clinical product operates inside the product team. In some organisations, particularly early-stage ones, the same person may cover both areas.
Why this definition matters
Clinical product is still an emerging discipline. We’re still in a state where there’s no standard job description, no universal competency framework and no agreed curriculum.
That ambiguity creates problems. Organisations hire clinical product people without knowing what they’re hiring for. People take clinical product roles without knowing what they’re signing up for. Expectations misalign, and accountability falls through the cracks.
Definitions help because they make it possible to have honest conversations about what the role requires and whether it’s being set up to succeed.
Thank you to Dani for sharing her thoughts and expertise in this post. 💜
Next week, we’re sticking with Dani for one the trickier parts of Clinical Product: the power to block. When should Clinical Product be able to stop something shipping — and when should it step back?
Clinical Product Drinks 🍸
Tuesday was Clinical Product Drinks #003. So much fun with so many incredible folks building the future of digital health. Thank you again to sponsor Scale Health. Look out for the next one in mid-November.
That’s all for this week. See you next time! 👋
🤝 Work with me | 📅 Attend an event | ✍️ Send a message
Written by Dr Louise Rix, Clinical Product, AI & Safety, doctor and ex-VC. Passionate about all things healthcare, healthtech and clinical product (…obviously). Based in London. You can find me on LinkedIn.
Made with 💜 for better, safer HealthTech.