Select Page

How the live phase works

The live phase is the time to keep improving your service based on:

  • user feedback
  • analytics
  • your ongoing user research

Before you go live

Before you can make your service live, you must make sure:

  • the service meets the user needs you found in your discovery, alpha and beta phases
  • you’re securing the service’s information
  • you’ve set up your analytics to accurately measure the success of your service
  • you’ve got a plan for the transition or integration of any existing services that meet a similar user need to yours
  • the service fully meets the Design principles and can continue to do so
  • you can support the service and you’ll be able to keep iterating it and improving it until it’s retired

The team you need in live

You should know the roles you need to run your service, based on your experience of building it.

Don’t disband your service team, or hand the service over to a ‘business as usual’ team that won’t keep iterating and improving it.

As you iterate and improve different parts of your service, you may find the team size changes along with your need for specialist roles.

After you go live

After you move to the live phase you should keep improving your service based on user feedback, analytics and further user research.

You should also:

  • monitor the status of your service
  • maintain uptime and availability
  • practise vulnerability and penetration testing
  • test your service’s performance
  • maintain quality assurance

You should repeat the development phases (discovery, alpha, beta and live) for smaller pieces of work as your service continues running.

Keep finding things that need improvement, do research to get the best solutions, iterate, then release.