Managing Resistance

Why People Resist Change

Resistance to change is one of the most predictable and human responses in any transformation. It is not a character flaw, a sign of laziness, or evidence of disloyalty. It is a natural psychological response to perceived threat — and in banking, where change frequently threatens roles, skills, routines, and professional identities, it is inevitable.

Understanding why people resist is the essential first step to managing resistance effectively. Without this understanding, change managers resort to ineffective tactics — pushing harder, communicating louder, or escalating prematurely — that treat symptoms rather than root causes and often make resistance worse.

Loss of Control

Change is something that happens to people. Even when the change is objectively positive, the experience of having your daily work, your tools, your routines, and your team restructured by someone else creates a powerful sense of loss of control. In banking operations, where analysts take pride in their mastery of complex processes and systems, the imposition of new ways of working can feel like a fundamental loss of agency.

The antidote to loss-of-control resistance is involvement. People who participate in designing the change, testing the new system, or shaping the new process feel ownership rather than imposition. They become co-creators of the change rather than passive recipients.

Uncertainty About the Future

Humans are wired to fear uncertainty. A known-but-imperfect present feels safer than an unknown future. In banking, uncertainty takes many forms: Will I still have a job? Will I be able to learn the new system? Will my expertise still be valued? Will my team be restructured? Will I report to a new manager? When the programme has not provided clear answers to these questions — or when answers have been provided but are not trusted — uncertainty fills the vacuum and resistance grows.

The antidote to uncertainty resistance is clarity and honesty. Providing clear, specific, honest information about what will change, what will not change, and what is still being decided reduces the space for speculation and fear. Where decisions have not yet been made, saying "this decision will be made by [date] and we will communicate immediately" is far more effective than silence.

Competence Fears

Perhaps the most personal and emotionally charged source of resistance in banking is the fear of becoming incompetent. A senior analyst who has spent fifteen years mastering the current system and is recognised as the team's go-to expert faces a deeply unsettling prospect: starting over as a beginner on a new platform. The new system threatens not just their technical skills but their professional identity and status within the team.

Competence fears are particularly acute in banking because expertise is a primary source of credibility and career progression. Being the person who "knows how everything works" carries significant professional value. A change that resets this accumulated expertise to zero provokes anxiety that is entirely rational.

The antidote to competence-fear resistance is training, support, and time. Providing comprehensive, high-quality training that builds confidence progressively, offering buddy systems and coaching that provide safe support during the learning curve, and — critically — communicating that the organisation values and will invest in developing people's new capabilities rather than discarding their old ones.

Past Failures and Broken Promises

In many banks, staff have experienced multiple change programmes that were poorly managed, over-promised, under-delivered, or abandoned. "We have seen this before" is one of the most common resistance statements in banking operations. If the last technology migration was chaotic, the training was inadequate, and the promised benefits never materialised, people will approach the next initiative with deep scepticism.

Past-failure resistance is particularly difficult to address because it is rooted in direct experience. The antidote is demonstrable credibility — showing through actions (not just words) that this time is different. Early wins, honest communication, visible leadership commitment, and genuine investment in training and support gradually rebuild trust. But it takes time, and the programme must earn credibility through consistent delivery rather than claiming it through rhetoric.

Legitimate Concerns About the Change Design

Not all resistance is emotional or irrational. Sometimes people resist because they have identified genuine problems with the change that the programme team has not recognised. A settlements analyst who says "this new matching algorithm will not work for cross-currency trades because it does not account for the value-date offset" is not resisting change — they are providing expert feedback that could save the programme from a significant design flaw.

The antidote is listening. Change managers must create channels for resistance to be expressed and genuinely heard. Not all feedback will be valid, but dismissing resistance wholesale risks missing the most valuable insights the programme receives.

Types of Resistance

Resistance manifests in two fundamentally different ways, and each requires a different management approach:

Active Resistance

Active resistance is visible and vocal. It includes:

• Open challenge — directly questioning the rationale for change in meetings, raising objections, and arguing against decisions
• Formal opposition — submitting formal objections, raising grievances, or involving union or works council representatives
• Refusal — explicitly refusing to participate in training, use the new system, or follow the new process
• Negative advocacy — actively trying to persuade colleagues to resist, spreading negative narratives, or undermining confidence in the programme

Active resistance, while uncomfortable, is actually easier to manage than passive resistance because it is visible. You can engage with it, understand its root causes, and address it directly. Active resisters are often the people who care most about the organisation and the work — their energy can potentially be redirected from opposition to constructive contribution.

Passive Resistance

Passive resistance is silent and hidden. It includes:

• Surface compliance — attending training, acknowledging the change, but not actually adopting the new way of working. People go through the motions but quietly revert to old practices whenever possible.
• Disengagement — withdrawing effort and enthusiasm. People stop volunteering, stop contributing ideas, and do the minimum required.
• Workarounds — finding ways to avoid using the new system or process, often by maintaining shadow processes, personal spreadsheets, or informal arrangements that bypass the new way of working.
• Delay and procrastination — continuously finding reasons to postpone adoption: "I will start using the new system next week," "I am too busy to attend training right now," "I need more time to prepare."
• Selective adoption — adopting the easy parts of the change while ignoring the harder parts. For example, using the new system for data entry but continuing to run reconciliations in the old spreadsheet.

Passive resistance is far more dangerous than active resistance because it is invisible to the programme. The programme's metrics may show that everyone has been trained, everyone has system access, and everyone is logging in — but actual adoption may be far lower than it appears. Passive resistance only becomes visible when adoption metrics are measured rigorously, when quality assurance reviews reveal inconsistent practice, or when the old system is finally decommissioned and people who have been relying on workarounds are suddenly exposed.

Identifying Resistance Early

Early identification of resistance is critical because resistance that is addressed early is far easier to resolve than resistance that has hardened over weeks or months. Warning signs include:

Behavioural indicators: Increased absenteeism (particularly around training dates), declining participation in team meetings, reduced engagement with programme communications, increased questions or complaints to HR, and a noticeable shift in team morale.

Performance indicators: Declining productivity during the transition period (beyond the expected temporary dip), increasing error rates, missed deadlines, and growing backlogs.

Social indicators: Negative conversations in informal settings (the canteen, the corridor, messaging groups), sarcastic comments about the programme, and the formation of vocal opposition groups.

Adoption indicators: Low training completion rates, low system login rates, continued use of old systems or workarounds, and poor scores on post-training assessments.

Change champions are your early warning system. Because they are embedded in the affected teams and trusted by their peers, champions hear the real conversations, see the real behaviours, and can report emerging resistance before it becomes entrenched. Regular, structured check-ins with champions — "What are you hearing? What concerns are coming up? Who is struggling?" — are one of the most valuable resistance management tools available.

Root Causes vs Symptoms

A critical skill for change managers is the ability to distinguish between the symptom of resistance and its root cause. Treating symptoms without addressing root causes is like treating a fever without diagnosing the infection — the symptom may temporarily subside but will return.

Diagnosing root causes requires empathetic, non-judgemental inquiry. Instead of asking "Why are you resisting this change?" (which puts people on the defensive), ask "What concerns do you have about how this will affect your work?" or "What would help you feel more confident about the transition?" These questions open dialogue rather than shutting it down.

Strategies for Addressing Resistance

Involvement

Involve resistant individuals and groups in the change process. Ask for their input on design decisions, invite them to participate in testing and piloting, and give them a voice in shaping the implementation approach. Involvement transforms people from objects of change to agents of change. In banking, involvement might mean asking experienced analysts to test the new system and provide feedback, appointing respected resisters as advisory group members, or soliciting input on the training design.

Communication

Increase the frequency, specificity, and honesty of communication. Address concerns directly rather than ignoring them. If people are worried about job security, address job security directly — with facts, not platitudes. If people are confused about the timeline, provide a clear, detailed timeline. If people feel uninformed, increase communication cadence and create additional channels for questions.

Support

Provide practical support that directly addresses the barriers people are facing. If the root cause is competence fear, provide additional training, coaching, and buddy support. If the root cause is workload concern, provide temporary additional resource during the transition. If the root cause is personal anxiety, provide access to employee assistance programmes, career counselling, or stress management support.

Negotiation

In some cases, resistance reflects legitimate interests that can be addressed through negotiation. A team lead who resists because the new operating model eliminates their management role may be more receptive if offered an alternative career path — perhaps as a senior specialist, a training coordinator, or a process improvement lead. In banking, where works councils and staff representative bodies have formal negotiation rights, this strategy may involve formal consultation processes.

Recognition and Incentives

Recognise and reward early adopters. When people see that colleagues who embrace the change are being recognised, celebrated, and supported — rather than those who resist — it shifts the social dynamic. Recognition does not need to be financial; public acknowledgement, new responsibilities, and career development opportunities are often more powerful.

When Resistance Is Legitimate Feedback

Not all resistance should be overcome. Sometimes resistance is the most important feedback the programme receives. Change managers must be able to distinguish between resistance that stems from emotional reactions (which should be managed empathetically) and resistance that stems from genuine operational insight (which should be listened to and acted upon).

Signs that resistance is legitimate feedback include:

• The concern is specific and evidence-based rather than general and emotional
• The concern is raised by subject matter experts with deep operational knowledge
• Multiple people in different teams raise the same concern independently
• The concern relates to operational risk, compliance, or customer impact — areas where front-line staff often have better visibility than the programme team
• The concern was not addressed in the programme's impact assessment or risk register

When resistance is legitimate feedback, the appropriate response is not to manage the resistance — it is to modify the change. Incorporate the feedback into the design, adjust the implementation approach, or add mitigations that address the identified risk. This not only produces a better outcome but also demonstrates to the wider population that the programme listens and responds — building trust and reducing future resistance.

Escalation and Intervention

Despite best efforts, some resistance cannot be resolved at the change management team level. Escalation to senior leadership is appropriate when:

• Resistance is sustained — it has persisted despite multiple interventions over a meaningful period (typically 4-6 weeks)
• Resistance is widespread — it is affecting a significant proportion of the affected population, not just isolated individuals
• Resistance is blocking adoption — it is preventing the change from being implemented or undermining adoption to the point where benefits cannot be realised
• Resistance is led or amplified by middle management — managers who resist have an outsized impact because they influence their entire team. Only senior leadership has the authority to address management-level resistance directly

Senior leadership intervention should be:

• Clear and direct — the senior leader should meet with the resistant manager or group, acknowledge their concerns, and clearly state the expectation that the change will be adopted
• Supportive but firm — offering additional support where legitimate needs exist, while making clear that sustained resistance is not an acceptable option
• Followed up — a single intervention is rarely sufficient. The senior leader should follow up to verify that the situation has improved and that adoption is progressing

In extreme cases — where an individual's resistance is wilful, sustained, and damaging despite every reasonable intervention — formal performance management may be necessary. This is a last resort and should be managed through the HR function with appropriate documentation and process.

Banking Example: Overcoming Analyst Resistance to Automation in Settlements

A European bank was implementing robotic process automation (RPA) in its securities settlements processing team. The automation would handle approximately 70% of routine settlement instructions that were currently processed manually by a team of 45 analysts. The remaining 30% — complex trades, exceptions, and fails — would continue to require human processing and investigation.

The programme anticipated some resistance but was surprised by its intensity. Within two weeks of the announcement, multiple analysts had expressed strong opposition. Several experienced analysts threatened to leave. Team morale dropped sharply. Training attendance for the first scheduled session was only 60%.

The change management team conducted a rapid resistance diagnostic through a combination of anonymous surveys, change champion feedback, and one-to-one conversations with key individuals. The diagnosis revealed three distinct root causes:

Root Cause 1: Fear of job loss. The most visceral concern was that automation would eliminate analyst positions. Despite programme communications stating that "no roles will be made redundant," analysts did not trust this assurance — partly because a different department in the same bank had undergone automation two years earlier and had subsequently reduced headcount by 30%. The official message ("no redundancies") was contradicted by institutional memory ("that is what they said last time").

Response: The Head of Securities Operations met personally with every team member in groups of 5-6 over two weeks. She was direct: "The volume of settlements we process is growing by 15% year-on-year. Automation will handle the routine work, freeing you to manage the complex trades, exceptions, and fails that are growing faster than we can hire. We need every one of you — but we need you doing higher-value work." She presented specific data showing the volume growth projections and the capacity gap that automation was designed to fill. She also made a concrete commitment: no compulsory redundancies for 24 months, with a skills development programme to prepare analysts for the higher-value exception management role.

Root Cause 2: Identity and expertise threat. Several long-tenured analysts had built their professional identity around their expertise in manual settlement processing. They were the go-to people for complex instruction formats, unusual settlement conventions, and obscure counterparty requirements. Automation did not value this expertise — it processed every instruction using the same rule-based logic. These analysts felt that their years of accumulated knowledge were being rendered worthless.

Response: The programme explicitly acknowledged and honoured this expertise. The most experienced analysts were invited to become "exception management specialists" — a new role that leveraged their deep knowledge to investigate and resolve the complex cases that automation could not handle. They were also asked to serve as subject matter experts for the RPA configuration team, helping to define the business rules that the automation would follow. This reframed their expertise from "threatened by automation" to "essential for automation" — their knowledge was not being discarded, it was being codified and amplified.

Root Cause 3: Competence fear about the new monitoring tools. Even analysts who accepted the rationale for automation were anxious about the new exception management tools they would need to learn. The monitoring dashboard, the exception investigation interface, and the automated reporting tools were all new — and the legacy processing skills they had spent years developing were not transferable.

Response: The training programme was redesigned with additional support for this population. Instead of the standard three-day classroom training, these analysts received five days of classroom instruction with extra sandbox practice time, followed by four weeks of buddy support (paired with members of the pilot team who had already become proficient). A dedicated coach was assigned to the team for six weeks post-go-live to provide at-the-desk support.

Outcome: Within six weeks of the targeted interventions, resistance had transformed into cautious acceptance. Training attendance rose to 95%. The four exception management specialist roles were filled by the four most experienced analysts — the very individuals who had initially been the most vocal resisters. Post-go-live adoption was strong: within eight weeks, 100% of routine settlements were being processed by the RPA, and the exception management team was operating effectively with the new tools. The anonymous pulse survey conducted three months after go-live found that 78% of analysts rated the change as "positive" or "very positive" — compared to only 25% at the point of announcement.

The lesson from this example is clear: resistance is not the enemy. It is a signal. When the change management team invested time in understanding the root causes — rather than simply pushing harder — they were able to design targeted, empathetic interventions that addressed the real concerns and converted resisters into advocates.

In the next module, we will explore how to sustain change and embed new behaviours so that the transformation delivers lasting results.