This is part 2 of a 3-part series on UX in Life Sciences from the Pistoia Alliance UXLS community.
If you’ve spent time in life sciences UX, you’ve likely experienced it: a project lands, you’re brought in late, you do what you can, it ships. And then the team moves on. The tool you helped design may stay in use for years, but nobody’s watching how it performs, and nobody’s asked to improve it. That’s the project mindset in action.
The shift to a product mindset changes all of that.
In an industry where digital tools touch scientific workflows, data integrity, regulatory compliance, and ultimately patient outcomes, whether UX is treated as a project deliverable or a product capability is not a semantic difference. It determines how early you’re involved, how success is defined, and whether the value of UX compounds over time or resets with every reorganization.
What is the article about?
This is the second in a 3-part series from the Pistoia Alliance UX in Life Sciences (UXLS) community exploring how UX operates in one of the most complex and regulated industries.
In part 1, we discussed how regulatory environments, scientific workflows, and long development cycles reshape UX practice in the Life Sciences and highlight the structural challenges practitioners face.
In this article, we examine the shift from project-driven to product-driven UX and why it matters in life sciences. We explore what the traditional project model looks like in practice, how the life sciences environment amplifies the need for change, and what a product mindset concretely enables: earlier strategic involvement, continuous measurement, and sustained UX presence across the product lifecycle. We also offer a practical set of checkpoints for practitioners navigating this shift in their own organizations.
Who should read this?
This series is for UX practitioners, designers, researchers, and digital leaders working in or considering moving into life sciences. It is especially relevant for those advocating for earlier UX involvement, clearer outcome measurement, or stronger UX presence within product teams.
If you are a digital or R&D leader responsible for transformation programs or AI adoption, this article offers a clear articulation of why the conditions under which UX operates directly affect the quality and sustainability of your digital systems.
From Projects to Products: Why UX in Life Sciences Needs a Mindset Shift
Across pharmaceutical and life sciences organizations, a significant shift is underway. Teams that once operated through short, linear projects are increasingly moving toward long‑lived, continuously evolving products. For User Experience (UX) practitioners, this shift is far more than operational vocabulary. It fundamentally changes when we are involved, how we work, and how user value is defined, measured, and sustained.
And in life sciences where digital tools influence scientific workflows, data quality, compliance, and ultimately patient outcomes, the difference between a project mindset and a product mindset is magnified.
The Project Model Most of Us Know
Traditionally, life sciences UX has grown up in a project-driven environment:
- Projects have a fixed start and end, often constrained to weeks or months, and are milestone driven.
- UX is brought in late, forcing the work to become reactive.
- UX is minimized to User Interface (UI) work or “Making things look nice”.
- Measurement often stops at go‑live, leaving no visibility into whether user behavior changes or whether the solution delivers meaningful value.
In this model, teams unintentionally build feature factories, where success is judged by output volume rather than outcome achieved.
In fast consumer tech, this inefficiency is annoying. In life sciences, it can be costly, risky, and long‑lasting.
Why Life Sciences Amplifies the Need for Change
Life sciences digital systems rarely stand alone. They operate within complex scientific and operational ecosystems, embedded across drug discovery and experimental workflows, supporting lab operations and data capture, enabling clinical development, underpinning quality, safety, and regulatory environments, extending into global manufacturing and supply systems, and ultimately engaging with patients and healthcare professionals.
These processes are interconnected, data‑dependent, and heavily governed. A misalignment introduced early can ripple across years of scientific and operational activity.
That is why organizations are increasingly adopting a product mindset, because scientific, digital, and data systems cannot be improved meaningfully through short-term, isolated bursts of delivery.
What a Product Mindset Enables
A product mindset reshapes three foundational aspects of UX in life sciences.
1. UX Starts Earlier
With a product approach, UX is brought into the conversation before a solution is predefined. Teams take time to frame the problem:
- What scientific workflow are we trying to improve?
- What pain points or cognitive burdens do users experience?
- What scientific or business impact are we targeting?
- How will we know if we achieved it?
This early strategic framing allows organizations to avoid misalignment that is costly to fix later.
2. Success Is Measured Continuously
Products are evaluated not just at launch but by how they perform and deliver value over time, with teams continuously monitoring usability, adoption, satisfaction, and workflow impact through telemetry and usage analytics, standardized measures like the User Experience Questionnaire (UEQ), ongoing qualitative feedback, and trend analysis gathered over months and years.
Instead of a single point-in-time snapshot, UX becomes a continuous, evidence-based practice.
3. UX Stays Embedded
Product teams keep UX involved for the long haul, which allows practitioners to build deep domain understanding, track evolving workflows, support iterative improvements, maintain consistency across releases, and reduce long‑term design and technical debt.
The Defining Difference Between Projects and Products
Projects optimize delivery. Products optimize long-term value.
A project mindset keeps UX in a reactive posture. A product mindset elevates UX into a strategic role.
This shift is not theoretical. It improves the quality, safety, and sustainability of digital systems used across life sciences. As a result of that, UX contributes to long-term product health, critical in large organizations where structures and priorities frequently shift.
For UX Practitioners Navigating the Shift
Moving from projects to products isn’t like turning on a switch. Adopting product terminology doesn’t mean true product thinking is in place. The real question is whether the conditions for product‑driven UX actually exist. Use this as a practical checkpoint to guide your work and influence your teams:
- Are you involved before solutions are defined, helping frame the problem rather than reacting to it?
- Do you stay engaged across the product lifecycle, shaping direction and what matters, not just polishing the UI?
- Is user experience evaluated continuously through ongoing feedback loops, not only just at a point in time?
- Does the team optimize value, not delivery, focusing on solving the right problems rather than shipping the most features?
- Are success metrics tied to real user, scientific, and business outcomes, not just delivery milestones?
If the answer to several of these is “no,” then the organization is still operating in project logic, and that’s your signal to advocate for earlier involvement, clearer outcomes, and stronger UX presence throughout the lifecycle.
The organizational reality
Life sciences organizations are large, complex, and constantly evolving. With every restructuring and organizational change, UX maturity can easily slip backward if teams lack shared standards and a common language. This is where communities of practice (CoPs) become essential. They preserve institutional knowledge, promote consistent methods, strengthen collective understanding of UX’s value, and connect practitioners who might otherwise work in isolation. Most importantly, they provide the continuity needed to sustain product thinking through ongoing organizational change.
In the third article of this series, we explore how UX CoPs help break down silos, accelerate learning, and strengthen UX’s strategic role across R&D, digital, data, and IT in Life Sciences.
What can you do with this?
If you work in UX within life sciences, use the practitioner checklist in this article as a starting point for an honest conversation with your team or stakeholders. Not all five conditions will be in place. But that’s not a failure. It’s a map. Identify where the gaps are, name them clearly, and begin advocating for the specific conditions that would shift your practice from reactive delivery to strategic contribution.
If you lead a digital, R&D, or data function, ask yourself whether the UX embedded in your organization operates with the right mandate, timing, and continuity. The sustainability of your digital systems depends on it.
What’s coming next in this series
In Part 3, we explore how communities of practice are forming across life sciences organizations to sustain UX maturity, share knowledge, and reduce the isolation that so many practitioners experience, even as structures shift around them.
Join the UX in Life Sciences (UXLS) community
The UX in Life Sciences (UXLS) community at the Pistoia Alliance brings together practitioners across organizations to share frameworks, exchange lessons learned, and strengthen the role of UX in a complex and evolving industry.
If your organization is already a member of the Pistoia Alliance, we invite you to get involved in UXLS. If not, this is an opportunity to explore how the Pistoia Alliance supports collaboration across data, AI, interoperability, and digital transformation in life sciences.
Where to learn more
The UXLS Community of Experts > https://pistoiaalliance.org/community/uxls/
Joining the Pistoia Alliance > https://pistoiaalliance.org/membership/
About the authors
This article reflects the collective expertise of members of the UX in Life Sciences (UXLS) community within the Pistoia Alliance.
The main contributors were Jing Zhang, PhD Jing Z. · Sven Neumeyer · Peter Hummel · Brian Mila · Nicola Marcon · Voula Gkatzidou, PhD · Breac Baker Breac B. · Sudha Yerramilli Sudha Y. · Peter Horvath · Farah Egby
A special thanks goes to our Steering Committee, Sven Neumeyer (Novartis) · Simon Fortenbacher (GSK) · David Pace (Merck), and to all members of the UXLS Best Practices workstream for their contributions, ideas, and energy throughout the year.