https://gds.blog.gov.uk/2016/12/19/introducing-the-next-stage-of-the-service-manual/

Introducing the next stage of the Service Manual

The new Service Manual homepage

The latest iteration of the Service Manual is now published. The Service Manual exists to help people across government build services that meet the Digital Service Standard and prepare for service assessments.

Over the past year, we’ve built a new front end and created or updated more than 150 pages. We’ve just added a new homepage.

We’ve made all of these improvements gradually. In September we wrote about some of the work we did earlier in the year. Now, we want to share what the latest steps have been.

Changes we’ve made

Ahead of making any changes, we ran a discovery to find out what the most valuable improvements would be. As a result, here’s what’s changed:

  • we’ve been improving topics since we first published in January 2016, and we’ll keep doing that
  • we’ve introduced a new information layout for easier navigation: we’ve created new topics, subtopics and guides and we’ll continue to test and improve them
  • subject-matter experts have checked every piece of content in the new manual to make sure it’s up to date and factually correct
  • we’ve removed duplicate content and redirected content so bookmarks and saved links don’t break
  • the manual is now written in plain English and follows the latest GOV.UK style guide
  • we’ve standardised the way we present content across the manual so that it's consistent and therefore quicker and easier to read
  • we’ve built a new publisher so that it is easier to update the content - previously we updated content via Github

This is just the beginning

What we’ve done has given us a great base to build on, but it’s just the start.

We’ve already started improving content and we’ll continue to do so based on analytics, user research and feedback, and the help we get from experts.

We know that every service is different, and the manual can’t just explain how to build a service in a one-size-fits-all way.

GDS wants to support government to build great services and we want the Service Manual to play a part in this.

Talk to us

The Service Manual is for the benefit of service teams across government. With your help, we can make sure it keeps improving. As we iterate the manual, we want to hear from you.

There is a feedback option at the bottom of every page of the Service Manual. You can also leave a comment below to let us know what you think about the changes.

Follow GDS on Twitter, and don’t forget to sign up for email alerts.

6 comments

  1. Comment by Mark Aberdour posted on

    Hi, are you still managing this content changes to the service manual on Github at this URL? https://github.com/alphagov/government-service-design-manual

    As a gov supplier, this was very useful for watching and receiving notifications of changes to the manual, but I get the impression that github repo may be defunct now? if so, are you managing via another repo?

    many thanks!

    • Replies to Mark Aberdour>

      Comment by Alice Noakes posted on

      Hi Mark
      We're no longer using Github to manage the content of the Service Manual. However, you can subscribe to receive email alerts whenever guides are added or updated. To do this, go to the topic that you're interested in and sign up to 'Get notifications' on the right hand side. All the topics are listed on the Service Manual homepage (https://www.gov.uk/service-manual). You can also subscribe to receive alerts for the Digital Service Standard (https://www.gov.uk/service-manual/service-standard).

      • Replies to Alice Noakes>

        Comment by Oli Wood posted on

        No longer sharing via github? Well that's a massive step backwards. One of the things that made gov.uk great was that that it made is easier for all the world to improve. Subscribe for notification by email - is this the 90s? What about seeing the history? What about being able to fork it and drive our own companies behaviours off this excellent example?

        If the driver for this was "but we need a CMS everybody could use" maybe you should have built that so that it pushes to GitHub? That would be helpful in lots of ways, to lots of people too.

        100% retrograde step and upsetting to see on a project that has been such an inspiration. Sad times.

        • Replies to Oli Wood>

          Comment by Alice Noakes posted on

          Hi Oli, thanks for your comment. Feedback like this is useful as we continue to iterate the Service Manual.
          Change notes summarising updates are available for every page in the manual. We store a version history of each page, and can explore the need for displaying a full version history in future, as well as needs for content syndication.
          User research identified that while content management and engagement in GitHub was useful for some, it was a barrier to others and at alpha the team made the decision to build the new Service Manual on GOV.UK. This allows a full-time team of content designers to work with communities of practice across government to keep guidance up to date. The move to the GOV.UK platform also provides a robust tech support model and a development roadmap that the Service Manual will continue to benefit from.

  2. Comment by Matthew Ford posted on

    One aspect of moving off github which will be missed is the opportunity of open discussions around changes or proposed changes.

    • Replies to Matthew Ford>

      Comment by Alice Noakes posted on

      Thank you for this feedback, Matthew. Content in the Service Manual is written by our communities of practice. Research at alpha showed that discussions about content usually happen away from the Service Manual and GitHub itself, before consensus is reached and guidance is published in the manual. You can find out how to get involved in these discussions via the community pages in the manual.