Intro to


Published on

Introduction to GOV.UK, and its origins. Presentation by Louise Russell from DCLG.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • more than 30 million visits a month
  • beta – task completion from c60% to c70%
  • DirectGov - c 120 seconds GOV.UK - c 80 seconds 100,000 days a year
  • Half the people Less than half the cost 7 x the output
  • We ’ re applying similar disciples to departmental sites - reducing costs by creating common templates and publishing tools. Departments still have effective and differentiated web presences, full of content they provide and control, but more consistent design and navigation will ensure users can easily get to the content they want. People shouldn ’ t have to know how government is structured to find the information they need, so we ’ re also playing close attention to how information is structured and tagged – making it easy to search across government. So, for instance, users can find out about a policy or service without having to know, before they start, which department is responsible.
  • Intro to

    1. 1. Louise RussellProgramme Manager Local Directgov
    2. 2. GOV.UK
    3. 3. How did we get here?
    4. 4. In 2004 thegovernment webwent from alooselycoordinatedcollection ofwebsites...
    5. 5. directgov businesslinkto somethinga bit simpler...
    6. 6. A tremendousachievement,which broughtenormous directgov businesslinkbenefits,but it’s time tomove on again
    7. 7. The web is now mainstreamUsers expect high quality serviceexperiencesAnd businesses know how todeliver them
    8. 8. directgov businesslink directgov businesslinkWe’ve gonefrom this...
    9. 9. GOV.UK Mainstream Users & a singledomain Specialist Users & Needs
    10. 10. Simpler, Clearer, Fasterservices for UsersSavings and Innovationfor Government
    11. 11. Simpler
    12. 12. Clearer
    13. 13. Faster
    14. 14. Savings
    15. 15. Common platform for hosting,fewer systems, less duplication ofeffort
    16. 16. Innovation
    17. 17. We’re doing less
    18. 18. We’re doing less
    19. 19. We’re doing less
    20. 20. We’re focused on tasks - gettingto the ‘quick do’
    21. 21. We’re focused on tasks - getting to the‘quick do’
    22. 22. We’re focused on tasks - gettingto the ‘quick do’
    23. 23. We’re optimising for the common case but notignoring the edge case
    24. 24. GDS
    25. 25. What if a user goes to a page that won’t be on GOV.UK?If a user has followed a link to a page on Directgov that is not being reproduced on GOV.UK they will see a message that:• explains the changeover• introduces them to GOV.UK• offers them a link to the National Archives to see the information that used to be on the page• or, whenever possible, a link to information provided by trusted third parties specific to the page they are looking for.
    26. 26. Lets talk technical But not for long!
    27. 27. Small teams of world-classdevelopers, designers andmanagersTight control of experiencedesignIterative, agile, user-focusedproduct development
    28. 28. We‘ve built GOV.UK the wayGoogle build Google and Amazonbuild Amazon
    29. 29. We’re using open source and making that source freely available
    30. 30. GOV.UK is being extensively and continuously tested and improved so we know it works better for users
    31. 31. Campaigns
    32. 32. GOV.UKs primary role isfulfilling user needs - weshould not interrupt usersor distract from that todeliver campaigns
    33. 33. But there will be places where‘campaign spaces’ will beappropriate - the homepage,golden pages, search pages
    34. 34. For task-driven campaigns(where the principal call toaction exists as a need onGOV.UK) we will adaptGOV.UK content page toreflect the campaign
    35. 35. For behaviour-changecampaigns which dont reflectGOV.UK needs and dont needto come from governmentwed recommend hosting withpartners wherever possible...
    36. 36. Contact detailsLouise Russell, Local