Financial Services

Forty years in banking technology taught me that intelligence is only as good as the data it can trust.

Over the past year, I have met with financial institutions across multiple markets, and one conversation keeps returning. It is no longer primarily about AI budgets or which model to deploy. It is about the data underneath all of it.

The question in many boardrooms has shifted from, “How do we deploy AI?” to something more fundamental: “How do we redesign our enterprise data architecture so AI and autonomous agents can operate with trust, speed, and scale?”

That may sound like an incremental change. I do not believe it is.

In forty years of banking technology, it is one of the most consequential shifts I have seen. We are moving from systems that help people understand what is happening to systems that can interpret context, support decisions, and increasingly take action.

That changes the role of data architecture. It is no longer simply the foundation for reporting and analytics. It becomes part of the institution’s decision and execution infrastructure.

How We Got Here

I have watched this industry reinvent itself four times. Mobile-First brought banking to our fingertips. Digital-First reimagined customer journeys and operating models. AI-First enabled intelligence through personalization, automation, and predictive decision-making. Each wave solved a specific business problem and created significant value.

Now we are entering the era of Agentic Banking, where autonomous AI agents can reason, collaborate, make decisions, and carry out complex workflows across the banking value chain.  We are moving from systems that produce insights to systems that can act. If you are leading a bank amid this transition, that distinction changes everything about how you build.

The Problem Nobody Solved Along the Way

Here is what I have seen across almost every institution I have worked with. The pace of innovation has consistently outstripped the evolution of the underlying enterprise data architecture.

Data Warehouses gave way to Data Lakes, then Middleware, APIs, RPA, Hyperautomation, AI, and now Agentic AI. Each wave added capability. Yet, in many institutions, the underlying foundation did not evolve at the same pace.

 Many institutions today find themselves with segmented data estates, duplicated customer information, inconsistent governance, and AI models that cannot consistently access trusted, real-time enterprise data. You can build the most sophisticated agent in the world. If it cannot access a trusted and current view of the customer, it may make confident decisions based on incomplete information.  In high-stakes banking workflows, that can be more dangerous than keeping the decision under human control.

This is driving significant investment in cloud-native data platforms, real-time event-driven architectures, enterprise data products and data mesh principles, API-first integration, strong data governance and lineage, and unified customer and enterprise data models. In my view, this is becoming the most important technology investment of the decade.

From Systems of Record to Systems of Engagement

Another major shift is taking place in customer relationship management.

For nearly three decades, CRM platforms have served as the primary interface for sales, service, and customer management. In the Agentic AI era, that role is beginning to evolve. CRM is increasingly evolving into the system of record, while intelligent agents begin to take on a larger role as the system of engagement.

Instead of relationship managers manually identifying cross-sell opportunities, next-best actions, portfolio gaps, or customer service interventions, AI agents can continuously analyse customer behaviour, life events, risk, profitability, and intent, then recommend or orchestrate personalised actions in real time.

Customer Value Management is undergoing a similar transition. It is moving away from periodic, campaign-based analytics toward continuous optimisation, where intelligent agents can help balance customer experience, revenue growth, risk, pricing, and profitability.

But this shift depends on the quality of the underlying data. An agent cannot create a coherent customer experience if customer information is fragmented, definitions are inconsistent, or important signals are delayed. It also raises the bar for governance. Institutions will need clear accountability, decision boundaries, explainability, and appropriate human oversight as agents take on more consequential customer interactions.

The institutions that lead in the Agentic era will not necessarily be those with the largest AI budgets. They will be those that have built a trusted, cloud-native enterprise data foundation capable of supporting intelligent agents across the organisation.

In this environment, data architecture is no longer back-office infrastructure. It is becoming part of the enterprise’s decision and execution system.

The next competitive advantage will not come from AI alone. It will come from AI built on data that is trusted, connected, current, and governed.

Why HR technology works only when HR leads as process owner - a CHRO’s perspective

Until recently, HR technology decisions were uncomplicated. The focus was on payroll accuracy, compliance, efficient hiring processes, and keeping employee records up to date. But as businesses grew and expectations shifted, that world changed.

In every growing organization I’ve worked with, HR systems sit at the center of cost control, governance, employee experience, and growth capacity. Workforce data feeds audits, regulatory submissions, productivity reviews, and leadership dashboards. HR metrics are reviewed by CEOs, CFOs, other CXOs, and boards. This increased scrutiny has pushed HR into a far more strategic role, and I’ve witnessed how fundamentally this changes the HR function.

This shift changed how I think about HR technology. As HR became more central and visible, the question was no longer which system had more features or a better interface, but whether the system fit my organization’s current and future needs. The platform had to support essential customizations aligned to our processes and policies.

I encountered this shift firsthand while leading an HRMS transition in a fast scaling financial institution. In that context, cost discipline, compliance, and effective operations were all equally non-negotiable.

Where HR Technology Helps And Where It Quietly Gets In The Way

Most HR platforms I’ve used perform as designed: they standardize processes, introduce controls, and bring structure. However, issues often arise when technology dictates behavior instead of supporting it. In these situations, there is pressure to reshape processes to fit the system’s design, rather than configuring systems to reflect what actually works for the organization.

A common issue I’ve encountered is over-standardization. Many HRMS platforms are built for global use, which is both a strength and a limitation. Standard processes may work in theory, but I’ve seen them clash with the realities of organizations operating under specific governing regulations or customized policy guidelines. When systems don’t reflect how work actually happens, HR teams, mine included, end up managing exceptions manually. The system becomes an extra effort rather than a source of efficiency.

Cost is another gap. HRMS costs increase with headcount, and sometimes faster than the business. For organizations in margin-sensitive environments, this is hard to justify. The system may be stable, but the economics no longer make sense.

Customization is often treated as a technical decision left to vendors or IT teams. I’ve seen the result: a system that looks fine on paper but feels awkward in daily use. When I don’t own process design, customization remains superficial and fails to solve my team’s real problems.

Treating HR Technology As A Process Decision First

During the transitions I have led, the issue I observed was not focused on replacing one platform with another. The real gap was the absence of clear process ownership before technology decisions. At the same time, the most important choice was not which system to use, but how to approach the transformation. Process redesign needs to take the lead, with technology playing a supporting role.

With this principle in mind, the first step was to take an honest look at our HR processes. We mapped the employee lifecycle in depth - recruitment, onboarding, performance management, compensation, and exits. This brought to light inefficiencies, manual workarounds, and policy inconsistencies that had evolved into normal over time. After dealing with these, configuring the system was far simpler and more effective.

The second learning was about customization. Customization is often seen as risky, but poorly planned standardization is riskier. When grounded in approved policies and management structures, customization strengthens control. The key is discipline. Every customization must have a clear business rationale and strong HR ownership.

The third learning was about cost. The transition reduced HRMS costs, not just through negotiation. Savings came from eliminating parallel systems, cutting down manual work, and designing workflows that minimized exceptions. Lower cost of ownership was a by-product of better design, not the starting objective.

Why This Matters Beyond One Organization

These problems are not unique to one organization. Similar patterns appear across emerging economies where companies scale rapidly under regulatory and cost pressures. The most successful HR technology transformations share a common factor. HR leaders act as process architects, not system administrators. They define how work ought to flow, how decisions should be governed, and how exceptions should be handled before asking technology to support those choices.

Clarity Comes Before Code

Most HR technology transformations do not fail because of inadequate software. They fail because organizations expect technology to compensate for unclear processes and weak ownership. When HR owns the “why” and the “how,” technology becomes an enabler rather than a constraint. This makes system choice simpler and implementation smoother. The real transformation begins when HR leads with clarity, not code. Make process ownership your starting point, and technology will follow.