We need to prepare for a world where people might not access GOV.UK through their computer or smartphone, but could be using Alexa, Google Assistant or some technology that hasn’t even been created yet. We need to make GOV.UK understandable by humans and machines.
Original: https://gds.blog.gov.uk/2018/06/27/building-the-gov-uk-of-the-future/
…we sort of are a legacy of the original spirit of the web, and that’s very much what the Wikimedia Foundation was created to do — to ensure that Wikipedia was preserved as a nonprofit entity, with respect for community governance, and in the public interest and in the public spirit.
To help us understand the ‘as is’ in more detail we’ve gathered insights from available data and call centre staff, tested how easy it is for users to find things on the site and identified some key gaps in understanding around the importance of designing for user need, measurement and accessibility.
Original: https://servicedesign.blog.essex.gov.uk/2018/04/12/kick-off-for-the-essex-gov-uk-project/
Five more nuggets of interest I’ve spotted this week:
These have all been tweeted during the week, and you can find everything I’ve found interesting and bookmarked here.
There was a nice guest post from Doug Belshaw from Mozilla on Brian Kelly’s blog last week.
Entitled What Does Working Openly on the Web Mean in Practice?, it told us a bit about Mozilla’s culture of openness and how it ties into web based working.
Here’s a quick quote:
Working open is not only in Mozilla’s DNA but leads to huge benefits for the project more broadly. While Mozilla has hundreds of paid contributors, they have tens of thousands of volunteer contributors — all working together to keep the web open and as a platform for innovation. Working open means Mozilla can draw on talent no matter where in the world someone happens to live. It means people with what Clay Shirky would call cognitive surplus can contribute as much or as little free time and labour to projects as they wish. Importantly, it also leads to a level of trust that users can have in Mozilla’s products. Not only can they inspect the source code used to build the product, but actually participate in discussions about its development.
But you really ought to go and read the whole thing.
I find this stuff so you don’t have to:
I find this stuff so you don’t have to:
I find this stuff so you don’t have to:
I find this stuff so you don’t have to:
I find this stuff so you don’t have to:
Dave Briggs 