Blog
›
People & Performance

Change Management in the Pharmaceutical Industry: How to Lead Change Without Disrupting GMP Operations

Why approved changes fail to stick in GMP plants, and how to lead adoption, not just compliance.

Change Management in the Pharmaceutical Industry: How to Lead Change Without Disrupting GMP Operations

Approving a change is not the same as adopting it. Yet many organizations believe a change control system and a shared vision roadmap are enough. They are not.

Fewer than one in three executives surveyed by McKinsey in 2021 reported that their companies’ organizational transformations had both improved performance and sustained those gains over time. Pharma is no exception. Only 11% of health care and life sciences transformation programs fully achieve their targets, according to a 2026 Bain & Company analysis.

In a good manufacturing practice (GMP) plant, a change that is not adopted is more than a missed performance target. It can also become a compliance risk.

Change control protects product quality; change management gets people to adopt the change. Transformations fail when companies comply with the first and neglect the second, or when leaders approve a change but do not keep championing it until it sticks.

This article explains how change management in the pharmaceutical industry differs from change control, why pharma transformations fail and what to do differently, drawing on LaSalle Group’s experience in regulated plants.

What is change management in pharma?

In the pharmaceutical industry, change almost always has two elements. Change control is the formal pharmaceutical quality system process used to propose, evaluate, approve, implement and review changes, as described in ICH Q10. Change management is the discipline of getting people to adopt a change and sustain it as their new way of working.

The two are related but fundamentally different. Change control ensures that a change does not negatively affect product quality. EU GMP Annex 15 defines it as “a formal system by which qualified representatives of appropriate disciplines review proposed or actual changes that might affect the validated status of facilities, systems, equipment or processes. The intent is to determine the need for action to ensure and document that the system is maintained in a validated state.”

Change management aims to ensure that people embrace the change as a new way of working. In practice, that is not always how it turns out. The workplace transformation consultancy Corporate Rebels summed up how change management works in many companies: “Let’s make decisions FOR people and then blame them when it fails.”

Why pharma is different

In a GxP environment, everything must be documented, validated and ready for inspection by the U.S. Food and Drug Administration (FDA) and other regulatory bodies. The International Society for Pharmaceutical Engineering (ISPE) describes GMP as “a system for ensuring that products are consistently produced and controlled according to quality standards. It is designed to minimize the risks involved in any pharmaceutical production that cannot be eliminated through testing the final product.”

That rigor can create a blind spot: Organizations focus so closely on meeting formal quality and compliance requirements that they overlook the human factors that make a change stick. When a project closes in a GMP environment, it is easy to confuse “compliant” with “adopted.” Even the terminology blurs the line: ICH Q10 uses the term “change management system” (section 3.2.3) for what manufacturing sites call change control. It covers how to evaluate a change, including its effectiveness after implementation, but not how to get people to adopt it.

Change management vs. change control

Knowing the difference between change control and change management is more than a question of terminology. It determines how a change is executed, who is responsible for each part of it and where each process applies. The table below compares the two.

Change control vs. change management
Change control (ICH Q10 “change management system”)Change management (organizational)
What it isFormal quality system process to propose, evaluate, approve, implement and verify changes that may affect product quality or marketing authorization.The discipline of getting people to adopt a change and sustain it over time.
What it managesThings: processes, equipment, materials, methods, computerized systems, documents, suppliers, sites.People: behaviors, roles, habits, ways of working.
When it appliesMandatory for any change to something validated, qualified or committed in a regulatory filing.Whenever success depends on people working differently.
Who owns itA change owner and a cross-functional team (production, QA, QC, regulatory, validation, engineering). The quality unit approves (21 CFR 211.22 and 211.100).An executive sponsor, line leaders, supervisors and change agents, with HR and training support. QA is not the owner.
When it is doneThe change is implemented and verified with no negative impact on quality, and the change request is closed.The new behavior holds without supervision, and results do not regress.
What happens if it failsFDA Form 483 observation, warning letter, product recall.The plant complies on paper but reverts to the old way: workarounds, downstream deviations and a return on investment that never appears.

Where the two overlap

An enterprise resource planning (ERP) or manufacturing execution system (MES) implementation triggers both. It needs change control for computer system validation (CSV) or computer software assurance (CSA), and change management so employees actually use the new system in their daily work. Change control helps ensure that the software meets applicable regulatory and quality requirements. Change management helps employees learn the system and build it into their daily workflow.

CSV is the FDA’s term for confirming, through objective evidence, that software meets user needs and its intended uses, and that its requirements can be consistently fulfilled. CSA is the FDA’s newer risk-based approach to establishing confidence that software is fit for its intended use.

Neither works without a multidisciplinary team. Both processes require cooperation across departments, including Quality, IT and production. The most common mistake LaSalle’s experts see is siloed ownership: “That’s Quality’s problem, not mine.”

Who should own change management?

Change management should be a shared responsibility. An executive sponsor provides leadership, supported by line leaders, supervisors and change agents, with HR and training support. The quality unit keeps its responsibility for reviewing and approving changes under GMP requirements, but it should not own adoption. Quality, Operations and HR should be involved from the start, not brought in after problems appear.

Why pharma transformations fail

Even successful transformations fall short. Executives estimate that companies capture only 67% of the potential value of their transformations, and that 55% of the value loss happens during and after implementation, according to the same McKinsey research. LaSalle’s experts see four root causes in regulated plants.

1. Leadership disengagement

Leaders approve the change, hand it off to execution teams and disappear. On the floor, the same questions keep coming up: “Does leadership know about this? Are they changing the way they work, too?” Change cannot just be approved at the top. It has to be led from the top all the way through sustainment. Leaders are expected to be part of the entire change process, because change does not depend on a single group. It depends on every level of the organization.

2. Poor communication at every level

Decisions are made only at the senior level and imposed on the people who execute them. Silos between departments create misaligned information, rumors and misunderstandings. LaSalle’s experts see communication as a recurring area for improvement in every organization they work with.

3. No pre-work and no post-work

Organizations focus on the change itself, not on preparing people for it. Change management is seen as a cost or a waste of time rather than a value driver. Consultants are often called in only after problems emerge.

4. Underestimating sustainability

Companies assume approval equals adoption and that a fixed timeline is enough. Change management is continuous, not a project with a finish line. Metrics and key performance indicators (KPIs) must be set from the start to track progress.

How to measure whether a change has been adopted

Define adoption metrics before implementation and keep tracking them after go-live. A change is successfully adopted when the new behavior holds without supervision and results do not regress. In practice, that means workarounds decline, downstream deviations do not increase and the expected return on investment appears. Training records and course completions show that people were informed. They do not show that people changed the way they work.

Leaders know change management matters. Why isn’t it a priority?

Change management is a risk-avoidance strategy. A change that is approved but not fully adopted can put both a project’s return on investment and the company’s regulatory compliance at risk. Yet change management is often perceived as an expense rather than an investment. Companies focus on technology instead of people and assume change control already covers it.

Only 32.5% of executives surveyed by Deloitte said their companies use outside partners to help manage the changes introduced by smart manufacturing initiatives, even though they rely heavily on outside partners for the technology itself, according to the firm’s “2025 Smart Manufacturing Survey.”

Signs you may need outside support

When to keep it in-house

Keep change management in-house when the scope is smaller and the internal capability, capacity and experience already exist. In small and midsize organizations, the ideal leader is someone on the internal team who has managed a similar change.

Leading change in a GMP environment: 5 mistakes to avoid

Whether change is led internally or with outside support, LaSalle’s experts see the same five mistakes again and again.

Case study: Two transformations, two outcomes

Similar technology projects can fail or succeed depending on how the people involved are managed. Below, we compare a manufacturing execution system implementation that reached 100% adoption before go-live with an ERP rollout that ended in low adoption and passive boycott. Both companies are anonymized.

Company A
Company A is an aseptic parenteral manufacturing site that moved from paper-based records to an MES to improve traceability, reduce documentation errors and speed up batch release. Many of its operators had used paper records for more than 20 years, which made the move to digital tools a significant change for the people on the floor.

Company B
Company B is a regulated food manufacturing site. After its ERP system of more than 20 years was discontinued, the company needed to move to a new software provider. The technology gap between the old system and the new, cloud-based system required significant IT infrastructure and integration work. Unlike at Company A, the new system mainly affected supervisors and managers. The organization made key decisions without sufficient input from the people affected, communication was limited and staff had little opportunity to prepare for the new system.

Company A vs. Company B
Company A: MES implementation (successful)Company B: ERP rollout (chaotic)
Psychological frameworkTrust built. Security created through clear training plans and support. Recognition embedded in communication.Trust eroded by top-down communication and late involvement. People were reluctant to change the way they worked. Operations-level effort was overlooked.
Information flowFrequent, multichannel updates tailored to each audience.Infrequent, highly technical messages. Many employees learned of changes through rumors.
Decision-making approachDistributed decision-making: Frontline input shaped MES workflows.Centralized decisions made by executives and consultants. Operational staff excluded from key planning.
RecognitionEarly adopters publicly acknowledged. Milestones celebrated.No structured recognition. High effort went unnoticed, and some employees were penalized for not participating in deployment activities.
Result100% adoption before go-live. Higher employee productivity from a lighter documentation effort. Stronger morale and collaboration.Return to the previous system in less than a year. Surge in workarounds and internal support requests. Passive boycott.

Company A results: The site reached 100% operator adoption at rollout, 100% right-first-time documentation and zero documentation errors during implementation. It also cut batch release time by 42%, from 24 to 14 days.

Company B results: The company went live with the new system despite a passive boycott and a growing number of workarounds. In less than a year, it had to return to its previous system. The main reason: The organization did not integrate the change design recommendations made by its consultant.

What made the difference

Although the two projects differed in scope and technology, four management choices made the biggest difference in their outcomes. Each one maps to a cause of failure described earlier:

Company A reached 100% adoption before go-live, while Company B returned to its previous system in less than a year.

For another example of people-centered change in a regulated plant, see our cultural transformation case study in aseptic manufacturing.

Frequently Asked Questions

What is change management in the pharmaceutical industry?

Change management is the discipline of getting people to adopt a change and sustain it as their new way of working. In pharma, it complements change control, the formal pharmaceutical quality system process used to propose, evaluate, approve, implement and review changes, as described in ICH Q10.

What is the difference between change control and change management?

Change control manages things, such as processes, equipment, computerized systems and documents, and ensures that a change does not negatively affect product quality. The quality unit approves it. Change management manages people, and it is done when the new behavior holds without supervision and results do not regress.

Why do pharma transformations fail?

LaSalle’s experts see four root causes in regulated plants: leadership disengagement, poor communication at every level, no pre-work and no post-work, and underestimating sustainability.

How do you measure whether a change has been adopted?

Define adoption metrics before implementation and keep tracking them after go-live. A change is adopted when the new behavior holds without supervision and results do not regress: Workarounds decline, downstream deviations do not increase and the expected return on investment appears.

Compliant is not the same as adopted

Change control makes a change compliant. Change management makes it work and makes it last. Pharma needs both.

When a change is approved but not adopted, the plant complies on paper and reverts in practice, with workarounds, downstream deviations and a return on investment that never appears.

The fix is not more documentation. It is leaders who stay visible through sustainment, frontline teams involved in designing the change, shared ownership across Quality, Operations and HR, and adoption metrics that keep running after go-live.

To go deeper on the business case, read about the benefits of a change management process.

Planning a transformation in a GMP environment? Talk to LaSalle’s People & Performance team.

Contact Us

Book a meeting

Let’s talk about your goals, challenges, and the right path to measurable results.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.