Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (19)
Destaque
Semelhante a Intro to gov.uk
Semelhante a Intro to gov.uk (20)
Intro to gov.uk
- 1. Louise Russell Programme Manager Local Directgov
- 2. GOV.UK
- 3. How did we get here?
- 4. In 2004 the government web went from a loosely coordinated collection of websites...
- 5. directgov businesslink to something a bit simpler...
- 6. A tremendous achievement, which brought enormous directgov businesslink benefits, but it’s time to move on again
- 7. The web is now mainstream Users expect high quality service experiences And businesses know how to deliver them
- 9. directgov businesslink directgov businesslink We’ve gone from this...
- 10. GOV.UK Mainstream Users & Needs ...to a single domain Specialist Users & Needs
- 11. Simpler, Clearer, Faster services for Users Savings and Innovation for Government
- 12. Simpler
- 15. Clearer
- 18. Faster
- 21. Savings
- 22. Common platform for hosting, fewer systems, less duplication of effort
- 23. Innovation
- 25. We’re doing less
- 26. We’re doing less
- 27. We’re doing less
- 28. We’re focused on tasks - getting to the ‘quick do’
- 29. We’re focused on tasks - getting to the ‘quick do’
- 30. We’re focused on tasks - getting to the ‘quick do’
- 31. We’re optimising for the common case but not ignoring the edge case
- 32. GDS
- 33. 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.
- 34. Lets talk technical But not for long!
- 35. Small teams of world-class developers, designers and managers Tight control of experience design Iterative, agile, user-focused product development
- 36. We‘ve built GOV.UK the way Google build Google and Amazon build Amazon
- 37. We’re using open source and making that source freely available
- 38. GOV.UK is being extensively and continuously tested and improved so we know it works better for users
- 39. Campaigns
- 40. GOV.UK's primary role is fulfilling user needs - we should not interrupt users or distract from that to deliver campaigns
- 41. But there will be places where ‘campaign spaces’ will be appropriate - the homepage, golden pages, search pages
- 43. For 'task-driven' campaigns (where the principal call to action exists as a need on GOV.UK) we will adapt GOV.UK content page to reflect the campaign
- 45. For 'behaviour-change' campaigns which don't reflect GOV.UK needs and don't need to come from 'government' we'd recommend hosting with partners wherever possible...
- 49. Contact details Louise Russell, Local Directgov louise.russell@communities.gsi.gov.uk
Notas do Editor
- 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.