GOV.UK Verify: Objectives for live
...government services, and making changes to make GOV.UK Verify as straightforward as possible for people to use. We’ve made a lot of progress in our public beta We now have...
...government services, and making changes to make GOV.UK Verify as straightforward as possible for people to use. We’ve made a lot of progress in our public beta We now have...
...For the first exercise we did the ‘Minisculus Challenge’. This is a set of small coding puzzles based around codebreaking. We ran the exercises in a mob programming style, swapping...
...of the PIA for anyone who wants to know how we assessed privacy-related risks and their potential impact on users during our public beta phase. We’ve also published the full...
...and dice the data in a number of ways. Start with user needs As with everything at GDS, we started with user needs. We spent a lot of time working...
...we were only able to use data from Great Britain in our reporting but we’ve now been able to use data collected by the Northern Ireland by the Northern Ireland...
...them to direct the user to use their credentials for a purpose not evident to the user (such as gaining access to the user’s records within a government service). It...
...to work for users GOV.UK Verify works best for users when it is implemented as an integrated part of a transformed digital service. When users are given a choice between...
...We should improve how often we rotate between who drives the mouse and keyboard We should investigate how we can improve our development setup to support mobbing whether through better...
...and make it better for users, since our last update we’ve: improved the layout and messaging on the page displayed to users after a certified company successfully verifies their identity...
...do next In the coming 3 to 4 weeks we expect to: improve how users can pause and continue verifying their identity at a later time give users clearer information...