This blog post is for anyone interested in the technical development of GOV.UK Verify.
There are 3 parts to GOV.UK Verify: the hub (which allows communication between the user, the certified company, and the service on GOV.UK); the certified companies’ service (which verifies your identity and confirms it to government); and the Document Checking Service (which allows the certified company to check digitally that your given information matches a valid record).
The GOV.UK Verify delivery team is responsible for building and maintaining the GOV.UK Verify hub and Document Checking Service. We are organised into 3 teams around our current technical delivery priorities. These are: increasing adoption of GOV.UK Verify, improving and maintaining GOV.UK Verify and reducing our technical debt.
These teams are made up of developers, engineers, analysts, product managers, delivery managers and architects.
In this post I’ll explain what we’ve been working on over the past 2 weeks and what we plan to do next.
Increasing adoption of GOV.UK Verify
We want departments across government to adopt GOV.UK Verify increasingly as it progresses from beta to live because it’s secure, straightforward and meets the needs of their users. Here are the things we’ve done to improve GOV.UK Verify and make it better for end users:
- completed an AB test that proved we should stop asking users if they access to their financial records when recommending the best certified company for them
- developed a tool for the DVLA to enable them to performance test their matching service and our matching service adaptor
- made it clearer to users that they need to have their documents with them during verification
- began recommending relevant certified companies to users who have a photocard driving licence from Great Britain and a smartphone
- improved our analytics of the answers users provide on the hub
- allowed users to return to the hub from a certified company and choose another one within the same session
- improved our performance monitoring and reporting to make it more accurate
Improving and maintaining GOV.UK Verify
We want to improve the way we run the GOV.UK Verify federation and ensure we’re ready to run a live service come April 2016. To keep GOV.UK Verify available and secure, and to meet the most pressing needs of end users, we’ve:
- released a new version of the Matching Service Adapter with performance improvements. The Matching Service Adaptor is a tool which simplifies the integration with GOV.UK Verify.
- resolved an issue with the Compliance Tool which prevented a department from being able to test their service during the onboarding stage
Reducing our technical debt
To reduce accumulated technical debt and allow us to continue to deliver at pace, we’ve:
- improved the logic behind questions on the hub and the certified company recommendations, allowing us to make improvements faster in the future
Things we plan to do next
Over the next 2 to 3 weeks we expect to:
- run an A/B test to assess a potential improvement in the hub user journey
- continue to improve our performance monitoring and reporting
- continue to adapt the hub to accommodate new certified companies and verification options for users
Subscribe to the blog and keep up to date with GOV.UK Verify's latest technical developments.