A launch date does not make a service ready. Use these questions to expose gaps while there is still time to act.
Users and purpose
- The intended users and their main need are clear.
- The first useful outcome can be explained in plain language.
- Representative users have completed the important journeys.
- Accessibility and mobile use have been checked.
Ownership and operations
- One accountable owner can make decisions after launch.
- Support routes, response expectations and escalation points are documented.
- Known manual work and exceptions have named owners.
- Teams know what changes on launch day.
Data and technology
- Required data is available, lawful, accurate enough and protected.
- Integrations, permissions, backups and recovery routes have been tested.
- Monitoring identifies failure before users have to report it repeatedly.
- A rollback or safe-stop decision is understood.
Evidence and improvement
- Success measures relate to the user and service outcome.
- A baseline exists where comparison matters.
- Feedback can reach the people able to act on it.
- The first post-launch review has a date and owner.