Banks without a digital core will fail

Building on the discussion of data being key to disruption, I often use the phrase ‘digital core’ in this context.  Therefore, I was intrigued when someone asked for a definition of a ‘digital core’ and one of the replies was there isn’t a core anymore. 

I wondered what they meant and, in explanation, they referred to the idea of a central point of systems – a mainframe – is no longer the way the markets operate.  Systems should instead be spread across server farms in the cloud so there is no single point of failure.  I totally agree, and therefore felt it worth a little more explanation of digital core as so many misinterpret what this means.

First, I have defined my terms several times before:

But it does no harm to reiterate some points, such as this one.

So a digital core is, in essence, the removal of all bank data into a single structured system in the cloud.  The data is cleansed, integrated and provides a single, consistent view of the customer as a result. 

That’s a big ask, and most banks tell me it’s not achievable.  Silo structures and line of business empires protect data sharing and lock client information in their product focused empires; creating a single, cleansed store of cloud-based data is too insecure, creating the opportunity for any cyberattacker to bring down the bank; a single data store would not be good for risk management purposes; etc, etc.

I understand all these concerns, but don’t agree with them.

The product-focused empires are the problem.  You cannot have customer-centric operations if your organisation is product aligned.

Cyberattackers also find it far easier to steal from fragmented systems than one that can track digital entries in real-time across the enterprise.

Equally, banks are pretty darn poor at risk management in their fragmented, product-focused structures, as evidenced by two meetings with my bank recently.  The first meeting is with my business relationship manager, who tells me all the ins and outs of the banks’ SME operations.  I then, for the first time in living memory, allowed my new personal relationship manager to visit.  He had printed and read very carefully all my information and wanted to complete an up-to-date fact find for KYC and sales purposes.  That was fine.

Halfway through the conversation he asks: “what do you do for a living?”  I said that I thought he would know as I talk to my relationship manager often.  “Oh”, he says, “that doesn’t show on our records.  Who did you talk to?”  I explained that it was Paul, my SME manager, as I have my business account with the bank.  “Oh”, he says, “I didn’t know that”.

This is fairly typical of all banks I talk to – their corporate, commercial and retail bank systems are separated and never the twain meet – but it’s not the way a digital bank would work.

A digital bank with a digital core would immediately create the inter-relationship profiles of the digital footprints of all individuals who touch the bank.  That is the way you can drive contextual relationships and offers to those who touch the bank.  It is also the only way you can drive a consistent, augmented and informed approach to clients who touch the bank.

Equally, a digital bank has a single digital core of data in the cloud that can then be accessed by any form.  The digital core is independent of the processors, and hence you can take out a server or a system at any point and replace it with a new processor, because you have no reliance on the engines.  Your reliance is on the data being clean and consistent.

For me, it is a critical factor in developing the digital bank and yet whenever I get into a conversation about this with a bank, I’m told it’s too difficult.

It may be too difficult but I suspect that if banks don’t bite this bullet, the fintech specialists who do get the data structures right will eat their lunch,

Powered by WPeMatico