SERVICE STANDARD · POINT 8
Iterate and improve frequently
Launch day is not the finish line. Services drift when teams stop learning from users, support contacts, and performance data.
Treat launch as a starting point. Use data from research, analytics, and support contacts to prioritise improvements. Services that stop iterating tend to drift away from what users actually need.
Iteration needs capacity and permission after go-live. Teams should have a pipeline of improvements grounded in evidence — not just defect fixes but purposeful changes to better meet user needs.
This point connects strongly to Live phase work: retrospectives, performance reviews, and ongoing research keep the service aligned with reality.
How teams usually demonstrate this
- Post-launch backlog with user-need-driven improvements
- Regular review of analytics, support themes, and research
- Published changelog or iteration history for significant changes
- Capacity reserved for continuous improvement, not only incidents
Phases where this often matters
See also delivery phase guides and how frameworks fit together.
Related standard points
- Point 4: Make the service simple to use
- Point 7: Use agile ways of working
- Point 10: Define success and publish performance data
Point 8 of the Service Standard is published by the Government Digital Service on GOV.UK. Content is available under the Open Government Licence v3.0. UCD Services explains the standard in its own words and is not affiliated with GOV.UK or the Government Digital Service.