top of page

Continuous Innovation for Regulatory Organisations: Go-Live is Just the Beginning

13 hours ago
4 min read






I have spent more than twenty years working across infrastructure, release management, and live services, including fifteen years supporting Microsoft Dynamics environments at large organisations running major transformation programmes.


Over that time, I have seen plenty of successful go-lives. They matter because they represent years of planning, delivery and hard work. But I have also learned that go-live is rarely when a transformation's value is proven. The real test begins when the organisation starts depending on the platform every day.


What happens after go-live comes down to a few things I have seen repeatedly over the years: whether the support team understands the context, whether knowledge is retained, whether problems are genuinely fixed rather than simply closed, and whether the platform can evolve with the organisation.


Supporting a regulator requires more than Microsoft expertise


If a registration platform goes down, it is not simply a technical issue. A registrant may not be able to join the register, a professional may be unable to renew their licence, or a regulator may be unable to fulfil a statutory responsibility. That is why regulatory domain expertise is as important as technical capability.


Today I lead a dedicated onshore team that supports live Microsoft business application services for more than eight regulatory organisations across the UK and Ireland, covering critical regulatory processes relied on by over a million registrants. Working with these organisations every day means we understand the regulatory processes behind the technology.


That knowledge sits alongside deep Microsoft capability across Dynamics 365, Power Platform, Azure and the wider Microsoft cloud ecosystem. It means we can look at a problem through both lenses: what is happening technically, and what does it mean for the regulatory service?


That understanding becomes even more important after implementation, when project teams begin to move on.


The continuity challenge


One of the biggest challenges I have seen in the industry is the loss of knowledge after implementation. I have watched organisations spend two years building institutional knowledge with a supplier, only to lose it all in a single resourcing decision.


Our model is different. We are a 100% onshore team, and our project, delivery, support, and leadership teams all work from the same office. If a complex issue arises, we simply turn around our desks and collaborate with the people who built, delivered and now support the service. That makes a big difference.


That continuity is also reflected in how we work with clients. All our regulatory clients work directly with me as their Service Delivery Manager, so they know who is accountable for the service. When an issue arises, we take ownership from start to finish, whether that means resolving it ourselves or working directly with Microsoft when platform support is required.


It also allows us to ask a better question. Not just, “How do we fix this?” but, “What should we improve next?” That is where our role begins to move beyond support. We become an extension of the client’s team, using shared knowledge to help them continually improve and look ahead.


Continuous improvement means looking ahead


The longer you support a live service, the more opportunities you see to make it better. Support gives us the knowledge and insight, but continuous improvement is how we turn that into structured change.


We deliver continuous improvement through a governance-led and evidence-based approach embedded within our Managed Services model. We maintain a roadmap of opportunities identified through service reviews, user feedback, operational insight, Microsoft release waves, automation opportunities and new capabilities such as AI and Copilot. Each opportunity is assessed against business value, effort, risk, security, compliance and adoption impact so investment is focused on changes that deliver tangible outcomes.


Microsoft is evolving at the same time. Dynamics 365 and Power Platform continue to change through new capabilities, updates to existing functionality and retirements of older features, alongside its major release waves. Part of our role is to understand what those developments mean for each client and help them decide what to adopt, what to prepare for and where there is an opportunity to improve.


A modern Microsoft platform should not look exactly the same several years after go-live. Regulations change, organisations evolve, business priorities shift, policies develop, user expectations mature, and the technology itself advances. The platform should evolve alongside them.


I have seen the value of that adaptability first-hand. When the Nursing and Midwifery Council modernised its registration services, the platform faced an extraordinary test later, during the COVID-19 pandemic. Legislative changes meant the NMC needed to establish an emergency temporary register, allowing nurses who had recently left the register and overseas professionals already progressing through registration to enter practice quickly. By extending the existing Microsoft platform, the team delivered the new capability in three weeks.


That showed the value of the transformation wasn't simply delivering the original requirements. It was in having a platform that could respond to a completely new requirement when the organisation and the public needed it.


That is what Continuous Improvement enables. It helps regulators move beyond looking back at what has already happened and become more proactive, more adaptable and better prepared for what comes next.


For our team, go-live is actually the beginning


There is a simple question every organisation should ask its support partner. "What part of our platform is worse today than it was twelve months ago, and what are you doing about it?"

A supplier focused only on day-to-day support may struggle to answer that because they see the immediate service rather than where it needs to go next. A partner who genuinely understands your organisation should have a clear view of what needs improving and why.


Go-live is a milestone, and people should be proud of it. But it is also the moment your organisation starts depending on the platform. Everything that follows: the legislative change nobody forecast, the platform update, the process that quietly stopped fitting how the team works, determines whether the investment continues to deliver.


Our delivery, support, managed services, and continuous improvement are one coherent service, delivered onshore by my team, with accountability.


If you cannot get a straight answer to the question above, it is worth a conversation. Get in touch.


 
 
 

Comments


bottom of page