Competence Is a Control: Why Boards in Payments and Banking Technology Must Learn to Spot Leaders Who Hire for Loyalty

Introduction

Competence is not a soft attribute in financial infrastructure. It is a control, in the same sense that dual authorization, sanctions screening and reconciliation are controls. When a payments, core banking, or remittance function is led by someone who cannot do the work, the organization does not simply lose productivity. It loses the judgment that sits between a routine incident and a reportable one. And because that loss is invisible on a dashboard, boards routinely discover it only after a settlement failure, a regulatory finding, or a public outage has made it undeniable.

This article is about a specific and under-discussed failure pattern i.e, the leader who is out of their depth, appoints people chosen for allegiance rather than capability, and then manufactures a case against the competent professionals they inherited. It is a pattern that ends with capable engineers, risk specialists and operations leaders pushed out one at a time, replaced by people whose primary function is agreement. For a technology or manufacturing business, this is expensive. For a business that moves other people’s money across borders under licence, it is existential.

The pattern

It usually runs like this. A new head of payments technology, digital channels, or transaction banking operations arrives. Within weeks, a narrative forms, the inherited team is slow, resistant, legacy-minded, not commercial enough. The narrative is rarely tested, because it flatters everyone above. Boards like hearing that a problem has been identified and someone is gripping it. Next come the appointments. Two or three senior hires arrive from the leader’s previous employer, through processes that were compressed or waived. Their qualifications are asserted rather than demonstrated. They are placed above or alongside the existing subject-matter experts, and they carry the leader’s authority without the leader’s accountability.

Then the fault-finding begins in earnest. The professionals who built and ran the ISO 20022 migration, who understand why the correspondent nostro reconciliation behaves the way it does at month-end, who know which parts of the sanctions screening tuning are load-bearing, find themselves excluded from decisions and then blamed for the consequences of those decisions. Objectives shift mid-cycle. Credit for delivered work is re-assigned. Concerns are raised about them verbally, never in writing, until a performance process appears fully formed. Most of them do not wait to be pushed. They leave, quietly and professionally, to competitors and to fintechs who are delighted to have them. This is the detail that makes the pattern so hard for boards to see that the organization never has to fire anyone, so there is no incident, no dispute, no paper trail. There is only attrition, which the leader describes as renewal. Eighteen months later the function is fully staffed with loyalists, the reporting is more confident than it has ever been, and nobody left in the room can explain why the reconciliation breaks are ageing.

Why incompetence replicates rather than stays contained

The instinct is to treat this as one bad hire. It is not. Incompetence at the top of a function is self-propagating, for a reason that is structural rather than personal. A leader who cannot evaluate the work cannot safely hire people who can. A genuinely strong payments architect or financial crime lead will, in the ordinary course of doing their job, surface the gap. So the selection criterion quietly shifts from capability to safety. Each appointment lowers the ceiling of the function, and each new appointee applies the same logic one level down.

In parallel, the leader’s only defensible position becomes the claim that the problem was inherited. That claim has a shelf life, and it must be continuously refreshed with new evidence of the old team’s failings. Blame stops being a reaction to events and becomes a management method. This is why the fault-finding does not stop once the original targets have gone. It moves on to whoever is next closest to the actual work. The organizational result is a function that has converted from a policy-driven, accountable operation into something closer to a personal court, where the operative question is what the leader wants rather than what the framework requires. In a licensed payments institution, that conversion is a governance breach whether or not anyone has yet noticed.

Why this is more dangerous in payments than almost anywhere else

Every industry suffers from this. Financial infrastructure suffers differently, for four reasons. They are:

1. The knowledge is tacit and thinly held. Documentation describes the happy path. The exceptions, the manual workarounds, the reasons a particular cut-off exists, the history of why a scheme rule is implemented the way it is, all of this lives in a small number of heads. Lose four such people in a year and you have not lost four headcount. You have lost the ability to safely change the system.
2. Failures are non-linear and deadline-bound. A weakened marketing team produces worse campaigns. A weakened payments engineering team produces a missed scheme mandate, a failed migration cut-over, or a settlement window that does not close. There is no gradual version of a payment that does not arrive.
3. The regulator holds named individuals accountable. SE Asia’s individual accountability and conduct expectations, the UK’s Senior Managers and Certification Regime, Hong Kong’s Manager-in-Charge arrangements and Australia’s financial accountability regime all rest on the same premise, that specified individuals are fit, proper and genuinely capable of discharging their responsibilities. A board that has installed and retained a leader who is demonstrably not capable is not merely making a talent mistake. It is exposed on fitness and propriety, on governance, and on the adequacy of its own oversight.
4. Correspondent and scheme relationships price your competence. Counter-parties, sponsor banks and scheme operators form a view of whether your organization is well run. That view is formed by the people who deal with you day to day, and it moves faster than any formal assessment. When your best people leave, your counter-parties know before your board does.

Why the boardroom is the last place to find out

Boards are structurally disadvantaged here, and it is worth being honest about why. Almost all information about a function reaches the board through the person running it. When that person is the source of the damage, the board is reading a report written by the subject of the report. Restructuring looks like reform. Attrition looks like renewal. Confident narrative looks like control. Absence of complaints looks like stability, when it often just means that people have concluded that complaining is unsafe and have decided to leave instead.

There is also a genuine complication that any serious framework has to handle. Sometimes an inherited team really is underperforming. Sometimes a new leader really is doing necessary, unpopular work, and the departures really are the right departures. Boards know this, and the knowledge paralyses them. Fear of undermining a leader they appointed six months ago prevents them from asking the questions that would distinguish the two cases. The distinction is knowable. It just requires the board to look at different evidence.

A detection framework for CXOs

The aim is not to adjudicate personnel disputes. It is to identify observable, verifiable signals that separate a leader fixing a function from a leader dismantling one. The following framework will work as guide to CXOs and Board members.

1. Attrition forensics, not attrition rates.
   • The headline rate tells you nothing. What matters is who left. Pull, for the last 24 months tenure, last two performance ratings before departure, criticality of the role, and destination. A genuine turnaround sheds weak performers and short-tenured hires. A purge sheds long-tenured, previously well-rated specialists into good roles at peers and competitors. That second pattern is a finding, and it should be presented to the board as one, not buried in an HR appendix.
2. Where did the new leadership come from?
   • Count the senior appointments made since the leader arrived that originate from their previous employer. Then examine the process for each and ask was there a competitive slate, an independent panel member, an objective assessment? Provenance plus process irregularity is a far stronger signal than either alone.
3. The policy-versus-preference test.
   • Take five recent material decisions in the function like a vendor selection, a risk acceptance, a control exception, an architecture choice, a rate or limit change. For each, ask whether the decision is traceable to documented policy and delegated authority, or whether it rests on the leader’s personal direction. Functions being run for loyalty show a rising proportion of the latter, and a rising number of exceptions granted informally.
4. The direction of blame across board cycles.
   • Read the last three or four reports from the function side by side. Leaders who are delivering absorb blame and distribute credit. Leaders who are struggling reverse that flow. When every miss is attributable to a predecessor, another function, a vendor, or a named individual who has since departed, and every success is attributable to the current leadership, the pattern is the message.
5. Substance density in reporting.
   • Track whether reporting is becoming more narrative and less measured. Specifically watch for the disappearance of uncomfortable metrics like ageing reconciliation breaks, repeat incidents, change failure rate, overdue audit findings, control testing exceptions, mean time to restore. Metrics that vanish are rarely improving.
6. Independent channels that do not route through the leader.
   • Skip-level sessions run by a non-executive director. Exit interviews for senior technical leavers conducted by someone outside the function, with results reported to the board unfiltered. Structured, periodic input from second and third line like internal audit, operational risk, compliance, and information security. These functions often see the deterioration first and lack a route to say so.
7. The counter-party read.
   • Ask correspondent banks, scheme operators, major clients and key vendors, in the ordinary course of relationship reviews, how they find working with the function now compared with two years ago. External parties will say things internally that no employee will put in writing.

Intervening without theatrics

When the signals converge, the response should be proportionate, evidence-led and quick. Commission an independent review with a defined scope and a hard deadline, ideally through the audit or risk committee rather than through management. Scope it to the function’s health, its control environment and its people decisions, not to the leader personally. That framing gets better evidence and is fairer to a leader who may be innocent of the charge. Protect the people who give evidence, and be seen to protect them. If the first person who speaks candidly suffers for it, the review is over regardless of how long it formally runs.

Examine the appointment processes rather than putting individual appointees on trial. Process defects are documentable, comparable and hard to argue with. They also tell you whether the problem is one leader or a wider control weakness in how the organization hires at senior levels. Then decide, within the window. Boards frequently know within a quarter and act after four. The delay is usually loyalty of a different kind i.e reluctance to concede that the board’s own appointment was wrong. That is the same substitution of loyalty for judgment happening one level higher, and it costs more than the original mistake.

Finally, treat capability loss as a risk with an owner and a remediation plan. Named single points of knowledge, documented recovery of undocumented process, targeted rehiring of specific expertise. Back-filling headcount is not the same as restoring capability, and boards should refuse to accept the former as evidence of the latter.

What is actually at stake

An organization that has traded competence for loyalty keeps functioning cosmetically for a surprisingly long time. Payments clear, Reports arrive, and Meetings happen. The deterioration is entirely in the margin for error, and the margin for error is invisible until it is exhausted.Then a scheme mandate lands, or a migration cut-over goes badly, or a fraud pattern shifts, or a regulator asks a question that requires someone in the room to genuinely understand the answer. At that moment the organization discovers what it sold. The people who could have handled it are now doing the same job for a competitor, and they will not be coming back.

Credibility in this industry erodes quietly and returns slowly. Licenses, correspondent relationships, scheme memberships and client trust are all built on an assessment of whether the organization is competently run. Sustainability is not about retaining people for its own sake. It is about retaining the capability that those people carry, and recognizing that the fastest way to destroy it is to put someone in charge who benefits from its absence.

Boards have one durable defense against this. Insist on evidence that does not originate from the person being evaluated. A board that only measures what a leader reports will only ever learn what that leader wants known.