Varför förändring känns svår inom allmänmedicin

The video gives a topic overview and has a viewing time of around 5 minutes. The written learning guide offers a more in-depth exploration and has an approximate reading time of 10-15 minutes.

Learning objectives

By the end of this guide, you will be able to:

• Understand the specific factors that make change particularly difficult in practice settings.

• Recognise legitimate concerns beneath surface resistance.

• Identify structural and emotional barriers to change in your own practice.

• Approach change with empathy while maintaining momentum.

• Distinguish between resistance that needs addressing and concerns that need listening to.

Why this matters

Change is exhausting. Particularly in general practice, where it feels relentless.

New contract arrangements. Software updates. Regulatory requirements. Workforce models. Reorganisations you didn't ask for and can't control. And on top of all that, the changes you actually want to make (improving processes, developing the team, trying new approaches) which somehow feel just as hard.

When people resist change, it's tempting to dismiss it as stubbornness or fear of progress. Sometimes that's true. But more often, resistance signals something worth understanding. People aren't resisting to be awkward. They're responding to genuine difficulties that general practice creates.

One useful way to understand why change feels so hard is to look at a combination of structural pressures and human responses. This doesn't make change easy, and it doesn't mean you should avoid it. But it does help you lead it with more empathy, more realism, and more chance of success.

The context: change fatigue is real

Before we get to why any specific change is difficult, there's the background reality. General practice has been through relentless change for years.

Contract changes. Pandemic adaptations. Digital transformation. Workforce crises. PCN formation. Reorganisations at every level. Changes imposed from outside that you have to implement but didn't choose and don't always agree with.

This creates change fatigue. People are tired. They've adapted and adapted and adapted. And now you're asking them to change something else.

This isn't resistance to your specific change. It's exhaustion from the cumulative weight of constant change. People don't have unlimited capacity for adaptation, particularly when much of that adaptation has been reactive, stressful, and forced upon them.

When someone says "not another change," they might not be opposing what you're proposing. They might be saying "I don't have anything left in the tank."

This doesn't mean you shouldn't make necessary changes. It means you need to recognise what people are carrying and factor that into how you approach it.

Why change is structurally harder in general practice

Beyond general change fatigue, there are specific structural realities that make change particularly difficult in practice settings.

Small teams with high interdependence

In a large organisation, you can pilot changes in one department, shield some people from disruption, or phase implementation gradually. In a small practice, everyone is affected by everything.

If you change the appointment system, everyone notices. Receptionists, GPs, nurses, patients, the practice manager. There's nowhere to test it quietly. No department that can carry on as normal while others adapt.

This means every change is high stakes and highly visible. People can't opt out or wait and see. They're all in, immediately. This raises the emotional temperature of any change and makes people more cautious about agreeing to it.

Partnership decision-making models

Many practices operate on partnership models where everyone has a voice (or a vote, or effectively a veto). This makes decision-making slow and consensus hard to reach.

One partner who's opposed can block a change. Or grudgingly agree but undermine it through lack of enthusiasm. Unlike hierarchical organisations where leadership can make a call and move forward, practices often need widespread buy-in before anything can happen.

This creates ownership and prevents poor decisions being imposed. But it also means change can stall even when the majority support it, and the process of getting there is slow and energy-intensive.

Patient relationships and continuity

Changes that might be simple in other organisations become complicated when patient care and relationships are involved.

Changing a GP's session patterns affects their patients who are used to seeing them on Tuesdays. Changing the phone system affects how patients access care. Even internal changes (who does visits, how referrals are managed) can impact patient experience and continuity.

This means you can't just optimise for efficiency or staff preference. You have to balance it against patient impact. And patients themselves often resist change. They liked the old system. They're used to the familiar receptionist. They don't want to adapt.

This doesn't mean you can't make changes. It means you need to think through patient impact and manage it actively, which adds complexity.

Regulatory and compliance burden

Some changes trigger additional regulatory or administrative work. Changing clinical software isn't just a technology project. It's a CQC consideration, a data migration challenge, a training requirement, and a patient information governance issue.

This means even sensible changes come with bureaucratic weight that makes them feel disproportionately difficult. The change itself might be straightforward. The compliance work around it isn't.

Clinical autonomy versus standardisation

General practice values clinical autonomy. GPs are trained to think independently, make their own decisions, adapt to individual patients. This is a strength.

But it creates tension when change requires standardisation. Implementing a consistent approach to chronic disease management, or a standardised referral process, or a unified prescribing approach can feel like an imposition on clinical judgement.

People may resist not because they're being difficult, but because they're protecting something they believe is important (individualised patient care, professional autonomy). The change might still be necessary. But understanding what's at stake helps you address the concern rather than dismiss it.

Why change is emotionally harder than we acknowledge

Beyond structural barriers, there are emotional and psychological reasons change feels difficult.

Loss and grief

Every change involves loss. Even good changes. You're asking people to give up something familiar, comfortable, or valued in exchange for something uncertain.

The old appointment system might have been inefficient, but people knew how it worked. They had mastered it. Changing it means giving up that mastery and becoming a learner again. That's uncomfortable.

People can simultaneously believe a change is necessary and grieve what's being lost. Understanding this doesn't mean you abandon the change. It means you acknowledge the loss rather than dismissing it.

Lack of control

Much of the change in general practice is imposed from outside. NHS reorganisations, contract changes, regulatory requirements. People have adapted to things they didn't choose and couldn't prevent.

This creates a background feeling of powerlessness. So when you introduce yet another change (even one that's genuinely beneficial and practice-led), people's response is shaped by that sense of having no control.

The resistance might not be to your specific change. It might be to the feeling of powerlessness. Acknowledging this and giving people agency where possible makes a difference.

Fear of competence loss

People have built competence in current ways of working. They know how to do things. They're good at their jobs. Change threatens that.

A new clinical system means they'll be slower, make more mistakes, feel less competent. A new way of working means their accumulated expertise is suddenly less valuable. Even if the new way is better, the transition period where they feel incompetent is genuinely threatening.

This is particularly acute for people whose identity is built around being competent. Admitting they don't know how to use the new system, or asking for help, can feel like failure.

Understanding this fear doesn't mean you avoid necessary changes. It means you provide proper support during the transition and acknowledge that the learning curve is real.

Past experience and pattern recognition

Some resistance is based on experience. "We tried something like this before and it didn't work." "The last three initiatives were abandoned halfway through." "This sounds good in theory but won't work with our patient population."

This isn't always stubbornness. Sometimes it's valid organisational memory. Sometimes previous attempts genuinely did fail, and the concerns being raised are worth considering.

The challenge is distinguishing between useful caution based on experience and cynicism that blocks all progress. Both can sound similar on the surface.

Uneven impact

Changes rarely affect everyone equally. What seems like a minor adjustment to one person is a major disruption to another.

Moving to online appointment booking might be easy for tech-confident staff. For those less comfortable with technology, it's a significant challenge. The people pushing the change (often those least affected by it) can underestimate how difficult it is for those most affected.

This doesn't mean you can't make changes that affect people unevenly. But it does mean you need to recognise the uneven impact and provide support accordingly.

The specific challenge of partnership dynamics

Partnership models create particular change challenges worth naming explicitly.

Consensus without authority

In partnerships, you can't simply make a decision and implement it. You need agreement. This means even obviously beneficial changes can stall if one partner is unconvinced or uncomfortable.

This is democratically fair but operationally slow. It also means the person with the most concerns (or the most persistence in raising them) can effectively slow or prevent progress.

This doesn't mean partnership models are wrong. But it does mean change takes longer and requires more investment in building agreement.

Conflict avoidance

Partners often avoid conflict with each other because they have to continue working together long-term. This means difficult conversations about change get deferred or diluted.

Rather than having a direct discussion about disagreement, partnerships sometimes resort to passive resistance or endless discussion that goes nowhere.

The change might still be necessary. But the partnership dynamic makes it harder to have the honest conversations needed to move forward.

Unequal stakes

Partners might have different time horizons or different stakes in a change. A partner nearing retirement has different interests from one planning to be in the practice for twenty more years.

This creates misaligned incentives around change. What seems urgent and important to one partner feels like unnecessary disruption to another. Neither is wrong. But the misalignment makes agreement harder.

Historical precedent

"We've always done it this way" carries particular weight in partnerships because "we" includes the people in the room. Changing approaches can feel like criticising past decisions that current partners made.

This isn't impossible to navigate, but it requires sensitivity. You're not just changing a process. You're implicitly saying the old way wasn't optimal, and that can feel personal.

Why some changes fail

It's worth acknowledging that not all change initiatives succeed, and failure isn't always about poor implementation or resistance.

The change itself was flawed

Not every change is a good idea. Sometimes the new system is genuinely worse than the old one. Sometimes the solution doesn't fit the problem. Sometimes the timing is wrong.

When people raise concerns, sometimes they're identifying genuine flaws you haven't seen. The challenge is staying open to this possibility whilst not letting it paralyse all progress.

Insufficient resource or support

Some changes fail because they weren't properly resourced. New system implemented but no training provided. New process introduced but no time allocated to learn it.

People aren't resisting. They're accurately identifying that the change can't succeed without more support. If you push ahead anyway, the change will likely fail, and people will be even more skeptical of the next one.

Poor implementation

Sometimes the change itself is sound but the implementation is poor. Rolled out too quickly, communicated badly, imposed without consultation.

The failure isn't in the destination. It's in the journey. People might have supported the change if it had been introduced differently.

Competing priorities

A change initiative can be good in isolation but still fail because it's competing with too many other priorities. People have finite attention and energy. If three initiatives are running simultaneously, none may succeed.

This isn't resistance to change. It's realistic assessment of bandwidth. Sometimes the right answer is to sequence changes rather than trying to do everything at once.

What this means for leading change

Understanding why change feels hard doesn't make it easy. And it doesn't mean you shouldn't pursue necessary changes. But it should shape how you approach them.

Start with empathy, but maintain direction

People aren't refusing to see the obvious benefits. They're carrying the weight of previous changes, worrying about legitimate concerns, and protecting things they value.

Lead with understanding, not dismissal. "I know this is the fourth major change this year and everyone's tired" acknowledges reality. But follow it with "And this still needs to happen because..." Don't let empathy turn into avoidance.

Listen to concerns without being paralysed by them

Not all resistance is obstruction. Sometimes people are identifying genuine problems or risks you haven't thought through. Listen properly.

But don't let concerns become an excuse for indefinite delay. The question isn't "Is anyone concerned?" (someone always is). It's "Are the concerns significant enough to change course, or can we address them whilst still moving forward?"

Acknowledge what's being lost

Even good changes involve loss. Name it. "I know this means giving up the familiarity of the current system and that's uncomfortable." Don't minimise or dismiss it.

But also be clear about what's being gained and why the trade-off is worth it.

Make space where you can, but don't wait for perfect timing

If people are genuinely at capacity, adding another change might be the thing that breaks them. Sometimes you need to wait, or stop something else to create space.

But be careful not to let "we don't have capacity" become a permanent excuse for avoiding necessary change. There's rarely perfect timing in general practice.

Be willing to adjust, but not to abandon

Hold your plan lightly. If people raise valid concerns or identify flaws, be willing to adapt your approach.

But distinguish between adapting and abandoning. Some changes are necessary even when they're difficult. Empathy doesn't mean endlessly deferring.

Practical strategies: moving forward despite difficulty

1. Be honest about what's negotiable

Distinguish clearly between what's fixed and what's flexible. "This regulatory requirement is happening whether we like it or not. What we can control is how we implement it."

People can handle difficult changes better when they have agency over some elements, even if the overall direction is set.

2. Involve people in solving problems, not just implementing solutions

Don't arrive with a fully formed change plan. Involve people in defining the problem and exploring options. They'll raise concerns you haven't thought of and may spot flaws in your thinking.

This makes the change more robust and builds ownership. But don't let involvement become endless consultation that never reaches a decision.

3. Sequence rather than overwhelm

If multiple changes are needed, be deliberate about the order. Implement one, let people consolidate, then move to the next. This is slower but more sustainable than trying to do everything simultaneously.

Sometimes urgency means you can't sequence. But often you can, and choosing not to creates unnecessary overwhelm.

4. Provide genuine support during transitions

If people are going to feel incompetent during a learning curve, acknowledge that and provide proper training, time, and support. Don't just announce the change and expect people to figure it out.

Investment in the transition isn't optional if you want the change to succeed.

5. Recognise adaptation effort

People rarely get acknowledged for the enormous effort of adapting to change. "I know learning this new system has been frustrating. I appreciate you persevering with it."

This doesn't make the change easier but it makes the effort feel valued, which builds capacity for future changes.

6. Follow through

Nothing creates cynicism faster than changes that are announced with great fanfare then quietly abandoned when they get difficult. If you're going to initiate a change, commit to seeing it through.

If you need to abandon it, be explicit about why and what you've learned, rather than just letting it fade away.

Viktiga punkter

• One useful way to understand why change feels hard is to look at structural pressures (small teams, partnership models, patient relationships, regulatory burden, autonomy versus standardisation) combined with human responses.

• Change fatigue is real in general practice. People have limited capacity for further adaptation after years of imposed change.

• Resistance often signals legitimate concerns (fear of competence loss, grief over what's being lost, past experience, uneven impact) rather than stubbornness.

• Partnership dynamics (consensus without authority, conflict avoidance, unequal stakes, historical precedent) make change particularly slow and complex.

• Some changes fail because they were flawed, under-resourced, poorly implemented, or competing with too many other priorities.

• Understanding why change is hard doesn't mean avoiding it. It means approaching it with empathy whilst maintaining momentum.

• Effective change leadership involves listening to concerns without being paralysed by them, acknowledging loss whilst being clear about necessity, and providing genuine support during difficult transitions.

Actions: try this week

1. Map the change landscape: List all the significant changes your practice has been through in the last 18 months. How many were chosen versus imposed? What's the cumulative impact on people's capacity?

2. Listen to one concern properly: Next time someone resists a change you're proposing, ask: What legitimate concern might underlie this? What are they worried about losing? What past experience might be shaping their response? Listen without immediately defending the change.

3. Assess capacity honestly: Think about a change you're planning. Does the team genuinely have capacity for this right now? If not, what would need to stop or wait to create space?

4. Be clear about what's negotiable: For one current or planned change, articulate clearly: What's fixed (must happen)? What's flexible (can be adapted based on input)? Communicate this distinction explicitly.