We work with government agencies to develop internal and digital solutions that support our vision of a simple, inclusive and selective government for all. Last month’s story on the GDS blog highlighted the problem we’re trying to solve. The other part is the answer to the signature problem, and now we want to share some of the alpha group keys.
Before we share our lessons learned, we want to talk about signing up simultaneously with a specific digital number. We started by talking to the staff about their needs. And so we broke down the problem to make two statements.
Requirements:
• create a smart, safe way for people to participate in all government services (once registered)
• allow users to show their status at a location (identification card)
This is a big problem and there are many things to look out for. So, a team at GDS looks at the statistics, we interact with the signing at the same time.
Why don’t we work on a sign?
Our general opinion is:
People use the same name and website for all the domains they use
• Users can create unique numbers, where they want, and use them in government services
• Any citizen who wants to register government statistics, can use our service
A signature is a common problem; the groups said they needed answers now. It’s also the doorstep of our best digital service, and the first person we need to start managing.
What do we want that person to do to be served? It should be:
• allow the user to sign in and access government services
• ensure that service teams ensure that each user receives a regular service (confirmation)
And, as we have on service boards, it will gradually become a secret name and for users who want to remember to use government services.
What was learned?
We recently attended an alpha test and our meeting with state partners. I am happy to say that we have succeeded in reaching the level of service. Our mission statement ‘The smartest and safest way to enter the public sphere, and the easiest way to mobilize workers across the country will be closely linked.
During Alpha, we recruited 329 participating researchers for important and specialized studies. And we spoke to 30 service providers from thirteen departments to understand what they need from a real-world product and the latest experience.
We want to share with you some important lessons from our Alpha.
Study 1
Users do not know the brand of the services
From our research, we found that users struggle to sign up for the services they want to use. They:
• Cannot remember the domain name and the expression where the service is used
• affected that government views and therefore those who think their username and password should work for all services
• Frustration if the government does not work as they think it should
We want to clean up this mess by helping run the government the way consumers have long thought.
Study 2
Build on what we already know
Many great subscription products are available in the state. They were not designed to serve all governments, but we can learn much from them and what happened to the workers and their users.
We have worked with support groups to understand what works best and what lessons we can learn from technology, implementation, and management.
We have worked with Veterans UK to link the Energy Payment and Critical Pension Scheme internally to test our skills and performance. Tom Stewart, Assistant Head of New Day Training for Veterans UK, said, as part of this important and exciting work. ”.
We want to make sure we use open positions wherever we can, so we are an Open ID Connect (OIDC) service. OIDC is an open-source certification used in transactions such as Open Banking and login.gov (equivalent US Gov.).
We want to build on what the government already knows and build a single signature in a flexible service house to meet the needs of different digital services and their users.
Study 3
Taking on a task for service teams
Our desired products are easy for ‘classes’ to come in and use. We want to simplify the experience of the ship. Over the course of 4 months, we spoke to about 30 service groups to find out what they need in this system.
We performed an alpha test with the Military Compensation Project service. We wanted to see how soon they would meet us. It took them 3 hours. We learned a lot about how to improve our customer experience.
We want to make sure that what we build is right for our service team and that they are easy to use at all times.