The conclusion to Part 3 (The Reboot) was:
- Verify – It’s time to be brave and ignore sunk costs (investment to date and contractual exit costs if any) and let this one go. It hasn’t achieved any of the plans that were set out for it and it isn’t magically going to get to 20m users in the next couple of years, least of all if HMRC are going their own way. The real reason for letting it go, though, is that it doesn’t solve the real problem – identity is multi-faceted. I’m me, but I do my mother’s tax return, but appoint my accountant to do mins, but I work for a company and I do their payroll, and I counter-sign the VAT return that is prepared by someone else, and I act as the power of attorney for my blind father. Taking a slice of that isn’t helping. Having many systems that each do a piece of that is as far from handling user needs as you can get. Driving take up by having a lower burden of proof isn’t useful either – ask the Tax Credits folks. HMRC are, by far, the biggest user of the Gateway. They need citizen and business (big business, sole trader, small company) capability. Let them take the lead – they did on the Gateway and that worked out well – and put support around them to help ensure it meets the wider needs.
- GDS speakers at the event encouraged suppliers to use the GaaP tools in their own products, in the hope of widening their use. However, according to guests at the event that Computer Weekly talked to – who wished to remain anonymous due to their ongoing relationships with GDS – GDS was unable to give any guarantees around support or service levels.
- GDS has now developed a new feature for Verify that allows “level of assurance 1” (LOA1) – a reduced level of verification that is effectively a straightforward user login and password system, which offers “minimal confidence in the asserted identity” of users for low-risk transactions. In effect, LOA1 means the government service trusts the user to verify their own identity.
- The government has committed to having 25 million users of Verify by 2020, and offering LOA1 is seen as a key step in widening the adoption of the service to meet this target.
- The goal isn’t to have 25 million users. That’s a metric from 1999 when eyeballs were all that mattered. 25 million users that don’t access services, or that sign up for one and never use another service isn’t a measure of relevancy
- A government authentication platform is instead for:
- Giving its users a secure, trusted way of accessing information that government holds about them and allowing them to update it, provide new items and interact with government processes
- Allowing users to act as themselves as well as representatives of others (corporate and personal) with the assurance that there is proper authorisation in place from all necessary parties
- Putting sufficient protection in the way so as to ensure that my data and interactions cannot be accessed or carried out by people who aren’t me. In other words, “I am who I say I am” and, by definition, no one else is
- Create an environment where a first time user, someone who has had no meaningful interaction with government before, is able to transact online and need never use offline processes from that moment on
- Sixteen year olds would begin their online interaction with government by getting their National Insurance numbers online
- They would go on to apply for their student loan a couple of years later
- With their first job they would receive their PAYE information and perhaps claim some benefits
- Perhaps they would be handling PAYE, or VAT, or CT for their own employer
- Health information and records would be available to the right people and would move them as they moved jobs and locations
- Perhaps they would be looking at health information and records for others
- They would see the impact of pension contributions and understand the impact of changes in taxation
- Perhaps they would be helping other people figure out their pension contributions and entitlements
- They might decide whether they can afford an ISA this year
- In time some would pay their Self Assessment this way
- Or maybe they would be completing Self Assessments for others
|A 2002 Slide|
Instead of spot creating some transactions that are nearby or easy, we would seek to change the entire experience that someone has who doesn’t know about government – they would never know that it had been broken for years, that paper forms were the norm for many, or that in 2010 people had to go from department to department to get what they needed. They would take to this the way a baby learns that you swipe an an iPad screen – it would never occur to them that a magazine doesn’t work the same way.
This wouldn’t be about transformation – the bulk of the users wouldn’t know what it was like before. This would just be “the way government is”, the way it’s supposed to be. Yes, in the background there would have been re-engineering (not, please, transformation), but all the user would see is the way it worked, fluidly, consistently and clearly, in their language, the language of the user.
Verify isn’t the way into this journey. Verify started out trying to solve a different problem. It isn’t seen, and wasn’t conceived, as part of a cohesive whole where the real aim is to shift interaction from offline to online. In its current form, it’s on life support, being kept alive only because there’s a reluctance to deal with the sunk costs – the undoubtedly huge effort (money and time from good people) it’s taken to get here. But it’s a “you can’t get there from here” problem. And when that’s the case … you have to be brave and stop digging.
If my original take on “What is GDS for” was:
GDS is for facilitating the re-engineering of the way government does business – changing from the traditional, departmentally-led silos and individual forms to joined-up, proactive, thought-through interactions that range widely across government. It is not, in my view, about controlling, stopping, writing code or religious/philosophical debates about what’s right. It’s job is to remove the obstacles that stop government from championing the user cause.
Then what if GDS took the vanguard in moving government to cater for the user journey, from a user’s first interaction to its last. A focused programme of making an online government available to everyone. A way of assessing that “I am who I say I am” is an essential part of that – and starting with a 16 year old with minimal footprint is going to be challenging but is surely an essential part of making this work. This would be a visionary challenge – something that could be laid out step by step, month to month, in partnership with the key departments.
It can be dull to look backwards, but sometimes we have to, so that we move forward sensibly. The picture above shows the approach we planned at the Inland Revenue a long time ago. We would take on three parallel streams of work – (1) move forms online, (2) join up with some other departments to create something new and (3) put together a full vertical slice that was entirely online and extend that – we were going to start with a company because our thinking was that they would move online first (this was in 2000): register the company, apply for VAT and tax status, send in returns, add employees, create pensions etc.
It feels like we’ve lost that vision and, instead, are creating ad hoc transactions based on departmental readiness, budget and willingness to play. That’s about as far away from user needs as I can imagine being.
As a post-script, I was intrigued by this line in the Computer Weekly report:
GDS was unable to give any guarantees around support or service levels.
On the face of it, it’s true. GDS is part of the Cabinet Office and so can’t issue contracts to third parties where it might incur penalties for non-delivery. But if others are to invest and put their own customer relationships on the line, this is hardly a user needs led conversation. Back in 2004 we spent some time looking at legal vehicles – trading funds, agencies, JVs, spin-offs – and there are lots of options, some that can be reached quite quickly.
My fundamental point, though, is that GDS should be facilitating the re-engineering of government, helping departments and holding them to account for their promises, not trying to replace the private sector, or step fully into the service delivery chain – least of all if the next step in the delivery promise is “you will have to take our word for it.”