davidbgk
/
larlet-fr-david-cache
Watch 1
Star 0
Fork 0
Code Releases 0 Activity
A place to cache linked articles (think custom and personal wayback machine)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
21 Commits
1 Branch
Tree: e695708c14
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from 'e695708c14'
${ noResults }
larlet-fr-david-cache/cache/b5a2cbb6fa8c7df0b2c6dcb3ee9.../index.md

index.md 4.6KB
Raw Blame History

title: Digital by Default Service Standard url: https://www.gov.uk/service-manual/digital-by-default hash_url: b5a2cbb6fa

The Digital Service Standard has changed from 26 points to a more concise 18. From 1 June 2015 all transactional services will be assessed on the new 18 points.

The Service Standard ensures digital teams build high quality government services.

A transactional service must meet each criteria to pass the Government Digital Service assessment. If a service doesn’t pass it won’t appear on GOV.UK.

Assisted digital support is an integral part of any service, helping users who can't complete the service on their own.

The criteria

  1. Understand user needs. Research to develop a deep knowledge of who the service users are and what that means for the design of the service.

  2. Put a plan in place for ongoing user research and usability testing to continuously seek feedback from users to improve the service.

  3. Put in place a sustainable multidisciplinary team that can design, build and operate the service, led by a suitably skilled and senior service manager with decision-making responsibility.

  4. Build the service using the agile, iterative and user-centred methods set out in the manual.

  5. Build a service that can be iterated and improved on a frequent basis and make sure that you have the capacity, resources and technical flexibility to do so.

  6. Evaluate what tools and systems will be used to build, host, operate and measure the service, and how to procure them.

  7. Evaluate what user data and information the digital service will be providing or storing, and address the security level, legal responsibilities, privacy issues and risks associated with the service (consulting with experts where appropriate).

  8. Make all new source code open and reusable, and publish it under appropriate licences (or provide a convincing explanation as to why this cannot be done for specific subsets of the source code).

  9. Use open standards and common government platforms where available.

  10. Be able to test the end-to-end service in an environment identical to that of the live version, including on all common browsers and devices, and using dummy accounts and a representative sample of users.

  11. Make a plan for the event of the digital service being taken temporarily offline.

  12. Create a service that is simple and intuitive enough that users succeed first time.

  13. Build a service consistent with the user experience of the rest of GOV.UK including using the design patterns and style guide.

  14. Encourage all users to use the digital service (with assisted digital support if required), alongside an appropriate plan to phase out non-digital channels/services.

  15. Use tools for analysis that collect performance data. Use this data to analyse the success of the service and to translate this into features and tasks for the next phase of development.

  16. Identify performance indicators for the service, including the 4 mandatory key performance indicators (KPIs) defined in the manual. Establish a benchmark for each metric and make a plan to enable improvements.

  17. Report performance data on the Performance Platform.

  18. Test the service from beginning to end with the minister responsible for it.