The first thing you see when you walk into GDS is the 7 main messages which guided the build of the GOV.UK alpha. Visitors to GDS often scribble them down, and like our Design Principles they help provide a shared language for people inside and outside government.
They’re also really useful points to keep in mind as we build a community around the exemplar services and the new service manual.
Digital by default
In November 2012 the Government Digital Strategy stated that from April 2014 all new and redesigned services processing over 100,000 transactions a year would have to meet the digital by default standard if they were to be launched and linked to from GOV.UK. It also stated that GDS would be responsible for defining that standard. In promoting an agile approach, the standard and guidance are a radical departure from what’s gone before.
Putting users first
People who use the standard are service managers. Service managers develop and deliver all the changes necessary to provide effective digital services. Because the role of service manager is relatively new it’s been a challenge to find them in government departments and to engage them in our development process. Other users of the standard are digital leaders, service teams (including designers and developers) and our own transformation team. By talking to these users we created profiles and user journeys to map out how each user might use the guidance. We then structured the guidance accordingly for our alpha release.
Learning from the journey
We wanted to expose our users to the standard and the service design manual as often as possible. We started with a simple email group, sending out weekly updates about the development of the standard and requesting feedback on its content, structure, guidance and governance. We kept close ties with our transformation team to make sure we added new service managers to the group as they joined GDS. The feedback became a foundation for the beta version of the standard, released last month.
Building a network of trust
When iterating the alpha version, we were determined to include as much user feedback as possible. In January 2013 we held a workshop for colleagues across government to air their concerns and expectations. This session was invaluable and we collated feedback into a directory, identifying the most significant areas of concern. We told our users what actions we were going to take in time for the beta release; by doing this our users could see that we were focusing on the areas they cared about most.
Moving barriers aside
At the workshop service managers asked for more opportunities to meet up to share ideas and discuss similarities about service transformation across government. We proposed a service managers’ ‘show and tell’.
Creating an environment for technology leaders to flourish
The first event went ahead on 11 April and brought together service managers from the Ministry of Defence (MOD), the Ministry of Justice (MoJ), Her Majesty’s Revenue & Customs (HMRC), the Department for Transport (DfT) and the Cabinet Office. The format proved to be a success, with service managers identifying and sharing problems and proposing solutions.
The service manager show and tell will now be a regular event, but our approach to building the community is still very much driven by what our users are telling us. We will continue to work with service managers to identify needs and help make the connections that will ultimately lead to more information sharing and better services being built.