Stakeholder Analysis & Engagement

Why Stakeholder Engagement Determines Success

The success or failure of a change initiative in banking is rarely determined by the quality of the technical solution. It is determined by whether the people who must adopt, support, enable, or approve the change are sufficiently engaged, informed, and committed. These people are your stakeholders — and every one of them has the power to accelerate or obstruct your initiative, depending on how effectively you engage them.

In banking, stakeholder landscapes are particularly complex. A single transformation programme might involve executive sponsors who control budgets, operational managers who control delivery, front-line staff who must adopt new ways of working, compliance officers who must approve regulatory implications, technology teams who must build and integrate systems, internal audit who must review the change governance, external regulators who must be kept informed, and — in some cases — correspondent banks, market infrastructure providers, or industry bodies who are also affected.

Failing to identify a critical stakeholder, misjudging their level of influence, or engaging them too late are among the most common causes of change failure in banking. A compliance officer who was not consulted early enough may raise a regulatory concern that forces a redesign at the eleventh hour. A middle manager who feels excluded from the decision-making process may quietly undermine adoption within their team. A regulator who learns about a significant change from a third party rather than directly from the bank will have legitimate questions about the institution's governance and transparency.

Structured stakeholder analysis and engagement is therefore not a "nice to have" — it is a critical discipline that must begin at the start of the programme and continue throughout its lifecycle.

Stakeholder Identification and Mapping

The first step is to identify every individual and group who has a stake in the change. In banking, stakeholders typically fall into several categories:

Executive sponsors and steering committee members. These are the senior leaders who authorised the change, provide budget and resources, and are accountable for its success. They include the business sponsor (typically a COO, Head of Operations, or equivalent), the technology sponsor (CTO or CIO), and in regulated change programmes, the compliance sponsor (Chief Compliance Officer or Head of Regulatory Affairs). Understanding their individual motivations, concerns, and expectations is essential.

Programme and project teams. The people delivering the change — project managers, business analysts, technology developers, testers, and change managers. While they are driving the initiative, they are also stakeholders who need to be aligned on objectives, scope, and approach.

Middle managers and team leads. Perhaps the most critical and most overlooked stakeholder group in banking transformation. Middle managers are the bridge between the programme and the front line. They will be asked to implement the change within their teams, manage disruption to daily operations, support their staff through the transition, and continue to hit operational KPIs while simultaneously managing change. They are also the group most likely to feel threatened by change, particularly if it restructures teams, reduces management layers, or automates functions they currently oversee.

Front-line operations staff. The people who will ultimately use the new system, follow the new process, or work in the new way. Their adoption determines whether the change delivers its intended benefits. They are typically the largest stakeholder group and the one most directly affected by the change.

Compliance and risk functions. In banking, the compliance and risk functions are not just stakeholders — they are gatekeepers. Their approval is often required before a change can proceed, and their ongoing oversight continues after implementation. Early engagement with compliance is essential to identify regulatory implications, notification requirements, and any constraints on the pace or nature of the change.

Internal audit. While internal audit typically operates independently, they will review the change management process and its governance. Understanding their expectations and ensuring that the programme's documentation, approvals, and testing meet audit standards is important.

External regulators. For significant changes affecting critical business services, regulatory reporting, or customer outcomes, the bank's prudential regulator (ECB, PRA) and conduct regulator (FCA, BaFin) may need to be informed or consulted. Proactive engagement builds trust; surprises erode it.

External partners. In banking, changes often affect external parties — correspondent banks, clearing houses, market infrastructure providers, technology vendors, and outsourcing partners. These stakeholders must be identified and engaged, particularly where the change affects shared processes or interfaces.

Customers. While often downstream from operational change, customers are stakeholders when the change affects their experience — for example, changes to online banking interfaces, branch operations, or the speed and accuracy of transaction processing.

The Power/Interest Grid

The power/interest grid (also known as the Mendelow matrix) is the most widely used tool for prioritising stakeholder engagement. It classifies stakeholders along two dimensions:

• Power — the stakeholder's ability to influence the change (through authority, budget control, decision-making rights, or informal influence)
• Interest — the degree to which the stakeholder is affected by or cares about the change

This creates four quadrants:

High Power, High Interest — Manage Closely. These are your most critical stakeholders. They have the authority to support or block the change, and they care deeply about it. Typical examples in banking: the business sponsor, the Head of Operations for the affected area, the Chief Compliance Officer (for regulatory change). These stakeholders need regular one-to-one engagement, involvement in key decisions, and proactive management of their expectations.

High Power, Low Interest — Keep Satisfied. These stakeholders have significant authority but are not directly affected by or focused on this particular change. Typical example: a board member who approves the programme budget but is not involved in day-to-day decisions. They need periodic updates that are concise, well-structured, and focused on outcomes rather than details.

Low Power, High Interest — Keep Informed. These stakeholders are directly affected by the change but have limited authority to influence its direction. Typical examples: front-line operations staff, junior analysts. They need regular, honest communication about what is changing, when, and how it affects them — and crucially, a channel to provide feedback and raise concerns.

Low Power, Low Interest — Monitor. These stakeholders are neither significantly affected nor influential. They require minimal engagement but should be monitored in case their position changes. An example might be a support function in a different geography that is not part of the initial rollout but may be brought into scope later.

The power/interest grid is a living document. Stakeholder positions shift during the lifecycle of a programme. A middle manager who starts as Low Interest may move to High Interest when they realise the change affects their team. A regulator who was initially Low Interest may shift to High Power, High Interest if they receive a complaint or if the change affects a regulated activity they are currently reviewing.

RACI for Change

The RACI matrix provides clarity on roles and responsibilities during the change. For each key change management activity — such as approving the go-live decision, delivering training, communicating to staff, managing resistance — RACI defines who is:

• Responsible — performs the work
• Accountable — owns the decision and outcome (only one person per activity)
• Consulted — provides input before the decision is made
• Informed — notified after the decision is made

In banking change programmes, RACI is particularly important because multiple functions (operations, technology, compliance, risk) all have legitimate interests in the same decisions. Without clear RACI, decision-making becomes confused, duplicated, or — worse — nobody makes the decision at all.

A common banking example: Who is Accountable for the go/no-go decision on a new transaction monitoring system? Is it the Head of AML Operations (business owner), the CTO (technology owner), the Chief Compliance Officer (regulatory owner), or the programme director (delivery owner)? Without a clear RACI, the go-live decision becomes a drawn-out negotiation that delays implementation.

Best practice is to define RACI early in the programme and review it at each programme phase gate. In banking, RACI should explicitly include the compliance function — their role is typically "Consulted" on most change activities and "Accountable" for confirming regulatory compliance of the change.

Building a Coalition of Sponsors and Champions

Effective change in banking requires a multi-level sponsorship structure:

The executive sponsor provides strategic direction, authorises resources, removes escalated barriers, and visibly endorses the change. In banking, the executive sponsor for an operational transformation should be the senior operational leader — the COO, Head of Operations, or Head of the affected business line. Technology-led sponsorship alone is insufficient because the change is fundamentally about how people work, not about the technology they use.

Senior sponsors within each affected function provide sponsorship within their own areas. For a cross-functional change, you might have senior sponsors in operations, compliance, technology, and finance — each responsible for driving the change within their function. These sponsors must be aligned with the executive sponsor's vision and actively engaged, not just named in a governance document.

Change champions are respected individuals within affected teams who volunteer or are selected to advocate for the change at the grassroots level. Champions are not project team members — they are credible peers who understand the daily reality of the front line. Their role is to translate programme messages into the language of their team, provide early warning of resistance or confusion, support colleagues who are struggling, and feed back honest, unfiltered information about how the change is landing.

In banking operations, effective change champions are typically experienced analysts or senior processors who are well-respected by their peers, open to the change, and willing to invest time in supporting their colleagues. They should be formally recognised, given dedicated time for their champion role (not asked to do it entirely on top of their day job), and provided with regular briefings, talking points, and a direct line to the programme team.

A good ratio is one champion for every 15-25 affected staff members. For a transformation affecting 200 analysts, you would aim for 8-12 champions distributed across locations and teams.

Engagement Strategies by Stakeholder Type

Different stakeholders require fundamentally different engagement approaches:

Executive sponsors need strategic-level engagement: clear programme objectives, milestone progress, risk and issue updates, and decision requests. They do not need (or want) operational detail. Engage them through structured steering committee meetings, concise written updates, and periodic one-to-one sessions. Always be transparent about challenges — executives lose trust far more quickly when they discover problems were hidden than when problems are raised early.

Middle managers need operational engagement: detailed information about what is changing in their area, what they are expected to do, and what support is available. Crucially, they need to be engaged before their teams — nothing undermines a manager's credibility faster than learning about changes that affect their team from a town hall they attended alongside their direct reports. Engage middle managers through dedicated briefings, workshops, and coaching sessions.

Front-line staff need practical engagement: clear, honest communication about what is changing, how it affects their daily work, what training and support they will receive, and where to go with questions and concerns. Engage them through team briefings, Q&A sessions, training workshops, and feedback channels. The tone should be empathetic and human, not corporate and abstract.

Compliance and risk functions need structured, evidence-based engagement: formal impact assessments, regulatory analysis, control mapping, and documented approvals. Engage them through formal submission processes, review meetings, and documented sign-offs. Include them early — compliance colleagues who are brought in at the end to "rubber stamp" a decision will rightly resist.

Regulators need proactive, transparent engagement: early notification of significant changes, clear articulation of risk management approaches, and evidence that the bank has assessed and mitigated the impacts. The style of engagement depends on the regulatory relationship — some supervisors prefer formal written notifications; others prefer informal early discussions. The bank's regulatory affairs team should guide the approach.

Managing Senior Leadership Expectations

Senior leaders in banking are accustomed to managing large, complex programmes. They expect structured reporting, clear metrics, and honest assessments of progress and risk. Managing their expectations effectively involves several principles:

Set realistic expectations from the start. Change adoption follows an S-curve — there is typically a productivity dip during transition before performance improves. If you promise that the new system will be delivering full benefits from day one, you will lose credibility when the inevitable dip occurs. Set expectations that include the transition period, the learning curve, and the time to full proficiency.

Report on leading indicators, not just lagging ones. Lagging indicators (such as processing volumes or error rates) take months to reflect the impact of change. Leading indicators — training completion rates, system login frequency, user satisfaction scores, resistance indicators — provide earlier signals of how adoption is progressing.

Be transparent about risks and challenges. Senior leaders in banking deal with risk every day — they understand it. What they do not accept is being surprised. If a risk is emerging — low training attendance, rising resistance in a particular team, a technology integration issue — report it early, with a clear mitigation plan.

Connect change outcomes to business metrics they care about. For a COO, connect change adoption to operational efficiency, cost reduction, and risk mitigation. For a CCO, connect it to regulatory compliance and supervisory relationships. Frame your progress updates in the language of their priorities.

Banking Example: Stakeholder Engagement for a Cross-Border Payments Platform Migration

A large international bank decided to migrate its cross-border payments processing from a legacy platform to a modern, real-time payments infrastructure. The migration affected every cross-border payment the bank processed — approximately 150,000 transactions per day across 40 currency corridors. The stakeholder landscape was exceptionally complex.

Executive stakeholders included the Global Head of Payments (executive sponsor), the CTO (technology sponsor), the Chief Compliance Officer (regulatory sponsor), and the CFO (who was funding the programme from the technology investment budget). Each had different priorities: the Head of Payments wanted faster processing and lower unit costs; the CTO wanted architectural modernisation; the CCO wanted continued sanctions screening compliance; the CFO wanted the programme delivered within budget.

Front office stakeholders included FX traders and sales teams who were affected because the new platform changed the cut-off times for same-day value payments in certain corridors. This was a commercial issue — later cut-off times were a competitive advantage, but the migration temporarily disrupted established patterns. Engagement strategy: dedicated briefings for each trading desk, led by the Head of Payments personally, with clear timelines for each corridor migration.

Operations stakeholders included 80 payments processing staff across London, New York, and Singapore who would need to learn the new platform, follow new exception handling workflows, and adapt to real-time processing (replacing the batch-based model they had used for a decade). Engagement strategy: dedicated change champions in each location, weekly team briefings, a pilot group of 12 experienced processors who tested the new platform and provided feedback before the wider rollout.

Compliance stakeholders required detailed impact assessments for sanctions screening (ensuring that the new platform's screening integration maintained equivalent or better coverage), regulatory reporting (confirming that payment reporting to central banks would not be disrupted), and customer notifications (ensuring that SWIFT MT messages remained compliant with format requirements). Engagement strategy: formal compliance review at each programme phase gate, a dedicated compliance analyst embedded in the programme team, and monthly compliance steering updates.

Correspondent banks — the bank processed cross-border payments through a network of 200+ correspondent banking relationships. Each correspondent needed to be notified of changes to message formats, settlement instructions, and cut-off times. Engagement strategy: a formal notification programme managed by the correspondent banking team, with 90-day advance notice, bilateral testing, and a dedicated helpdesk for correspondent bank queries during the migration.

Regulators — the bank proactively notified its prudential regulator (ECB) and national regulators in the UK (PRA/FCA), US (OCC/Fed), and Singapore (MAS) about the payments platform migration. The notification included the migration timeline, the risk management approach (including rollback procedures), and the impact on regulatory reporting. Engagement strategy: the bank's regulatory affairs team managed all regulatory communications, providing formal written updates at three key milestones (programme initiation, UAT completion, and post-go-live confirmation).

The programme used a tiered engagement model:

• Tier 1 (Manage Closely): Executive sponsors, Head of Payments Operations, CCO, correspondent banks with the highest payment volumes (top 20)
• Tier 2 (Keep Satisfied): CFO, Board Risk Committee, regulators
• Tier 3 (Keep Informed): All operations staff, FX trading desks, remaining correspondent banks
• Tier 4 (Monitor): Internal audit, other operations teams not directly affected

Each tier had a defined communication cadence, channel, message owner, and escalation path. The engagement plan was reviewed fortnightly by the programme's change management workstream and updated as stakeholder positions evolved.

The migration was completed over eight months, with each currency corridor migrated sequentially. Zero correspondent banking relationships were lost during the transition. Regulatory engagement resulted in no supervisory findings. Operations staff achieved full proficiency on the new platform within six weeks of their corridor's migration — two weeks faster than planned, attributed in part to the effectiveness of the change champion network and the early engagement of the pilot group.

In the next module, we will explore how to build a communication strategy that keeps all these stakeholders informed, engaged, and aligned throughout the change journey.