GDS design principles and design-driven public services
WRITTEN ON April 4th, 2012 BY William Heath AND STORED IN Design: Co-creation, Design: user-oriented, Ideal government IT strategy, Save Time and Money, We told you so...
Like a contented snore from a prolonged snooze, here’s a quick and now rare post to acknowledge the new GDS design principles:
1 Start with needs*
2 Do less
3 Design with data
4 Do the hard work to make it simple
5 Iterate. Then iterate again.
6 Build for inclusion
7 Understand context
8 Build digital services, not websites
9 Be consistent, not uniform
10 Make things open: it makes things better
It’s a great start. For digital services it strikes me as close to ideal; better than we could have thought to ask for. What we would still ask is that the notion of “starting with needs” and “doing less” be extended to policy and public services more universally.
On this basis it makes sense and feels achievable to go 100% digital for that hwich can be digitised. But it’s not just a digital thing. This is the culture we need across the board.
One Response to “GDS design principles and design-driven public services”
Great list of resources William, I like number 2 Do Less.