Change Management Fundamentals

Why Change Management Matters in Banking

Banking is an industry in constant transformation. Regulatory reform, technological disruption, competitive pressure, and evolving customer expectations mean that financial institutions are continuously changing — their processes, their systems, their organisational structures, and the skills their people need. Yet despite the volume and pace of change, the industry has a troubling track record. Research consistently finds that approximately 70% of organisational change initiatives fail to deliver their intended outcomes. They go over budget, over time, or — most commonly — they deliver the technical solution but fail to achieve lasting adoption.

In banking, the consequences of failed change are amplified. A poorly managed migration to a new core banking platform does not just cause internal disruption — it can trigger regulatory scrutiny, customer complaints, financial losses, and reputational damage. When a bank fails to embed new anti-money laundering (AML) processes after a regulatory remediation programme, the result is not just wasted investment — it is continued regulatory exposure and the very real risk of enforcement action. When a settlements team resists a new automated matching system and reverts to manual workarounds, the bank is left paying for a system nobody uses while carrying the operational risk of the old process.

Change management is the discipline that bridges the gap between delivering a solution and achieving the intended outcome. It is the structured approach to preparing, equipping, and supporting individuals and teams to successfully adopt change and realise the benefits that the change was designed to deliver. Without it, even the most technically brilliant projects will underperform.

The Unique Challenges of Change in Regulated Environments

Change in banking is fundamentally different from change in unregulated industries. Several factors make it uniquely challenging:

Regulatory obligations constrain the pace and nature of change. Banks cannot simply redesign processes at will. Changes to transaction monitoring, regulatory reporting, capital calculations, customer data handling, and many other areas must be designed, tested, and implemented in ways that maintain continuous compliance. A gap in regulatory reporting during a system migration — even for a single day — can result in a supervisory finding. This means that change initiatives in banking must plan for parallel running, phased cutovers, and extensive regression testing to a degree that would be unnecessary in non-regulated environments.

Audit and compliance expectations add documentation burden. Every significant change in a bank generates audit trail requirements. The change must be documented — not just the technical design, but the impact assessment, the stakeholder engagement, the training delivered, the testing performed, and the post-implementation review. Internal audit and external auditors will review change management practices as part of their regular programmes. Regulatory bodies such as the ECB, PRA, and FCA expect banks to demonstrate that changes were managed with appropriate rigour and governance.

Risk appetite limits tolerance for disruption. Banks operate critical infrastructure. Payment systems, securities settlement, lending platforms, and treasury operations cannot tolerate extended outages. This creates a cultural conservatism around change — a healthy caution that, if not managed carefully, becomes an unhealthy resistance to any change at all. Change managers in banking must work within tight risk tolerances while still driving meaningful transformation.

Deeply embedded operational cultures resist disruption. Banking operations teams often have long-tenured staff who have built their expertise and professional identity around current ways of working. A settlements analyst who has spent fifteen years mastering the manual reconciliation process has legitimate concerns about what automation means for their role. A compliance officer who has developed deep expertise in a particular regulatory reporting tool may view a system migration as a direct threat to their value. These are not irrational reactions — they are human responses that must be understood, respected, and addressed through structured change management.

Multiple stakeholders with competing interests. A single change initiative in banking may need to satisfy the business sponsor (who wants speed and cost savings), the compliance function (who wants regulatory continuity), the technology team (who wants architectural elegance), the operations staff (who want minimal disruption), the regulators (who want demonstrable risk management), and the auditors (who want documentation). Balancing these competing interests requires sophisticated stakeholder management that goes beyond simple project communication.

Kotter's 8-Step Model

John Kotter's 8-Step Change Model, first published in his 1996 book Leading Change, remains one of the most widely used frameworks for managing organisational transformation. The model provides a sequential, leadership-driven approach that is particularly effective for large-scale, strategic change programmes in banking.

Step 1: Establish a sense of urgency. The change must be positioned as necessary and time-sensitive. In banking, urgency often comes from regulatory mandates (a new regulation with a firm compliance deadline), competitive pressure (fintech disruption of a core product), or operational risk events (a significant processing failure that exposed systemic weaknesses). The key is to communicate not just that change is needed, but that the cost of not changing is unacceptable.

Step 2: Form a powerful guiding coalition. Change cannot be driven by a single individual. A coalition of senior leaders, respected middle managers, and influential front-line staff must be assembled to sponsor, guide, and champion the change. In banking, this coalition must span the key functions: operations, technology, compliance, risk, and the front office.

Step 3: Create a vision for change. The coalition must articulate a clear, compelling vision of the future state — what the organisation will look like after the change, and why that future is better than the present. The vision must be specific enough to guide decision-making but simple enough to communicate in five minutes or less.

Step 4: Communicate the vision. The vision must be communicated repeatedly, through multiple channels, by multiple people. In banking, this means town halls, team meetings, email updates, intranet articles, one-to-one conversations, and informal corridor discussions. The rule of thumb is that people need to hear a message seven times before it truly registers.

Step 5: Empower broad-based action. Remove barriers that prevent people from acting on the vision. In banking, barriers often include outdated policies, rigid approval processes, legacy system limitations, and middle managers who are quietly blocking progress. Empowerment means giving people the authority, resources, and skills to make the change happen.

Step 6: Generate short-term wins. Large banking transformation programmes can take years. Without visible, tangible wins along the way, momentum fades and cynics gain credibility. Short-term wins — a successful pilot, a measurable improvement in processing time, positive feedback from a regulator — provide evidence that the change is working and sustain the energy of the coalition.

Step 7: Consolidate gains and produce more change. Use the credibility from early wins to tackle bigger, more complex changes. In banking, early wins in one department can be used to build the case for rolling the change out to other departments, geographies, or product lines.

Step 8: Anchor new approaches in the culture. The final step is to embed the change into the organisation's culture, processes, and identity — so that the new way of working becomes "just the way we do things here." This requires updating policies, procedures, job descriptions, performance metrics, and training programmes to reflect the new reality.

Lewin's 3-Stage Model

Kurt Lewin's Change Model, developed in the 1940s, is one of the simplest and most enduring frameworks for understanding change. It describes change as a three-stage process:

Stage 1: Unfreeze. Before change can happen, the current state must be destabilised. People must come to understand why the existing way of doing things is no longer adequate. In banking, unfreezing often requires presenting compelling evidence: regulatory findings, operational loss data, benchmark comparisons with competitors, or customer complaint trends. The goal is to create enough discomfort with the status quo that people become open to change.

Unfreezing is particularly challenging in banking because the current state often "works" — it may be inefficient, risky, or costly, but it produces the required output. Convincing people to change something that appears to be working requires strong evidence and credible leadership.

Stage 2: Change (Transition). This is the implementation phase — introducing new processes, systems, structures, or behaviours. In banking, this stage is characterised by uncertainty, learning curves, and temporary productivity dips as people adapt to new ways of working. Effective change management during this stage requires intensive communication, hands-on support, and tolerance for mistakes as people learn.

Stage 3: Refreeze. Once the change has been implemented and is working effectively, it must be stabilised and embedded into business as usual. Refreezing involves updating standard operating procedures, embedding new KPIs, aligning performance management to the new expectations, and reinforcing the new behaviours until they become habitual.

The power of Lewin's model is its simplicity. It reminds change leaders that you cannot jump straight to implementation (Change) without first preparing people (Unfreeze), and that implementation alone is not enough — you must actively stabilise the new state (Refreeze) or the organisation will drift back to old habits.

The ADKAR Model

The ADKAR model, developed by Prosci, takes a different approach from Kotter and Lewin by focusing on individual change rather than organisational change. ADKAR recognises that organisations do not change — people do. For the organisation to change, each individual affected by the change must successfully move through five sequential stages:

Awareness — Understanding why the change is happening. "I understand that our current AML transaction monitoring system cannot meet the new regulatory requirements, and we need to migrate to a new platform."

Desire — Wanting to participate in and support the change. "I accept that this migration is necessary and I am willing to learn the new system, even though it will be difficult." Desire is influenced by personal motivation, organisational culture, peer pressure, and trust in leadership.

Knowledge — Knowing how to change. "I have received training on the new platform, I understand the new workflows, and I know where to go for support." Knowledge is developed through training, coaching, documentation, and hands-on practice.

Ability — Being able to implement the change on a day-to-day basis. "I can actually perform my job using the new system — not just in a training environment, but in live production with real transactions and real time pressure." Ability requires practice, feedback, and time.

Reinforcement — Sustaining the change over time. "The new system has become my normal way of working. My manager recognises my progress, the old system has been decommissioned, and reverting is not an option." Reinforcement is achieved through recognition, rewards, accountability, and the removal of the old ways of working.

The ADKAR model is particularly powerful in banking because it allows change managers to diagnose where individuals are stuck. If analysts are aware of the change but do not want to participate, the problem is Desire — and the solution is engagement and motivation, not more training. If analysts want to change but cannot perform effectively, the problem is Ability — and the solution is coaching and practice, not more town halls.

Choosing the Right Framework

Each framework has strengths that make it more suitable for certain types of change:

Kotter's 8-Step Model is best for large-scale, leadership-driven transformation programmes — such as a bank-wide digital transformation, a major regulatory remediation, or a post-merger integration. It provides a comprehensive, sequential roadmap that is easy for senior leaders to understand and sponsor.

Lewin's 3-Stage Model is best as a conceptual lens — a simple way to ensure that every change initiative includes preparation (unfreeze), implementation (change), and stabilisation (refreeze). It is particularly useful for mid-level managers who need a straightforward framework they can apply without extensive training.

ADKAR is best for managing the people side of change at the individual level — understanding where each person or group is in their change journey, diagnosing barriers, and tailoring interventions. It is particularly powerful in banking operations where you need to track adoption across large populations of analysts or front-line staff.

In practice, experienced change managers in banking combine frameworks. They might use Kotter to structure the overall programme, Lewin to frame the narrative for leadership, and ADKAR to manage adoption at the team level. The frameworks are complementary, not competing.

Banking Example: Transforming AML Operations from Manual to AI-Assisted

A tier-1 European bank with over 40,000 employees decided to transform its Anti-Money Laundering (AML) transaction monitoring operations. The bank's existing process relied on approximately 300 analysts manually reviewing alerts generated by a rules-based system. The false positive rate exceeded 95%, meaning that for every 100 alerts, fewer than 5 required genuine investigation. Analysts spent the vast majority of their time dispositioning false positives — a repetitive, demoralising, and expensive process.

The bank's leadership decided to implement an AI-assisted triage system that would automatically disposition low-risk alerts, prioritise high-risk alerts, and provide analysts with enriched case data to accelerate their investigations. The expected outcome was a 60% reduction in manual alert volume, a 40% improvement in case turnaround time, and a reallocation of analyst capacity from routine disposition to complex financial crime investigation.

The transformation team used Kotter's 8-Step Model to structure their approach:

Urgency was established through a combination of regulatory pressure (the bank's supervisor had flagged concerns about the timeliness of suspicious activity reports) and internal data showing that the cost per alert was three times the industry benchmark. The Chief Compliance Officer personally communicated the urgency to all AML staff.

The guiding coalition included the Head of Financial Crime, the Chief Technology Officer, the Head of AML Operations, two respected senior analysts (selected as change champions), and a representative from the regulatory affairs team.

The vision was articulated as: "From alert factory to financial crime investigators — using AI to eliminate routine work and focus our expert analysts on the cases that truly matter." This vision reframed the change from "automation replacing people" to "technology empowering experts."

Communication was delivered through monthly town halls, weekly team briefings, a dedicated intranet page with FAQs, and — critically — one-to-one conversations between the change champions and every analyst in the team.

Empowerment involved addressing two major barriers: the legacy technology platform that could not integrate with the new AI engine (requiring a parallel technology migration), and a middle management layer that was resistant because the new model reduced the number of team leads required.

Short-term wins included a successful pilot in one transaction monitoring team that reduced false positive review time by 55% within eight weeks, and positive feedback from the regulator during an interim review.

Consolidation involved rolling the AI-assisted model out to all transaction monitoring teams over six months, using the pilot team's experience to refine the approach.

Anchoring was achieved by updating all job descriptions, training programmes, performance metrics, and standard operating procedures to reflect the new operating model. The old rules-based system was fully decommissioned, removing the option to revert.

The transformation took eighteen months from inception to full embedding. Alert volumes requiring manual review fell by 62%. Suspicious activity report quality improved measurably, as analysts were able to spend more time on genuine cases. The regulator acknowledged the improvement in their next supervisory letter. And crucially, only 8 of the 300 analysts left the organisation during the transition — the remainder were successfully reskilled into higher-value investigative and analytical roles.

This example illustrates why structured change management matters. The technology was important, but it was the deliberate, framework-driven approach to leading people through the change that determined whether the transformation succeeded or became another failed initiative.

In the next module, we will learn how to systematically assess the impact of a proposed change — understanding who is affected, how severely, and what support they will need.