Namit Agarwal, Senior Vice President at i-exceed
There is a point in a major banking technology programme when the rubber meets the road and the project plans gives way to the operating bank. The platform goes live, migration is completed, early issues are stabilised and the focus gradually shifts from implementation milestones to operational resilience and business outcomes.
Many consider, this as the end of implementation but for others that is not the case. The assumptions made when the programme was designed now meet real customer behaviour, adaptation, operating conditions, transaction volumes and the rest of the bank’s technology environment. Some expected benefits become visible, while others prove harder to realise than anticipated.
That makes the period after go-live more than a stabilisation phase. This toddler period is the phase when transformation truly takes shape and the bank begins to realise the strategic value of its investments.
When the business case meets reality
Before implementation, the value of a technology programme has to be expressed through a business case. The expected outcomes are defined in advance: perhaps a better customer journey, lower cost of servicing, faster product delivery, greater automation, regulatory compliance, improved integration or the retirement of older technology.
Once the platform is live, however, the relationship between the technology and those outcomes becomes observable in a way it never could be during the programme.
Actual usage begins to show which capabilities are being adopted and which are not. Customer journeys reveal where friction has genuinely disappeared and where it has simply moved elsewhere. Operations begin to show which processes have become simpler and which still depend on intervention. The bank also starts to see where the capability is being used differently from what was originally envisaged.
This is where the post-go-live period becomes strategically interesting. The business case stops being a forecast and starts becoming evidence.
That evidence can challenge the original assumptions, but it can also reveal value that was difficult to see beforehand.
Value does not always arrive where it was expected
Technology investments can create effects beyond the outcome for which they were originally envisaged. A new digital onboarding capability, for example, can benefit in more ways than just being a customer acquisition platform. The underlying capabilities such as customer identification, workflow and integration can subsequently support servicing or other customer journeys. A payments capability can generate value through the data, orchestration and connectivity it introduces, not only through the transaction itself.
The same pattern is emerging in wider banking technology research. McKinsey’s analysis of more than 200 core-modernisation business transformation engagements found that much of the historical value came from infrastructure consolidation, technology simplification and lower run costs. Increasingly, however, leading institutions are finding significant value in improved decision quality across areas such as lending, pricing, servicing, fraud management and risk operations.
The significance of this is not limited to core banking. It points to a broader feature of technology investment: once a capability is operating inside the bank, its value can begin to extend beyond the use case that originally justified it.
That is also when reuse becomes visible. Integrations built for one journey can support another. Capabilities deployed through a single channel or customer touch point can be easily deployed via another customer touch point, Data structures can serve new decisions. Workflow capabilities can be applied elsewhere. What began as a project can gradually become part of the bank’s wider technology fabric and turn into an ecosystem.
What remains from the old environment matters too
The other side of this equation is what does not disappear.
Go-live does not automatically remove everything that existed before it. Legacy integrations may continue to support adjacent processes. Older systems may remain necessary for certain products or functions. Data can continue to sit across multiple environments. Processes built around the previous technology can survive because the surrounding operating model has not yet caught up.
Recent research on banking transformation describes this as a persistent problem: programmes can add or replace technology without sufficiently removing underlying complexity, leaving redundant systems, fragmented data and legacy integrations in place.
This creates an interesting tension after implementation. The new capability may be generating value while the old environment continues absorbing cost and organisational attention. At times these legacy components may also prevent you from fully realizing the benefits of new environment.
The strategic picture therefore becomes clearer only over time. The question is no longer simply what the new technology can do, but what is gradually becoming unnecessary because of it, what remains dependent on the old environment, and what new possibilities are emerging around the capability.
The transformation continues in a quieter form
There is also an organisational shift that is easy to miss once the programme structure begins to disappear. During implementation, the transformation has dedicated attention, specialised teams and a strong connection between the technology and the strategic objectives that created it. After go-live, that concentration naturally dilutes as the capability becomes part of normal operations.
This is where the logic behind change research becomes relevant. New ways of working become durable when they are reinforced through the systems and routines of the organisation rather than remaining associated only with the programme that introduced them.
In a bank, that process can take place gradually through product decisions, operating processes, customer journeys and subsequent technology investments. The transformation begins influencing decisions that were never part of the original programme.
That is perhaps the most interesting feature of the post-go-live period: the transformation starts to have a life beyond the transformation programme itself.
Where the longer-term value begins to emerge
Go-live therefore marks a transition between two very different kinds of uncertainty. Before implementation, the question is whether the bank can deliver the capability it has designed. After implementation, the question becomes what that capability changes once it encounters the complexity of the operating bank.
Over time, the answers become more visible. Some benefits become measurable while some assumptions must be revisited. Some of these capabilities find applications beyond their original purpose, and parts of the old environment remain more persistent than expected.
The value of the investment is therefore not fixed at the moment it goes live. It continues to take shape through what the bank learns, reuses, replaces and builds around the capability.
That is what makes the period after go-live worth examining in its own right. The programme may have ended, but the strategic consequences of the investment are only beginning to become visible.