Publicis Sapient
CORE MODERNISATION PLAYBOOK
Modernize your core bank in four clear steps.
The Core Banking Conundrum
There are two statements upon which almost every bank leadership team will agree:
- Their current core technology stack is struggling to keep up with the rapid shift to the digital-first, seamless interactions their customers, colleagues, and partners expect.
- Replacing these technologies is risky, complex, and expensive.
But the shift to modern core technologies is inevitable. Every year, banks are investing more and more time and money just to maintain the status quo. New regulations, rising digital expectations, and open banking are pushing legacy systems to the limit. Workarounds have made additional change riskier and more expensive. With increasing digital transactions and the rising customer expectation for personalized interactions and connected offerings, these challenges will only get harder to overcome.
Key Statistics:
- 48% of banks identify moving to a modern cloud-based banking system as their top priority.
- 37% of banks expect to transform their operations with a new cloud-based banking system.
- 1 in 10 banking systems are estimated to be running entirely on the cloud in 2023.
- 12% is the predicted increase in core modernization projects over the next year.
- 40% of APAC banks will undertake a coreless modernization program in the next 3 years.
- 51% of U.S. banks believe that a lack of agility is their greatest competitive threat.
The Case for Core Modernization
Replacing these core systems is no easy task. In the past, the easiest way for a CEO or CIO to lose their job was to propose a core system transformation and then fail to deliver it. The success stories are far outnumbered by the failures: programs that overran, overspent, and ultimately failed to achieve real value.
But times have changed. New technologies—from cloud, to coreless banking systems, to the surrounding ecosystem of SaaS solutions—have matured, been proven, and now enable differentiated services. More progressive, iterative approaches to core modernization can significantly mitigate transformation risks.
Put simply, the time to transform is now.
Benefits of a Modern Core Banking System:
- Lower operating costs and optimized change investments.
- Faster launch times for new products.
- Personalized banking experiences.
- More process and decision automation through real-time data streaming.
- Combine best-of-breed components, removing reliance on a single vendor and reducing the need for heavy customizations.
- Adopt new channels and ways of engaging customers.
A New Approach to Core Modernization
In this guide, we lay out a new approach to a longstanding challenge. We’ll outline how you can modernize your current core technology stack and deliver the experiences your customers expect, while sidestepping the pitfalls that cause most modernization projects to fail.
You will:
- Learn how to translate your ambition into an actionable transformation plan.
- Discover how to open new areas of growth for your business.
- Find out how to mitigate the risks of core modernization.
- Get tips on securing buy-in for your program from across your organization.
We’ve broken down the process into four clear, actionable steps.
Your Four-Step Guide to Core Modernization
At each step, we’ll list out the jobs you need to do and the pitfalls you need to avoid to deliver your modernization program without a hitch.
- Confirm your ambitions
- Mobilize the program
- Prove the platform
- Scale, progressively
Step 1: Confirm Your Ambitions
A successful modernization program begins with a clear and aligned ambition—one which everyone believes in and is committed to, from the board to the on-the-ground teams. Core modernization efforts fail when ambitions are poorly defined or misdirected.
Avoid these critical mistakes:
- An unclear ‘case for change’ that fails to drive commitment from the full leadership team.
- Failing to understand the major factors required for the program’s success.
Step-by-Step Guide:
Shape the Case for Change
- Ensure a common belief in the need for modernization, including:
- The critical challenges which modernization can address.
- The importance of modernization for achieving the bank’s north star vision.
- The benefits which modern capabilities and hosted cloud can unlock.
- The return on investment from modernization.
Understand the Success Requirements
- Core modernization requires addressing gaps across the organization, not just within technology. We recommend a comprehensive assessment to cover:
- Organization and cultural readiness.
- Change capacity and methods.
- Data and technology landscape.
- Risk and compliance requirements.
- Migration and integration complexity.
- Business readiness requirements.
Ensure Leadership Team Commitment
- The senior leadership team needs to understand and commit to the ambitions of the core modernization program. This will require:
- Ensuring a clear north star vision for the modernization effort.
- An investment case which has been tested with the CFO.
- An understanding of major program risks and how they will be mitigated.
- A clear roadmap and timeline for delivering the program.
- A robust method for overseeing the program with clear accountable owners assigned.
Establish the Program Leadership Team
- The right program leadership team must be established and set up for success. This will require:
- Selecting the right leaders for the program; this may require new hires.
- Enabling these leaders through appropriate funding, decisioning rights, and resourcing.
- Mobilizing supporting upstream and downstream functions and allocating appropriate accountability for modernization outcomes.
Step 2: Mobilize the Program
With your ambition set, you now need to ensure you set up the program for success: with the right people, the right roadmap, and the right vision for what can be achieved by when. Without the right preparation, modernization programs cannot succeed.
Watch out for these common preparation pitfalls:
- Product plans that result in a large early investment with no value release for years.
- Reproducing the legacy core rather than embracing the possibilities of a coreless architecture.
Step-by-Step Guide:
Mobilize the Program Team
- Bring the right combination of business, functional, and technology capabilities and:
- Confirm the leadership team, ensuring leaders are committed to challenging existing approaches.
- Set up the governance forums and design authorities required to make decisions at pace while mitigating risks.
- Ensure the right level of engagement from the broader organization (e.g., risk and compliance).
- Onboard the right delivery partner(s) to support the scaled transformation efforts.
Confirm the Product Roadmap
- Bring greater clarity to what the modernized platform will enable, and the iterative development pathway to achieve this future state by:
- Bringing to life major customer, partner, and/or colleague journeys and how the legacy core serves them.
- Linking these journeys and their requirements to the major data & technology and operational enablers.
- Confirming the series of launches and technical proof points required to achieve the target state.
- Adding greater detail and focus for the first major launch—the ‘pathfinder’—including the initial build and team requirements.
- Linking the roadmap to the benefits and cost to achieve, including key outcomes/KPIs.
Design the Coreless Architecture
- Use modern engineering practices to define the future-proof, coreless solution architecture by:
- Aligning on best-practice architectural principles.
- Conducting domain modeling to map existing capabilities into the domains forming core capability centers.
- Assessing and selecting best-of-breed vendors to make up the critical components.
- Ensuring a clear view of major integrations and migrations required and how to mitigate risks.
- Understanding the implications for the existing technology teams.
Fast-Track Any Critical Enablers
- Even as you confirm the future roadmap, you can begin to address critical path requirements including:
- Shortlisting preferred core solution providers.
- Confirming and building the required cloud infrastructure requirements.
- Aligning on the API and Data strategy and enabling requirements.
- Begin shaping the desired operating model for a coreless bank.
Step 3: Prove the Platform
Now it’s time to deliver. It’s critical to prove the new platform via a ‘pathfinder’ which includes a customer-facing launch. Getting to market quickly builds belief in the new capabilities while enabling learning and continuous iteration through real experience. The first release is pivotal to proving the modernization program and learning for subsequent releases.
Watch out for these pitfalls:
- Failing to launch, usually from a combination of incorrect delivery model, missing ‘go-live’ requirements, or taking on too much too soon.
- Not reducing the migration and integration complexity. There are often non-technical solutions such as product rationalization that can significantly mitigate risks.
Step-by-Step Guide:
Shift into Action
- Scale the delivery teams and methods required, including:
- Mobilizing all required cross-functional teams aligned around outcomes, not deliverables.
- Leveraging value-focused best-practice enterprise agile methodologies.
- Onboarding prioritized solution providers.
- Launching required training/capability building initiatives.
- Ensuring appropriate communication plans are in place, and strong program governance for value recognition and timely decision making.
- Ensuring risk and control requirements are understood and are automated where possible.
- Assuring regulatory commitments and obtaining internal and regulatory approval required for the pathfinder to go live.
- Delivering fully integrated and tested pathfinder to production in co-existence with the legacy core.
- Completing the operating model for the pathfinder including temporary coexistence demands.
Deliver the Pathfinder
- Ruthlessly focus on a series of releases to prove the new platform and its ability to unlock value for the bank, including:
- Building foundational elements such as environments, cloud, Data, DevSecOps, and vendor deployments.
- Identifying customers and accounts to migrate based on characteristics, size and complexity, channels, and usage patterns.
- Isolating and integrating legacy capabilities to function independently, establishing scaffolding to manage the coexistence of the pathfinder with the legacy core.
- Creating an automated reconciliation engine for data quality and migration exceptions.
- Setting up the model office to enable full business readiness testing.
(Re)shape the Post-Pathfinder Scaling Roadmap
- Ensure successful management of the coexistence interim state and the future pathway for scaling the platform and the migration onto it:
- Conduct retrospectives to reflect on learning from pathfinder to refine the next tranche of products and customers to be adopted.
- Ensure the appropriate methods are in place for managing the new and old environments simultaneously.
- (Re)shape the post-pathfinder delivery roadmap to bring the new platform to scale.
- Further detail and confirm the progressive migration strategy, including opportunities to mitigate complexity and risks involved (e.g., through product rationalization, customer incentives, etc.).
- Create a reuse catalog for capabilities, products, and foundational modules to support reuse and efficiency for future releases.
- Measure customer and efficiency metrics from the pathfinder.
Step 4: Modernize, Progressively
With the platform now proven, it’s time to accelerate its expansion and transition from the legacy onto the new modernized platform through a series of iterative releases. Ensuring the safe shift from legacy to modern platforms is a real challenge. It’s critical to prepare appropriately and ensure a full spectrum of levers are leveraged to mitigate risks.
Watch out for these additional pitfalls:
- Sequencing the migration appropriately, migrating in tranches and minimizing risk and disruption for customers.
- Failure to maintain a strong comms plan can lose program momentum and leave you stuck with co-existence, delaying full value release.
Step-by-Step Guide:
Expand the Coreless Platform
- Accelerate the build of the new platform, focusing on where the new capabilities can drive the most value for your customers and colleagues:
- Expand the platform, prioritizing new features based on value, speed, and quality metrics.
- Accelerate the pace of new releases, ensuring feedback loops to enable continuous learning from live-launches and migrations.
- Drive continued exploration of new, differentiated approaches that the new platform can enable and with which competitors will struggle to compete.
- Sustain the momentum. Ensure constant communication across the organization of major successes and setbacks to ensure continued commitment.
Scale the Modernization Factory
- Progressively develop the remainder of the functionality and migrate from the legacy, leveraging a full suite of capabilities to mitigate risks:
- Establish a modernization factory to continue to prioritize, deliver, and migrate new tranches of customers and products to the new platform.
- Gradually transition coexistence interim state to the target future model as the volumes shift from the old to the new platform.
- Decommission systems where beneficial based on the cost savings vs. the risks from completely transitioning from these systems.
Sustain the Change
- Ensure a smooth transition from modernization as a program to the new future state with a modern coreless bank:
- Build the right capabilities and skillsets needed to continuously enhance and expand the new coreless model.
- Begin to leverage modernization OKRs/metrics as the new business-as-usual management systems.
- Continue constant dialogue with competent authorities to build confidence in the new platform.
Core Modernization FAQs
Do I really need to modernize?
Yes. Not only do we see core modernization enable significant efficiencies—from automated processes to streamlined reporting—but also create new growth pathways for our clients. We believe within the next five years, a gulf will open up between those that have modernized, and those that have not.
Is it risky to build a coreless architecture?
There has been significant investment in the entire financial services technology space, dramatically improving the maturity of major software-as-a-service providers. The general integration patterns have been proven, and with the right engineering know-how, the critical foundational elements (such as the right API frameworks) can be quickly set up. The benefits from a coreless model now outweigh the costs.
Can you effectively mitigate the risks from migration?
It’s not easy, but it is possible. New technologies and approaches can make the process easier to manage. And getting commitment from the business and operational teams (in addition to the technology teams) ensures you can leverage a broader set of levers, such as enhanced product offerings, to incentivize voluntary rather than forced customer migrations. New UI/UX design patterns can also ensure the transition is seamless for customers.
How do you handle the dual-run interim state?
There are a variety of methods that can be used to support the build out of the new modern platform while running the existing capabilities. For example, we find it useful to establish a “model office” construct that runs any new functionality and grows as volumes on the new platform expand. Understanding the direction of travel for the future state, and the changes involved, ensures a strong understanding of the shifts required as volumes on the new platform increase. It’s also critical to be one step ahead of this transition: bringing in the right skills and capabilities to thrive in this future state.
What are the main reasons these programs tend to fail?
Often there is a failure of alignment across the senior leadership team on the modernization ambition. This is critical as success requires sustained commitment. It is then critical to ensure continuous releases—rather than “big bang” releases—as these build belief and prove the new model.
Speed and quality of delivery are, therefore, essential. Taking this approach, however, will challenge existing ways of working, so it’s critical to bring the organization along the modernization journey with regular communication and engagement to ensure understanding of the program, while also appropriately challenging the application of existing approaches to the new modernized world.
Let’s Start Your Core Modernization
While the opportunity to modernize the core of your bank might seem daunting, with the right planning and the right partners, you can position yourself for success. There will be challenges ahead. But staying focused on the big picture and maintaining your team’s enthusiasm and excitement will sustain you through the hard days.
Choosing the right partner is critical. Working alongside a partner with experience in creating modern coreless architectures helps you identify where you want to be, and navigate the complex journey to a more efficient banking model.
Success requires an ability to drive commitment to a clear modernization strategy, shape compelling new customer experiences, deliver the new platform at pace, and deploy best-practice modern engineering and data capabilities.
With success, you can harness the creativity on which the global tech giants rely, and more automation, greater personalization, and faster release cycles can help you realize the full power of digital transformation.
We’re ready to help you discover the exciting possibilities of core modernization. With our experienced team, stress-tested methodologies, and our unique SPEED capabilities, we’ll work with you to create banking products that put your customers first.
SPEED Capabilities:
- Strategy: Developing and testing hypotheses on priority value pools
- Product: Evolve propositions at pace and scale
- Experience: Create value for members and colleagues
- Engineering: Deliver on your promise, at pace, and at scale
- Data: Build compelling data/AI platforms, products, and deliver powerful insights
Contact:
- David Murphy – david.murphy@publicissapient.com
- Abhishek Bhattacharya – abhishek.bhattacharya@publicissapient.com
- Zachary Scott – zachary.scott@publicissapient.com
- Cian Ó Braonáin – cian.obraonain@publicissapient.com
www.publicissapient.com