Building Trust In Clinical Supply Digital Transformation

A conversation with Edwige Njiayap Nouboug, BioPharma Deputy Lead, Sanofi

Digital transformation has become a strategic priority across the life sciences industry, with organizations investing heavily in new platforms, analytics, and artificial intelligence to improve efficiency and decision-making. Yet technology alone does not guarantee better outcomes. In clinical supply, where patient safety, regulatory compliance, and operational continuity are paramount, the greatest challenges often stem not from the systems themselves but from how people adopt them and how organizations govern the data those systems rely on.

As clinical supply operations become increasingly connected across planning platforms, ERP systems, manufacturing, quality, and external partners, creating a trusted foundation for decision-making has never been more important. Effective data governance, clear business ownership, and strong user adoption are essential to realizing the full value of digital transformation. Without them, even the most advanced technologies can introduce complexity rather than clarity.

In this Q&A, Elizabeth Urbanek, executive editor of Clinical Supply Leader, sits down with Edwige Njiayap Nouboug, bioPharma deputy lead at Sanofi, to discuss why digital transformation initiatives succeed or fail, the critical role of data governance in clinical supply, strategies for driving lasting user adoption, and how organizations can prepare for a future where AI and advanced analytics play an increasingly important role in supply chain decision-making.

Clinical supply organizations are investing heavily in digital transformation. Why do so many initiatives struggle to achieve lasting user adoption, even when the technology itself performs as expected?

Most digital transformation programs I've seen don't fail because of the technology. They fail because organizations stop paying attention to people the moment the system goes live.

Clinical supply teams operate in a highly regulated environment where compliance, accuracy, and continuity are nonnegotiable. A new platform can be technically flawless and still fail to gain adoption because users haven't been shown how it makes their daily work easier or improves the decisions they make. When that confidence is missing, people keep their spreadsheets running in parallel "just in case." That workaround isn't simply resistance to change. It's a rational response to uncertainty.

I saw this firsthand while leading global rollout programs for a pharmaceutical organization. The platform passed validation without issue, yet adoption remained low for months after go-live. Business teams hadn't rejected the technology. They simply hadn't been involved in shaping it, so they couldn't see how it improved the decisions they made every day.

Adoption accelerated only after we brought a small group of end users, our business champions, into the workflow design process. They helped influence how alerts, approvals, and exceptions were presented instead of simply being trained on a system someone else had designed.

That experience taught me that trusting the data and trusting the system are really the same challenge. Even the best-performing platform will struggle with adoption if users question where the data comes from or who is accountable for it. Data governance and user adoption succeed together, or they fail together.

Organizations that get this right treat digital transformation as a change in how the business makes decisions, not simply how it operates. They measure success by changes in behavior and collaboration, not by the go-live date.

Ultimately, people don't adopt a tool because it's new. They adopt it because it helps them make better decisions faster, with less risk, and because they have confidence using it every day.

What role does data governance play in ensuring that digital tools actually improve decision-making rather than creating unnecessary complexity?

Data governance is what separates a digital tool that clarifies decisions from one that simply adds more complexity.

Clinical supply operates across a broad ecosystem that includes planning platforms, ERP systems, manufacturing execution systems, quality systems, laboratories, and external partners. Each of those systems may contain accurate information on its own, but they often don't define key data elements the same way.

A dashboard built on top of inconsistent definitions doesn't simplify decision-making. It simply makes disagreements more visible.

I worked on a program where three regional teams each trusted a different inventory number for the same shipment. The technology wasn't the problem. The business had never agreed on which system was the authoritative source or who owned the data definition.

Once we assigned clear business ownership for each critical data element and established a single shared definition across functions, the same dashboard that had generated repeated escalations became a trusted decision-making tool.

That's the real purpose of data governance. It's not about adding more control. It's about reducing variability. It defines who owns the data, how quality is monitored, and how information flows consistently across the organization so every stakeholder is working from the same understanding.

As AI and advanced analytics become more common in clinical supply, governance becomes even more important. AI built on inconsistent or poorly governed data simply produces faster decisions with greater confidence, but not necessarily better ones.

AI doesn't fix weak data foundations. It exposes them.

Better decisions don't come from having more data. They come from having data that everyone trusts, and that trust must be built deliberately.

Clinical supply teams rely on data from multiple sources, from planning platforms to ERP, laboratory, and manufacturing systems. What governance practices help organizations create a reliable single source of truth across this environment?

A single source of truth is often viewed as a technical objective, as though one system should contain everything. In clinical supply, that's neither realistic nor necessary. The real objective is ensuring that every critical business decision is based on data that means the same thing across every system involved.

Planning systems, ERP platforms, laboratory systems, and manufacturing applications all serve different purposes, and they should. The challenge isn't the number of systems. It's ensuring they all speak the same business language where it matters most.

The first step is establishing shared business definitions for the handful of data elements that actually drive decisions, such as inventory, batch status, release dates, and supply availability.

In one organization, different functions each maintained their own definition of "available inventory." Both definitions were technically correct within their respective systems, but they produced conflicting business decisions. The issue wasn't resolved until the business, not IT, agreed on a common definition and made it the enterprise standard.

The second requirement is clear ownership. Every critical data element should have a business owner who is accountable for its quality throughout its life cycle. Governance works best when accountability sits within the business rather than remaining solely with the project team or IT.

Third, data quality must be measured continuously through meaningful KPIs. Governance isn't a one-time exercise. Data requires ongoing monitoring and stewardship because its relevance and accuracy can quickly decline if left unmanaged.

Finally, none of this succeeds without collaboration. Clinical supply, manufacturing, quality, regulatory, and IT teams all need to develop these standards together. A single source of truth imposed by one function rarely survives in a cross-functional environment.

Ultimately, a single source of truth isn't a system. It's an organizational agreement around common definitions, governance, and accountability. That's what enables faster decisions, stronger compliance, and greater confidence across the business.

When implementing a new digital platform, what are the biggest mistakes organizations make in driving user adoption, and what approaches have you found to be more effective in a regulated healthcare environment?

The biggest mistake I see is treating user adoption as something that begins after go-live, when in reality it starts the day the platform is first designed. Too often, end users are involved only when it's time for training. Organizations are then surprised when technically sound solutions fail to fit the way people actually work.

In a regulated healthcare environment, that gap is particularly costly. Users are responsible for patient safety, data integrity, and compliance. Their hesitation isn't resistance to change. It's a legitimate need for confidence that the new way of working will stand up under audit and under pressure.

Another common mistake is confusing training with adoption. Training teaches people which buttons to click. Adoption happens when they genuinely believe the new process helps them do their jobs more safely, efficiently, and confidently.

On one implementation, the training program was comprehensive and well attended, yet user adoption declined within weeks after go-live because no one had clearly explained why the new process was better than the one it replaced. The turning point came when we identified respected business champions within each department. They were able to explain the value of the new process from the perspective of their peers rather than the project team.

Successful organizations involve end users throughout the project, not just during user acceptance testing. They continuously gather feedback, refine workflows, and recognize that go-live marks the beginning of adoption rather than the end of the project.

Leadership visibility also matters. Active sponsorship demonstrates that adoption is a business priority rather than an optional initiative.

Most importantly, organizations should measure whether behaviors have actually changed. Are employees relying on the new platform, or are they still maintaining backup spreadsheets?

Technology changes what a system can do. Adoption changes what people actually do with it. Sustainable transformation only happens when both evolve together.

How should clinical supply leaders measure the success of digital transformation beyond implementation milestones? Which operational or business metrics best indicate that adoption is creating real value?

Go-live is where many organizations stop measuring success, but it's actually where value creation begins. System deployment, validation, training completion, and project milestones are all important, but they don't tell leaders whether clinical supply operations are performing better than they were before implementation.

The metrics that matter are operational. They include faster decision-making, improved forecast accuracy, fewer manual reconciliations between systems, shorter process cycle times, fewer supply disruptions, and stronger collaboration across functions that previously worked in silos.

On one project, the implementation was declared a technical success at go-live. The real insight emerged several months later when we measured how frequently planners continued exporting data into personal spreadsheets before making decisions. That seemingly simple metric told leadership far more about adoption than training completion rates or system usage statistics ever could.

Organizations should continually assess whether employees are relying on the platform for daily decisions or working around it. They should also evaluate whether decisions are increasingly based on shared, trusted data instead of individual interpretation or institutional memory.

Perhaps the most overlooked measure is confidence. When people trust both the platform and the data behind it, adoption becomes self-sustaining rather than something leadership must continually reinforce.

That confidence eventually appears in stronger compliance, more effective collaboration, and faster cross-functional decision-making.

The purpose of digital transformation is never simply to deploy a system. It's to improve how the business performs and, ultimately, how reliably it serves patients. Success should always be measured against that objective rather than against the implementation schedule.

Looking ahead, how do you see stronger data governance and greater user adoption shaping the future of clinical supply operations as AI and advanced analytics become more common?

I don't believe AI will solve weak data foundations in clinical supply. Instead, it will make the consequences of those weaknesses faster and more visible.

AI and advanced analytics have tremendous potential to improve forecasting, identify risks earlier, and optimize inventory and supply decisions that still depend heavily on individual experience today. However, an algorithm trained on data that people don't trust won't produce better decisions. It will simply produce faster, more confident, and potentially incorrect decisions at scale.

That's why I believe data governance will evolve from a background compliance function into a strategic business capability over the next several years. Organizations will need to demonstrate that the data feeding AI models is accurate, traceable, and explainable, not only for internal quality teams but also for regulators who will increasingly expect organizations to justify how AI-supported decisions were reached. I've already seen this shift on transformation projects where the most important discussions weren't about whether the model could perform the task. They were about whether the organization could explain exactly which data had been used and why.

User adoption will evolve as well. The future won't simply require people to operate digital systems. It will require them to know when to trust an AI recommendation, when to question it, and when human judgment should override it. That demands a different kind of digital confidence than organizations have traditionally focused on, and it's something that must be developed intentionally.

The organizations that lead clinical supply five years from now won't necessarily be those with the most advanced AI. They'll be the ones that invested early in trusted data, strong governance, and engaged, confident people. That combination, rather than the algorithm itself, is what will enable organizations to use AI responsibly when it matters most.

About The Expert:

Edwige Njiayap Nouboug is a BioPharma Deputy Lead at Sanofi with 15 years of experience in digital transformation, data governance, and user adoption across regulated industries, with a focus on life sciences.

Throughout their career, they have led global initiatives at organizations including Roche and Pierre Fabre, driving improved decision-making, operational excellence, and the successful adoption of digital platforms such as CRM and data governance systems in complex, highly regulated environments.

Passionate about translating complexity into practical business outcomes, Edwige shares insights through the newsletter From Clarity to Execution and writes regularly on digital transformation, governance, and leadership in the life sciences industry.