LG/WWW

Sometimes you have to push back. It won't make you popular, but when business requirements and user needs clash you have to stand up for the user. Let me give you two examples of this. A service delivery team wanted a new digital service so that users could register for a permit. Most of the proposed questions were simple and straightforward, but two weren't. They were: Upload a copy of a recent utility bill  Upload a copy of your vehicle's V5 certificate Asking these questions assumes that the user has access to the technology to scan or take a picture of the documents required, and also the skills required to use the technology. We asked the team to research their service users' skills and their access to technology. At present the service is being created without these two questions. The second example is where a new law and statutory requirement meant the creation of a new digital service. The service delivery team wanted the digital service to ask arou

Why aren't the private sector lobbying for the public sector to use open standards? Why would they do that you might ask? Well let me propose why they should be, and what's in it for them. Take how the private sector sell to councils for example, whether you're buying a product, SaaS or using a paid for service another way, this is generally how it works Yes, I know that the API might be a database connection and there's lots other ways to integrate a service with a website or app, but let's look at this model for now. So the maximum number of clients the supplier can ever reach directly is 433 because that's the number of Tier 1 and 2 councils in the UK. So lets make one change that enables another. Now the API is using open standards. This in turn opens up a new market, as now suppliers can sell direct to the service user, because they can build in the knowledge that the API won't change. So now they've expanded their market from