We’ve launched the Service Toolkit to give teams across government quick access to the resources they need to build and run services.
GDS turns 5 this week (officially on Thursday 8 December), and we’re celebrating all week.
We’re going to spend some time on this blog looking back at the story so far. We’ll also look forward to the future.
December 2015 was the wettest month ever recorded in the UK. We didn’t have time to do a complete revision of the content before imminent flooding. So we made a few quick fixes and planned to return to the content in the spring for a proper improvement project.
We’ve blogged before about our discovery into building better service assessments. Now we’re ready to talk about our new approach.
The US government runs an International Visitors Leadership Program, which brings together future leaders from around the world. The most recent visit was for future digital and technology leaders and GDS was invited to take part. We wanted to share what we learnt.
Webchat is a support channel where users can talk to advisers through real-time online text chat. We ran an alpha to learn from departments that have been using webchat and to learn what works for users.
Kevin previously wrote about how GDS needs to make a commitment to collaborate with all government departments. This post announces 2 new senior appointments to GDS. Both will play a vital part in making that collaboration happen.
The Performance Platform measures how government services are performing. The team recently did a rediscovery of its work and now we’re exploring what data we should provide and how we should provide it to enable better decisions about government services.
At the Transforming Together event, Kevin Cunnington set out his initial views on what GDS is here to do and how we’re going to do it.
This week, there has been a series of events running across the country to celebrate National Get Online Week. We also announced the GDS charity of the year, Dragon Hall.
When designing services or creating content, we always start by thinking about user needs. We create registers in the same way.