The system goes live. The behaviour doesn’t.

Every clinical organisation has a version of this story. A new tool is selected, validated, configured and released. Training is delivered, the SOP is updated, the go live date passes without incident. Six weeks later the old spreadsheet is still circulating by email, because it is faster, because it is familiar, and because nobody ever made the case for stopping. 

Nothing failed. That is exactly what makes it difficult to fix. 

The problem is rarely the tool 

A global pharmaceutical company approached us recently to design a change management programme for a small group in compliance. The brief was unusually honest. The organisation was replacing a spreadsheet based risk assessment process with a new system, and the teams concerned were not enthusiastic. What made it interesting is that they were also dissatisfied with how risk assessment worked today. You might expect that to help. It did the opposite. They had strong, well formed views about the current process, and a new system arriving from somewhere else did not feel like an answer to those views. It felt like a different set of instructions. 

That pattern repeats across the sector, whatever the trigger: an eTMF migration, a shift to risk based quality management, a new CTMS, the introduction of AI assisted review, or the process rewrites that ICH GCP E6(R3) has set off in most quality functions. The technical implementation gets a plan, a timeline and an owner. The human implementation gets a kick off email and a training slot. 

Resistance is information, not an obstacle 

The instinct in a regulated environment is to treat reluctance as a compliance issue. The procedure is approved, the system is validated, adoption is mandatory. That framing wins the argument and loses the change, because compliance produces the minimum viable behaviour and nothing more. People will use the system in the meeting and keep the workaround on their desktop. 

Experienced clinical professionals rarely resist for the sake of it. They resist because they can see a cost the project plan has not accounted for: a step that used to take two minutes, a control they trusted, a judgement call the new workflow does not allow for. Those objections are the most valuable material available to anyone running a rollout. They are specific, they come from people who understand the work, and they surface every weak point in the design before an auditor does. 

Which is why the preparation we ask participants to do is deliberately uncomfortable. Write the change out on a single page, in your own words, as you would explain it to a colleague. Do it alone. Then write down every objection you expect to hear, and every genuine criticism people already have of the way things work today. Most participants discover two things. Their own version of the change is vaguer than they assumed, and the objections they expect are largely reasonable. 

Three questions, in the right order 

The method we use organises a change around three questions, worked in sequence, because taking them out of order is where most rollouts go wrong. 

Why, which is not the business case but the story: what the organisation is trying to become, and why the current way of working cannot get it there. This is the part that gets skipped, and it is the part people need first. Facts travel badly. Stories travel. 

How, meaning the concrete shifts that follow. What gets built, what gets dismantled, what people stop doing. This is where a change becomes real enough to argue with, which is the point. A change nobody can argue with is a change nobody has understood. 

What, meaning the actions, the sequence, the stakeholders, and the plan for the period in between, when the old way has gone and the new way is not yet automatic. Most organisations plan the destination and leave the transition to look after itself. The transition is where adoption is won or lost. 

From understanding to tactics 

Once the picture is clear, the question becomes practical: what do you actually do on Monday morning with a team that is not convinced. We work through seven levers for influencing mindset and behaviour, and build a specific plan for each one against the stakeholders in the room. Three of them motivate, three of them support, and the last is experience, which tends to matter more than the other six combined. Nothing shifts a sceptical professional faster than fifteen minutes of hands on contact with the thing they were arguing about. 

Impacting a mindset, not changing one 

One distinction is worth borrowing even if you never book a course. The people asked to lead a change are almost never the people who control the conditions around it. They cannot rewrite performance objectives, reallocate headcount or change how a department is measured. Setting out to change a mindset sets them up to fail, because too much of it sits outside their authority. 

Impacting a mindset is a different and achievable brief. It is about what can be influenced from where you actually stand. That reframing alone tends to change how a team talks about the people resisting them, which in turn changes how those people respond. 

Built around your change, in whatever shape fits 

There is no fixed format, because there is no fixed change. The programme above ran as two days with a small group, so the room could work on their real rollout rather than a case study. Other situations call for something else: a half day with a leadership group who need to agree the story before anyone else hears it, modules spread across the rollout so the plan is tested against reality and revised as the change moves, or follow up coaching for the people who have to hold the line three months in, when the initial energy has gone. 

What stays constant is the output. Participants leave with a draft plan for their own change. Not a certificate and a set of slides, but the sequence of conversations, the coalition, the objections they will face and their answer to each, built in the room by the people who will have to deliver it. 

If you have a rollout that is technically on track and quietly stalling 

Change Management is available as a tailored course, built around the change you are actually managing rather than a generic model. Format, length and group size are yours to set, in house or at a location of your choice. It suits compliance, quality, regulatory and clinical operations teams introducing a new system, a new process, or a way of working the organisation has not asked for. 

Tell us what is changing, who has to carry it and how much time you can release. We will come back with a programme built around that, not around our catalogue. 

info@eccrt.com | +32 (0)2 504 07 20 | www.eccrt.com