Introduction to GOV.UK and user needs
โขDownload as PPT, PDFโข
2 likesโข772 views
A presentation by Louise Russell and Abby Rudland from Local Direct. The presentation covers how GOV.UK was developed and how it puts user needs at the heart of content design.
Recommended
Recommended
More Related Content
Similar to Introduction to GOV.UK and user needs
Similar to Introduction to GOV.UK and user needs (20)
More from Local Direct
More from Local Direct (7)
Recently uploaded
Recently uploaded (20)
Introduction to GOV.UK and user needs
- 2. How did we get here?
- 3. In 2004 the government web went from a loosely coordinated collection of websites...
- 4. to something a bit simpler... Directgov Business Link
- 5. A tremendous achievement, which brought enormous benefits, but itโs time to move on again Directgov Business Link
- 6. The web is now mainstream Users expect high quality service experiences And businesses know how to deliver them
- 9. They went from this... directgov businesslink Directgov Business Link
- 10. ...to a single domain Mainstream Users & Needs Specialist Users & Needs GOV.UK
- 11. Focused on user needs, not government needs
- 12. Simpler
- 15. Clearer
- 18. Faster
- 23. Itโs saved money.. ยฃ42 million (2012/2013) by replacing Directgov, BusinessLink, departmental sites and related organisation sites with GOV.UK
- 24. E.g. Online: 22p Phone: ยฃ4.11 Post: ยฃ6.62 Digital by default 20 x cheaper than phone, 30 x cheaper than post 50 x cheaper than face-to-face
- 25. It does less
- 26. It does less
- 27. Itโs focussed on tasks - getting to the โquick doโ
- 28. It optimises for the common case but doesnโt ignore the edge case
- 29. GOV.UK is bigโฆ
- 30. Itโs won awards Design of the Year 2013 D&Ad Awards 2013
- 31. What does this mean for local government?
- 32. There are 134 journeys from GOV.UK to local government
- 36. Letโs talk technical But not for long!
- 37. Small teams of world-class developers, designers and managers Tight control of experience design Iterative, agile, user-focused product development
- 38. Theyโre building GOV.UK the way Google build Google and Amazon build Amazon
- 39. Theyโre using open source and making that source freely available
- 40. GOV.UK is being extensively and continuously tested and improved so it works better for users
- 41. GOV.UK โ putting user needs at the heart of content design
- 42. What is a user need?
- 43. Whoโs the audience? Whatโs the action? Why do they want to do it?
- 44. Defining the user need โAs a _______ I want to ________ so that I can ________โ
- 45. Defining the user need โAs a self-employed person I want to file my tax return so that I can avoid nasty fines.โ
- 46. โAs a self-employed person I want to file my tax return so that I can avoid nasty fines.โ
- 48. Content should be as short, simple and specific as possible Users wonโt read your content - so donโt make them!
- 50. Front-load sentences with the important stuff If itโs not essential, leave it out Break it up. Use - short sentences and paragraphs - subheads - lists - active voice
Editor's Notes
- 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
- But what is a user need? And how do you work out what the needs of your users are?
- These 3 simple lines help you think about 1 who the user is 2 what the action is 3 why the user wants to do the action
- GOV.UK uses a simple formula. As a blank, I want to blank so that I can blank.
- So for example, โAs a self-employed person, I want to file my tax return so that I can avoid nasty fines.โ
- Hereโs a reason why you should keep things short and simple: Most people read webpages in an F-shape pattern. Ie they read the top few lines, then scan down, looking at the beginnings of lines and subheadings By halfway down the page, theyโve stopped reading!
- To deal with this style of readingโฆ (see slide)