January 27, 2021
Myth or Reality? Core Deemphasized
The idea of the core taking a backseat is a myth: Core systems are not necessarily the drivers of digital projects, but they are the enablers.
Many of you have been in insurance for quite some time, and it might sound amazing to even ask you to consider the possibility that core systems will take a backseat to digital projects.
Because of the pandemic, there was a real pause back in March to reassess what the priorities were. How would core systems need to interact? How would we keep pursuing core systems – as replacements, enhancements, in new roles, etc.? In this digital age, we feel tugs and pulls from the many different priorities that we have. Are we trying to cut some costs? Are we really focused on all of the digital engagement initiatives that we have underway? And where does core sit in all of this?
Well, I would suggest that the idea of the core taking a backseat is a myth: Core systems are not necessarily the drivers of digital projects, but they are the enablers. They are the core – the hub of many of the interactions with data from both internal resources and external resources. The facilitation of transactions connected via APIs is now the critical enabler for digital engagement.
When we look to our internal operations, how effective are our resources, our underwriters, our billing staff or our claims staff? Is the core system enabling them to move forward with their tasks in the most efficient and effective way? How open and interactive is your core system with bot technologies or robotic process automation (RPA)?
We must enable the balance between the digital workforce and the human workforce to be the most efficient that it can be.
There is a plethora of different technologies and initiatives out there focused on external digital projects. We now have digital platforms. We have new user interface (UI) initiatives. We have a whole new way of looking at our interactions with customers and agents.
How does your core system help enable the transactions? Is it open? Does it have access to the APIs? Is it efficient? Can it perform? Can it live in the new world?
We know empirically from our research this past year that core, because of the type of expense it is and because of its criticality to organizations, continues to push forward as a key initiative.
Whether you’re sourcing a new system, in initial deployment or in rollout, remember that core initiatives do not take place in a short time. They are significant investments.
We are balancing a new world of digitally engaged platforms with the enterprise core system needs that we have today. There is a fit and purpose for every type of solution out there. Some are meant to expedite product innovation, and others are meant to handle the thrust and bulk of transactions and the volume of significant blocks of business. The important thing is to make sure your core system is working cohesively within your digital structure and enabling you to move forward with the digital projects that you have underway.
See also: Cloud Computing Wins in COVID-19 World
Call to Action:
To counteract the myth that core systems will take a backseat to digital projects, my call to action is to really make sure you’re using a core system that has and can expose their capabilities via APIs – because the core system is going to have to live within the new ecosystems in and of itself.
It is not the entire ecosystem, and it is not the only solution that you’re going to have in play. This digital landscape requires much more from core systems from an interaction standpoint. Core systems must be able to interoperate with other technologies and enable interactions, and they must be as open as they possibly can be. We have to open up these systems to make them much more collaborative, available and accessible so we can capitalize on the gains made with cloud deployments, which will enable improved scalability and versatility.