...each other. Learning sessions also allow us to experiment and try new tools and approaches without the same concerns we have when building code for a production environment. One of...
...they can continue their journey researched new ways to explain to users how GOV.UK Verify works so they can make better-informed decisions about which certified company to choose. Improving and...
...some new ideas that we are planning to test and iterate over coming months. This blog post provides an insight into what was covered. What we did During the first...
...under new contracts added new journeys to the hub to reflect the new features released by the certified companies - for example, we can now recommend certified companies for users...
...through our requirements and, in particular, thinking about the data. This resulted in a life-sized sketch of the prototype, which showed the connections between data sets and meant that everyone...
...points of the standard before going live. The GOV.UK Verify team used the criteria of the Service Standard as a tool for development throughout GOV.UK Verify’s beta phase as it...
...new? if we were to build something new, should it be a cross-government service like GOV.UK Verify? how can someone prove, entirely digitally, that an organisation exists and they have...
...so that it’s as clear as possible to services what they will need to do, and any new needs arising from new services adopting GOV.UK Verify are understood early on...
...point. We are building a new service, in a new market, and in a new way, for the first time anywhere in the UK and in a way that’s unlike...
...users. To improve GOV.UK Verify and make it better for end users, since our last update we’ve: started A/B testing an improved ‘Can I be verified?’ page. The new design...
