Déjà vu
Hey Bank, You launched that industry first AI powered decisioning suite. You launched your first AI-enabled digital branch. Your entire competition announced exactly the same. But to the customer it is déjà vu, playing on a loop, every few years.
We heard the same noise for anywhere banking, internet banking, for mobile banking, then for those dumb branch robots. You made it again for super apps. Meanwhile your IVR is still a fossil from 1998. Your account opening still can’t resolve a simple deviation. Your business analysis is still copy-paste, earlier from the web, now from an LLM. And yes, you still mis-sell those third-party products.
This noise works in a launch event, a board presentation, a press release, a LinkedIn post. It may even make the bank look progressive. What it does not do is answer the rather mundane question the customer is asking: Can I get my work done without fighting your process?
That is the whole and complete question. Not whether the bank has adopted a particular technology. Not whether the bank has kept up with the vocabulary of transformation, innovation, digital-first, AI-first, paperless, seamless, frictionless, or whatever the season demands.
The customer never experiences your technology. The customer experiences the effort it takes to get work done.
Fifty out of sixty-six
A few years ago, I was part of a diagnostic review of a bank’s technology strategy. The bank told us, with justified pride, that it had 66 initiatives running to modernise itself. On paper that is a bank in motion with a full transformation pipeline.
When we reviewed these initiatives, 50 of them sat in or around payments. All were useful. But all were incremental, necessitated by ecosystem and regulatory changes. These were being adopted by every bank. In essence it was a catch-up list. The bank was already late.
Then there was the usual experimental garnish too, a blockchain idea, a VR-led marketing concept, things that look well in a steering committee deck and have little contact with any customer’s actual problem. The catch-up game was being presented internally as cutting-edge transformation strategy. It was solving some problems of compliance and competitive pressure. It wasn’t focussed on solving customer experience.
The bank had an ambition to become digital. It did not have an ambition to become easier.
Reel bank, Real bank
Banks modernise the happy path, because the happy path is visible, measurable and campaign friendly. But happy paths come with ifs and buts.
Open an account in 30 minutes if every document is perfect. Make a remittance in seconds if all details are correct. Sanction a loan in an hour if the parameters match. Complete KYC if every database agrees. Issue a card at the airport if the bureau profile is unambiguous.
The real problem hides in these ifs.
Customers do not live inside standard journeys. People change addresses and mobile numbers. They change mandates, nominees and operating instructions. They move from minor to major. They add and remove joint holders. They deal with deceased accounts. They inherit relationships, restructure loans, dispute charges, and discover that their digital and AI powered bank is still in the previous decade. The real bank appears when the customer needs it to handle a change.
In our family we had to convert a minor account to a major account with one of the country’s largest banks. A child becomes an adult, the operating instructions change, documentation is refreshed. It is the most predictable event in a banking relationship, and the bank has known the date since the account was opened. Despite my years in banking, none of it helped. Form after form. Deviation after deviation. Document after document. Clarification after clarification. It took months. That bank had apps, campaigns, a modern branch and even a dedicated RM.
The digital, modern reel bank was on every screen. The old archaic real bank was in the paperwork.
Why banks do this anyway
It would be lazy to put this down to vanity or to assume that banks don’t work on improving processes. It would be presumptuous to say they don’t care about customers. They do, sometimes. The bigger point is that the setup incentivises them for something else.
A board can count initiatives, budgets, and go-live dates. It cannot easily count friction, because nobody instruments friction. A rating agency will ask about your capital adequacy, management and digital strategy. It will not ask how many times you asked a customer for a PAN card you already hold. An analyst call has a slot for the AI roadmap. It has no slot for mandate changes. So, a head of retail who announces that re-KYC now takes one interaction instead of three gets a smaller round of applause than one who announces an industry first AI-led 60 second approval, even though the first person has done more for the bank’s customers.
None of these parameters is irrelevant. They were simply never designed to detect whether a bank is easy to deal with.
The choice for noise is perfectly rational albeit absurd. It is the reason the gap between how a bank sounds and how it behaves keeps widening.
Measurement bias
Most banks measure themselves on turnaround time (TAT), cost to serve, and digital adoption. These are valid measures. The problem is that they are measured stage by stage, and the customer does not live in stages.
The loan was approved in a day. But disbursement then took four rounds of re-documentation. The approval TAT still looks excellent.
Account opening was instant and fully online. Adding a second signatory to the same account took five weeks. The onboarding metric remains perfect.
The card was issued remotely with no branch contact at all. Re-KYC on the same card required a branch visit. The acquisition journey scores 100% for digital end to end.
Speed matters and digitisation in each case helps. The bank was fast but in none of them was the bank timely. Speed is how quickly a narrowly defined internal milestone is completed. Timeliness is whether the customer got the outcome when they needed it. A bank optimised for speed can still be reliably late.
The deeper problem is where the measurement lives.
Acquisition is priority and instrumented to the field level. Every lead drop-off is tracked, attributed and reviewed. Servicing, on the other hand, doesnt get the required focus. A signatory addition has no funnel. A nominee change has no dashboard. A re-KYC that bounces between the branch and the back office has no owner and no clock. Ask most banks for the median elapsed time on their twenty most common service requests and the answer is likely to be hazy, because the data is either not collected or not properly collated.
First time right (FTR) is not new to banks. They talk about it. They dashboard it. And then the improvement strategy boils down to an employee training on getting the customer to sign at right places.
The actual reason sits upstream, in the process design and more tangibly in the product note. Most product notes are written as approval criteria. Who qualifies, at what score, at what price, against what security, up to what limit. Edge cases, servicing and deviations at best get a paragraph or two. Improvements are after-thoughts, reaction to customer escalations.
When things are even slightly off the template, the organisation struggles. The customer suffers. Without a pre-defined basis, the deviation approver asks for comfort in the form of another document. The RM goes back to the customer. This is the loop, and every dashboard blames it as ‘document awaited from customer’ and brushing the actual cause under the carpet.
What to measure
A happy path of approval conditions is not a process design. Until every deviation a product has been thought through and documented, no technology intervention will resolve the friction
So, the first step is to build right metrices, because in a bank nothing gets attention until it gets counted. These are the ones that may show the direction.
| Measure | What to count |
| Touches per completed request | Every interaction the customer had to initiate, from first ask to closure. |
| Elapsed time on the customer’s clock | Calendar days from first request to final outcome. Median and 90th percentile. |
| Repeat-document rate | How often the bank asks for a document it already holds. (you can expand this to data redundancy- same detail sought again and again) |
| Post-approval document additions | Documents asked for after the first decision, per case. |
| Deviation coverage | Share of deviations encountered outside the anticipated scenarios. |
| Reopen rate | Share of closed requests where the same issue comes back within a month. |
| Channel consistency | Whether branch, call centre, app and back office give the same answer to the same question. |
| Service catalogue coverage | Share of service journeys, as distinct from product journeys, redesigned in the last three years. |
Put these in front of a board once a quarter and the transformation priorities will rearrange themselves.
Hey bank, become easier
Use technology. Use it deeply, and use it wherever it removes repetition, shortens waiting, clarifies who is responsible and makes service more humane. Banking is dynamic and needs better systems, cleaner workflows, stronger data and sharper controls, and it needs them urgently.
So, when I say I do not care about your technology, I mean I should never have to notice it. Used well, it disappears into the solution. It shows up as a form that was not repeated, a document that was not asked for twice, a request that was not passed from one desk to another, and a deviation that was not treated as a system failure.
The claim worth making is not that you are digital or AI-led. It is that a service request now closes in one visit, and that when something changes in their life, you do not turn it into a project.
Hey bank, make banking easier.
