In many change programmes, go-live is treated as the point of success. However, the real test actually begins, in most cases, once the system has launched, the process has changed, and the new operating model is in place.
A change programme has only truly succeeded once the new way of working is understood, adopted, controlled and is producing the expected outcomes. Without these outcomes, the programme may appear complete, but the risks, workarounds and old behaviours may still be present.
The FCA’s 2026/27 Work Programme continues the regulator’s shift towards becoming smarter, more data-led, and more technology-enabled; it uses data and technology to strengthen supervision, streamline regulatory activity, and identify risk more effectively.
Now, firms need to show that change is fully embedded, with the right controls, ownership, and evidence working in practice. The risk here is that too many programmes lose focus too soon, with reduced governance, a lack of understanding across the organisation, and responsibility lost across teams.
While the programme may have reached go-live, firms need to be mindful that, once launched, teams may still have work to do to achieve the outcome the programme was intended to deliver.
Many programmes are judged too early, often leaving gaps that become visible only after the project team has stepped back. Teams may return to familiar ways of working if the new process feels unclear, and managers may lack the information needed to monitor adoption.
As a result, senior leaders may assume the change has landed purely because the programme is complete. However, this can quickly create problems; if the new process is not being followed, the firm may struggle to evidence control effectiveness, customer outcomes, risk management or operational resilience. The issue is not simply that adoption is lower than planned, but that the organisation may not know where the gaps are until they become more difficult to correct.
To succeed, change programmes need a clear post-go-live plan. Firms should be confident in measuring adoption, ownership beyond completion, what evidence to capture, and how to escalate issues.
A stronger approach treats go-live as the start of a controlled transition; the organisation still needs active oversight, clear ownership, practical support, and reliable management information until the change operates consistently.
Change programmes often fail after go-live because the organisation reduces attention at the point where oversight is still needed. Before launch, there is usually a clear programme structure, with meetings in place, risks tracked, and progress reported regularly. Once the change is live, the project team moves on, governance forums become less frequent and the business is expected to absorb the new process into daily activity.
The crucial gap is in the handover, where ownership may still be unclear and training may not have reached every team. Documentation may also still be changing to reflect how work happens under the new change, and some controls may not have been fully tested in a live environment.
In many cases, workarounds appear during this time: teams may create their own ways of completing the work, managers may own separate progress trackers, and people may still reconcile and correct information manually. While these behaviours can keep activity moving, they also weaken the control environment and reduce confidence in the change.
Most of the time, teams try to make the new process work with the tools, information, and time available, rather than wholly resisting the change. However, if the programme has not planned properly for embedding, these issues can quickly become part of day-to-day operations before senior leaders review the change's full impact.
To support a successful change programme, teams need to exercise discipline post-go-live. Firms need to ensure governance and reporting are fully in place so the change is working as intended. Without this, a programme may be marked as delivered, but the organisation could risk continuing with the same operational problems they experienced previously.
As supervision becomes more data-led and technology-enabled, organisations need to demonstrate that change has been implemented properly and operates in practice.
Firms need to evidence that the new process, system or control is producing the intended outcome. They also need to know who owns it, how it is monitored, what MI is available and how issues are identified. A firm may update a policy, implement a new workflow or introduce revised controls, but the real question is whether teams understand the change and follow it consistently. If evidence is weak, ownership is unclear, or reporting does not show how the change is working, the firm may struggle to demonstrate effective implementation.
The same applies to technology and data-led change, as new platforms, automation and reporting tools may improve capability, but they also create new control points. Data quality, access, approval routes, exception handling and output review all need to be understood after go-live. Otherwise, the firm may have introduced new technology without enough clarity around how it is governed in day-to-day use.
In a regulated environment, successful change needs to leave behind a stronger operating model, clearer accountability and better evidence. Go-live should not be the point where scrutiny reduces, but the point where the organisation starts testing whether the change is working under real conditions.
Embedding change properly means ensuring that the new process, system or control can operate without relying on the original project team, which is where clear ownership is most effective. Once the programme moves into business as usual, people need to know who is accountable for the process, who monitors performance, who resolves issues and who decides when further change is needed.
Leaders also need to use practical management information to see whether the change is being used, whether controls are working, whether exceptions are increasing, and whether benefits are being realised. This information should become part of the ongoing rhythm of how the business monitors performance and risk.
Training and communication also need to continue after launch, as initial training may explain the process, but teams often understand the real impact only once they start using it. User feedback can show where instructions are unclear, where the process creates delays, or where additional support is needed.
Control testing is another important part of embedding; a control that works in a design document may behave differently once volumes increase, teams are under pressure, or exceptions start to appear. As such, firms need to test whether controls operate as intended, whether evidence is captured, and whether the process can withstand normal business conditions.
When ownership, MI, training, feedback and controls are properly embedded, the business has a stronger chance of sustaining the change after go-live.
Firms should define what successful adoption will look like, not only what needs to be delivered. That means agreeing how the new process will be used, how performance will be measured, what evidence will be captured and how issues will be managed once the programme moves into live operation.
BAU ownership should also be confirmed before go-live. If accountability is unclear at launch, it is unlikely to become clearer once the project team starts to step back. The business needs to know who owns the process, who owns the controls, who owns the data and who has authority to make decisions when problems arise.
Firms should also agree what evidence will be needed after implementation, which may include adoption data, control testing results, exception reporting, customer or colleague feedback, benefit tracking and updated process documentation.
The strongest programmes build these requirements into delivery from the beginning, defining the handover, ownership, reporting, and assurance needed to ensure the change can operate in practice.
Brighter Consultancy supports firms with the delivery, governance and embedding of complex change programmes. We help organisations move beyond implementation plans and ensure change operates effectively in practice, with clear ownership, strong controls, practical reporting and the right evidence in place.
Our work can support programme governance, implementation planning, post-go-live assurance, operating model design, control testing, MI development and business readiness. We also help firms identify where change is not landing as intended, so issues can be addressed before they become embedded operational problems.
If your organisation is preparing for a regulatory, operational or technology change programme, Brighter Consultancy can help build the structure, governance and assurance needed to make change last beyond go-live.
Talk to us.