What happens after services go live? What happens once large scale digital transformation programmes end? Sarah and Juliette share what they learned discussing this topic with International Design in Government community.
We're building an autocomplete – we've started by building one for users to provide country and territory information. Here's why we're developing it and what we've done so far.
Chris Thomas, designer on the Cross-Government Service Data team, writes about some of the things he learned about designing during an alpha.
This is the third in our series of blog posts about new patterns looking at the 'tasks' or elements of a service. This post looks in detail at the task list pattern.
We're publishing new patterns looking at the ‘tasks’ or elements of a service. This blog post is about our new ‘check before you start' pattern.
We're publishing new patterns looking at the ‘tasks’ or elements of a service, rather than trying to create patterns for the service or license as a whole. This blog post is about our new ‘naming your service’ pattern.
Paul Smith, a frontend developer at DWP, writes about why it's so important to make our work open and how we can all help make this happen.
...build design culture in their teams and departments. Things like show and tells, retrospectives, meetups and even team lunches and outings. Other practices include shared language and collective actions such...
We've collected examples from around government of services that require users to upload something.
We're planning to set up an international government design group, bringing together practitioners to talk about our work, share best practice and discuss some of the common issues we face.
On 9 March, GDS will host a day for students interested in finding out more about design in the public sector.
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.