You’ve been building a service to meet users needs, and after your public beta you have a tested solution that is ready to release.

Going live

To provide a fully resilient service to all end users the service should now meet all security and performance standards. You have configured your analytics to accurately monitor the key performance indicators identified in the building of your service, and you have planned the transition or integration of any existing services.

You have liaised with the team governing the Digital by Default Service Standard to make sure that you have met the requirements of new and redesigned services.

And, most importantly, you have met the user needs identified in the discovery, alpha and beta phases.

Post-launch stages

This is not the end of the process. The service should now be improved continuously, based on user feedback, analytics and further research.

Operational support – both technical and customer-focused – is in place, and you have implemented pro-active monitoring methods. These will help you to:

  • monitor system performance
  • optimise the code
  • ensure the service remains secure

You’ll repeat the whole process (discovery, alpha, beta and live) for smaller pieces of work as the service continues running. Find something that needs improvement, research solutions, iterate, release. That should be a constant rhythm for the operating team, and done rapidly.

Team requirements

You’ll have identified the roles required to run your service, including the service manager and user support teams, while building the service. As different areas of your service are iterated and improved the team size will expand and contract, accommodating specialists as appropriate.