Priya Jaiswal, a renowned authority in global banking and financial market analysis, joins us to discuss the strategic maneuvers required when critical payment infrastructures undergo a change in command. With extensive experience in portfolio management and international business trends, she provides a deep dive into the complexities of leadership transitions within the UK’s largest financial institutions. Her insights offer a unique perspective on how legacy banking giants balance the weight of historical systems with the urgent need for modern, cloud-native innovation.
This conversation explores the vital components of a successful leadership handover, focusing on the continuity of large-scale migration projects and the technical evolution toward ISO 20022 standards. We examine the operational culture required to drastically reduce system failures and the risks associated with integrating low-code tools into national infrastructure. Finally, the discussion addresses the broader impact of executive turnover on a bank’s long-term technical roadmap.
When a leadership transition occurs in a department managing critical infrastructure like SWIFT and BACS, what are the immediate priorities for the incoming head? How can a successor ensure that multi-year migration projects maintain momentum without disrupting daily domestic and international payment schemes?
The immediate priority for any incoming leader, such as Trish Arksey, is to maintain the invisible but vital heartbeat of the bank’s daily operations across schemes like CHAPS and Faster Payments. When you are managing the movement of billions of pounds, the successor must first secure the trust of the “village” that builds and maintains these systems to ensure no loss of focus during the handoff. To keep the momentum of multi-year migrations, it is essential to lean on the established institutional knowledge—leveraging someone’s 15-year tenure, for instance—to bridge the gap between old legacy platforms and new goals. The transition feels less like a hard stop and more like a relay race where the baton is passed at full speed, ensuring that international connectivity via the CREST network or SEPA remains flawless. By validating the existing strategic roadmap early on, a new head can signal stability to both the internal engineering teams and the global financial markets.
Transitioning from legacy platforms to ISO 20022–compliant systems involves significant technical hurdles. What specific strategies should engineering teams use to manage these staged migrations, and how do event-streaming tools help bridge the gap between aging architectures and modern, cloud-native solutions?
Engineering teams must adopt a “decouple and conquer” strategy, where legacy systems are gradually isolated rather than replaced in one risky “big bang” event. ISO 20022 is not just a format change; it is a data-rich transformation that requires systems to handle much more complex information than the old standards allowed. Event-streaming tools act as a high-speed digital translator, allowing data to flow seamlessly between the rigid, aging mainframes and the flexible, modern cloud environments. This creates a hybrid state where the bank can test new ISO-compliant pathways in real-time without shutting down the traditional rails that customers rely on. This staged approach reduces the anxiety of the migration, allowing for a “fail-fast” environment where bugs are caught in the stream before they ever impact a final transaction.
Implementing a “run-first” operating model can lead to a dramatic reduction in system incidents. What are the practical steps required to embed this culture into a large-scale technology team, and how do you measure the trade-offs between rapid delivery and high-level operational stability?
Embedding a “run-first” culture requires a psychological shift where every developer feels personally responsible for the live environment’s health, rather than just throwing code over the wall to operations. Practically, this involves automating the “boring” parts of maintenance and monitoring so that the team can react to anomalies before they become full-blown outages. We saw the power of this at NatWest, where incident volumes reportedly fell by a staggering 80% within the first year of the model’s introduction. The trade-off between speed and stability is managed by setting strict “error budgets”—if the system is unstable, new features are paused until the foundation is reinforced. This ensures that while we are pushing for innovation, the reliability of the service remains the non-negotiable north star for the department.
Incorporating public cloud and low-code tools is becoming standard for supporting in-house engineering at major banks. What are the primary risks when integrating these tools into critical national infrastructures, and how do they change the way developers deliver services to a massive, multi-million-user customer base?
The primary risk is the “black box” effect, where the underlying complexity of a low-code tool or a public cloud provider might hide vulnerabilities that are hard for internal teams to patch during a crisis. When you are serving 20 million customers, even a minor glitch in a low-code interface can scale into a national headline within minutes. However, these tools also democratize development, allowing engineers to build and deploy customer-facing services at a velocity that was previously impossible. This changes the developer’s role from a “builder of bricks” to an “architect of systems,” focusing more on the user experience and less on the plumbing of the server room. The key is to wrap these modern tools in rigorous governance frameworks that ensure they meet the same ironclad security standards as the old-school infrastructure they support.
Large financial institutions often face periods where multiple high-level executives depart across various departments like data, digital, and retail. How do these shifts impact long-term technical roadmaps, and what organizational measures can ensure that institutional knowledge is preserved during such significant leadership changes?
When you lose key figures like a CEO of retail banking, a chief data officer, and a head of digital all within a year, there is a very real danger of “strategic drift” where the original vision for the bank’s future begins to blur. These shifts can stall long-term roadmaps because new leaders often want to bring in their own preferred technologies or methodologies, which can lead to expensive pivots. To prevent this, organizations must foster a culture of “unity and the village,” as Ian Povey described, ensuring that the strategy lives within the collective team rather than just in the head of one executive. Rigorous documentation and a strong middle-management layer act as the “memory” of the institution, keeping projects like the ISO 20022 migration on track despite the revolving door at the top. Succession planning should be a continuous process, not a reactive one, so that someone like Trish Arksey is ready to step in with a deep understanding of the existing roadmap from day one.
What is your forecast for payments technology?
The future of payments will be defined by the total disappearance of friction, where the technical complexity of moving money becomes completely invisible to the end user. I expect to see a rapid acceleration in the use of real-time data enabled by ISO 20022, which will allow banks to offer hyper-personalized financial services that can predict a customer’s needs before they even make a purchase. We will likely see the “run-first” model become the industry standard, pushing incident rates even lower and making the concept of “bank downtime” a thing of the past. As public cloud and event-streaming continue to mature, the barrier between domestic and international payments will dissolve, creating a unified global payment grid that operates with the speed and simplicity of a local text message. The ultimate goal is a 24/7/365 system that is as resilient as it is innovative, serving millions without a single point of failure.
