Just about everyone can agree that digital transformation is a strategic imperative to remain relevant. But the right path to get there is a subject of much debate. Should you go all in and create a separate digital entity? Or should you slap on a digital front-end that preserves a backend legacy infrastructure? Or should you find a way to develop in two speeds - taking care of improving customer experience while in parallel modernize your backends? What’s the right path to digital transformation? It really depends on the depth of the company's pockets and their appetite for risk. We can outline three different options:
Front-end Only: Rolling out CX improvements and cosmetic fixes without retooling any of the tech infrastructure.
Going Digitally Native: A fully digital customer interface supported by a fully digital and modernized backend.
Wrap and Digitize: Setting up a digital business platform first to decouple the front-end and backend, then gradually launch CX / UX improvements, while upgrading backend components and build on them as the company develops.
Before picking one of these three directions companies must first determine how digital fits into their overall strategy, before embarking on a me-too project that could be the wrong approach… and costs millions. While it’s important to keep up with competitors, you must tailor your digital transformation journey to your strategy and your needs. You can’t just follow in the footsteps of another institution. Senior leaders should ask the following three questions to figure out which approach is the right one for their institution:
What do we want to be known for?
Which consumer segments are we targeting?
What are our core capabilities and points of differentiation, and how will a digital strategy strengthen them?
According to industry research within the finance industry, all of the top 30 financial institutions and most second and third tier banking providers, have already initiated a digital transformation project of some kind, but these efforts are often ad hoc and fail to yield the expected improvement in profitability. A host of challenges create significant headwinds for any company considering an undertaking of this magnitude — a legacy infrastructure hobbled by an aged core platform, an internal culture resistant to change, and an inherent aversion to risk.
That means for most companies, digital transformation will be a lengthy, iterative process, and very few will become digitally native any time soon. Let’s zoom-in on the three different options for digital transformation.
Front-end only, take the path of least resistance A front-end only digital strategy in which you focus your energy on CX and consumer-facing systems, while ignoring the backend and legacy problems will deliver you speed and focus at the start of your digital transformation. It is a cosmetic strategy that only addresses superficial elements of the experience. Specifically, you make the mobile app and online banking interface as intuitive and attractive as possible, but don’t invest in any substantive changes to the underlying legacy systems yet. While this is definitely the quickest and least expensive way to get a digital look and feel for your institution, it’s only a temporary fix — a digital “veneer” overlaid on a dated infrastructure that will still need gutting somewhere down the road. Behind the scenes, the institution remains limited in what it can deliver. Without integration of back-end systems and no fundamental change to the operating model, the experience will be not be significantly different to what customers had before. In other words, the front-end promises what the backend will struggle to deliver. This approach is really just a stop-gap strategy. Nevertheless, the front-end experience has the biggest impact on consumers and how they perceive the company's brand, so it makes sense to get busy pouring dollars into an improved CX. For some — those that either don’t have the stomach or the budget for full digital transformation at this time — it may be the best alternative. They can at least remain competitive by appearing to be digital. However, without integration between the front-ends and backends, you probably won’t realize the cost and efficiency savings that ultimately make a digital-first strategy so attractive. If you’re not careful, all you may accomplish is adding costs to maintain a new front-end — trapped in a quasi-digital environment where you’re constantly struggling to retrofit workflows and adapt processes in ways for which they were never originally designed.
Bottom Line: A front-end approach may seem penny-wise but pound-foolish, yet it still may be the right strategy. Going digitally native: reinvent from the ground up Some companies choose to go all in. With this strategy, the management team typically starts over by defining a “minimally viable company,” one that will offer just a handful of products. A basic retail bank, for example, might focus on deposits, payments, or loans. Many financial institutions pursuing this approach have decided to create an entirely new digital arm — a separate arm with its own consumer-facing brand that may eventually overtake the legacy brand. Reducing costs is a big reason that in the finance industry, banks and credit unions should consider going digitally native. Branch transactions cost roughly $4 each, while online and mobile transactions cost $0.09 and $0.19, respectively. But the main reason to go digital native is that it makes organizations much more agile. When you’re digitally native, you don’t have to spend months or years on IT initiatives, only to find out that consumer preferences have changed in the meantime. It lets them adapt to rapidly changing customer tastes, and it lets them test and iterate rather than commit and hope. The digital core and open architecture also allow flexible approaches for partnering with third parties to offer a range of products and services. It’s now possible to set up a fully functional, digital native platform using third-party architectures. If this is so attractive, why don’t we see more of it? Usually it comes down to perceptions of expense. Another example from the financial industry: many financial institutions think it’s costly and time consuming to launch a fully digital bank, though this doesn’t have to be the case. Using cloud technology, it’s now possible to launch a digital native bank in months and at far less expense than ever before.
But going fully digital means replacing the legacy core systems, which can cause a raft of cultural and HR challenges — e.g., getting employees comfortable with a more modern customer experience. The ability to go to market faster with new products can also result in cultural dissonance; many companies simply aren’t accustomed to doing anything on the fast track. The siloed departmental organizational structure served by centralized IT is another detriment. To take advantage of the nimbleness of digital, a modern company need to have IT capabilities in each department rather than rely on an IT department charged with competing projects from multiple areas of the institution. Think “distributed model” rather than “centralized model.” That’s why you shouldn’t expect the CIO or CTO to automatically jump on board. Losing control of some IT functions and distributing decisions is definitely scary and potentially threatening. In finance specifically, institutions now have to compete with fintechs, so getting the IT talent they need to shift to a distributed model can be a major challenge. Let’s face it, it’s difficult finding IT folks who are up on newer technologies and excited about working at a bank or credit union.
Bottom Line: The digital native strategy will ultimately deliver the biggest cost savings as well as the ability for companies to adapt quickly when change comes. But the internal challenges and the operational risks could prove too painful. Wrap, decouple + digitize: gradual iteration This path replaces the front-end with a digital experience for consumers, while acknowledging that the underlying legacy systems need to go… at least eventually. With this approach, you fix the front-end and build a decoupling capability that enables you to use your backends, while you create a roadmap outlining how and when you will retire your aging systems and replace them with new digital solutions. You get the big bang impact from revamping your front-end, while establishing a timetable for complete digital transformation. Taking this path, companies can use Low Code, Process Automation, Service Oriented Architecture and APIs, Robotic Process Automation and Artificial Intelligence to integrate with front-end apps and experiences. This integration approach gives employees a 360-degree view of the customer and sets the stage for modular, “plug and play” capabilities.
With data integrated across the organization, the organization can become more agile. Instead of multiple sites or separated channels, customers can have access to all of their accounts with a single sign-on. And employees can quickly turn data into real insights, customer interactions are more tailored to them.
Besides that this approach will provide a powerful transition stage, it also enables a more rationalized digital architecture, where systems are separated by concern, driving agility and efficiency.
For Systems of Record (SOR) we need to go back the core and reimplement the "vanilla" principle – using out of the box features without customization. When required we adopt the processes enabled by the tool, but we don’t adapt the software.
For Systems of Differentation (SOD) we should refactor and converge to ONE low-code suite – e.g., using Netcall Liberty Create – and re-factor existing legacy tools with it.
Bottom Line: The wrap and digitize approach yields a customer experience that tends to be better than the front-end only path, and the transformation process can drag out over many years. Each improvement is made one by one, so it might take a little time to tackle all your processes. On the flip side, the costs are spread out, making it a more affordable approach and more attractive to management teams, who are concerned that they may be disrupting too much at one time. This is a great option for companies that need to take a more gradual approach and that need to show value from digital investments, as the business case is created on two important levels: at the end-customer level, impacting customer experience and at the core of the company, improving the ability to integrate the backends. Pivotal for success with this approach is to realize a certain maturity level in terms of enterprise architecture, service orientation (SOA) and APIs, deploying low-code, RPA and AI capabilities, while focusing extremely on CX/UX - ideally through customer journey design.
Comments