Quantcast
Channel: Government Digital Service
Viewing all 965 articles
Browse latest View live

Professions and boldness

$
0
0

Janet Hughes

As the brilliant Janet Hughes says, the civil service should be a place where people can be bold.

I especially like this bit:

Being bold means bringing your whole self to the situation and engaging fully with it. It involves openness, optimism and a commitment to something bigger than yourself.

Yes! I think that leadership means making a space where people can work like that, in line with the Civil Service Code.

People need to work in an environment where that sort of thinking and behaviour is supported. I usually tell the people I work with: “Succeed and that’s on you - mess up, and that’s on me.” Be open, optimistic and committed to something bigger than yourself - I’ll be there with you. That’s never more true than when it comes to doing service transformation.

There are reasons why my Twitter bio says “The gaffer” at GDS: this job isn’t glamorous, and it shouldn’t be. We’ve had an incredible few years showing what is possible to build in government. Now we need to really transform government services, from operations and offline channels through policy and user-facing services, always with user needs at the centre.

Transforming services isn’t something that digital teams or operational service teams do in isolation. It’s increasingly becoming everyone in government’s responsibility. Everyone needs to be able to fix things that aren’t working and use their skills and knowledge to find ways to make services better.

That’s not just about being good at recruiting, we also need to make sure that the structures are right. We need to keep supporting the specialists we already have. There are gifted digital, data and technology specialists across government today - many more than we had when GDS began. Many of those professionals have learnt a lot from the work we’ve done so far. They know what works and what doesn’t when you’re delivering digital government services. And they’re using that knowledge in the best possible way - by sticking with what works, and iterating on what didn’t.

Part of the work that’s being led across government by GDS’s Liv Wild is building up a digital, data and technology profession. We’ll continue to blog about her team’s work. This profession should sit alongside the other professions in the Civil Service, with clear guidelines for how digital or technology professionals should be supported.

We also need to be giving people who are already working in government the chance to learn how digital, data and technology skills are relevant to them, as people who spend their working lives delivering public services. We need to encourage cross-pollination of ideas across professional groups. Great ideas come from combining different perspectives.

We’ve often talked about “delivering at pace”. This requires people working and speaking up according to the best of their abilities. That’s what makes multidisciplinary teams great. We’re building public services so good people prefer to use them, beyond individual transactions. Making sure that government is efficient, and meets user needs, not its own outdated structures. A bold ambition, but not a reckless one. That’s the cause we’re all committed to, and that we’re building professional structures to support it. And beyond having the right structures in place, I believe we should all be showing leadership by giving others the space and support they need to do their jobs to the best of their abilities.

That’s why I cheered when I read Janet’s blog post. Of course that’s how we should act and think and I’m confident we will. Be bold!

Join the conversation on Twitter and don't forget to sign up for email alerts


A hack day to test Government as a Platform

$
0
0

Last week, GDS hosted a hack day for developers from across government. We welcomed about 30 developers to the Cabinet Office to test out some of the new Government as a Platform components that we’ve been working on over the last few months: GOV.UK Pay, GOV.UK Notify, and Government PaaS.

Representatives from digital service teams from all over the country got together to try integrating with our new products. It was a fantastic opportunity to get feedback from one of our main groups of users, to see whether we’ve been heading in the right direction.

Building a community of developers for Government as a Platform

One of the goals of the day was to start building a community of developers from across government, and work collaboratively with them to improve our products. We hosted teams from:

  • Companies House
  • Department for Environment, Food & Rural Affairs
  • Department for Work and Pensions
  • Home Office
  • Ministry of Justice
  • NHS Business Services Authority

The developers who attended are all from services that have worked with GDS to identify the user needs for GOV.UK Pay, GOV.UK Notify and Government PaaS. The hack day was a chance for them to build their own mock services to integrate with GOV.UK Pay to take a test payment, then use GOV.UK Notify to send out an electronic payment confirmation automatically. Once they’d done that they could experiment with hosting their service with Government PaaS.

Hackers at the GaaP hack day

We’ve worked hard to design the APIs - sets of requirements that govern how one application can talk to another - for GOV.UK Pay to be as good as possible. We’ve also thought a lot about producing great documentation that should make the process even more straightforward.

Good news - low technical barrier

The good news is that developers using a range of stacks - Java, Node.js, Python, and Scala - all succeeded in integrating with GOV.UK Pay and taking a test payment in only a few hours. Some of the teams got as far as using GOV.UK Notify, and a few experimented with Government PaaS. This was a great result. It showed the low technical barrier to adoption of these new cross government components. It made clear just how much time will be saved by building reusable components that any public service can use, rather than expecting individual services to tackle payments or notifications on their own.

Things we need to fix

Of course, not everything went perfectly. This was the first time that we’d let more than a handful of our own developers loose on our code. Some things broke. Which in some ways is what we wanted to happen. We learnt a lot about how we can improve our account creation process, increase the robustness of our systems as we move closer to taking real payments later in the year, and identified a number of bugs that need fixing.

We had lots of feedback from attendees; some of it about what was already good, and some, even more usefully, about what we could do better. It was gratifying that the draft GOV.UK Pay documentation got some love, but there were still areas for improvement and each of the GDS teams left with work to do.

Minister visits GOV.UK Pay’s hack day

Hackers with the Minister, Matt Hancock

Before our end of day retrospective we had a visit from Matt Hancock, the Minister for the Cabinet Office. He was keen to come along to express his support for the hack day and our efforts to collaborate closely with departments across government to make sure the platforms we build will work for them. He said:

This hack day is a great example of government embracing ways of working we’d usually associate with innovative startups to make sure we deliver on the Government as a Platform vision. Working together like this, across government, will help us recast the relationship between the citizen and the state.

And we plan to continue doing just that. If you’re a developer interested in joining GDS and doing work that matters, check out our current GDS vacancies.

We hope this will be the first of many hack day events as we continue to work with our partners across government to digitally transform the delivery of public services.

Follow Rory on Twitter and don't forget to sign up for email alerts

Notes from a Swedish explorer

$
0
0

Lars Boström is a Team Leader and Web Coordinator at the Swedish Consumer Agency: a government agency under the Swedish Financial department. Lars is responsible for web development of Hallå Konsument; a web service that gives guidance to consumers in need of help.

Today Lars talks about his experience of job shadowing user researchers here at GDS.

Profile picture of Lars Bostrom

After almost two weeks as a guest at GDS, I’m starting to get to grips with the processes that drive the work that happens here.

During my job shadowing experience I’ve learnt to use GDS vocabulary; I’m in the discovery phase, have explored the way GDS works, made loads of findings and now I’m in the process of sorting the most relevant out, making inferences and drawing conclusions.

I’ve experienced user research training, and I’m now on the wheel of think – make – learn; and I’m learning the importance of communicating your findings. User research is one part research and two parts communication. Writing this post is one way of communicating what I’ve learned.

I would like to start with the most obvious question you might have – why was he around in the first place?

Back home in Sweden I work as a Team Leader in web communications at the government’s Swedish Consumer Agency. During the last two to three years, we’ve been implementing new ways of working with web development. We used to be stuck in the traditional waterfall methodology, but we wanted to explore new ways to work.

The thing that set the ball rolling was when we were given a new mandate from our government, to put forward a new service to Swedish consumers – Hallå Konsument/Hello consumer. This service gives advice to Swedish consumers before they buy something or afterwards when they’ve bought something that they’re having problems with (similar to the way Citizens Advice work in the UK). The service will give consumers help over the web, phone, callback, chat, and through social media – Twitter and Facebook. We also include information from twelve other government agencies, four consumer bureaus, and municipal consumer guidance organisations.

With lots of challenges, we started to search for new ways of doing things. When building the web development part of the new service we tried out agile methodologies and started to follow the GDS blog, - learning from GDS’s work along the way. The things we did were on a rather experimental level and we were mostly finding our path through the project to finish everything in time for the big release.
Now that the service is up and running, we have more time to plan for the future. We’re starting to think about the possibilities and what we could actually do together with our collaborators when it comes to future web services.

The big question now is if I will be able to find a wall or other plain surface big enough to stick all my findings on when I get back home. Because there are loads of them.

Eight findings from GDS I’m taking back home

1. User research and data analysis
The way user research and data analysis runs through everything at GDS is truly impressive; but sometimes it’s hard to grasp if you’re not there observing it first hand. Even if it’s talked about throughout the work you do, it’s hard to really really understand the meaning and importance of it. Especially when you are coming from the old school way of doing web development. We will start to work in a similar way, putting more trust into user research findings as well as data analysis and get a methodology into place.

2. The informal and creative way of doing things
When I first came to the GDS office I was struck by the creative workflow. I later found that this is very typical of the way GDS do things. Meetings seems to be held on the fly; if something needs to be handled you simply walk over to your colleagues and have a short informal chat. It’s not a big thing, and often no meeting arrangements need to be done at all.

3. Professionalism and transparency
The size of GDS allows staff to specialise in their particular area and role. While at the same time, allowing them to collaborate outside their area of expertise . and being completely transparent the whole time.

4. The user researcher role
User research should be for everyone in the team (user research is a team sport) and is something we’ve tried in our teams back home as well. But the role the user researcher plays when leading the process forward has stood out more clearly since my time at GDS.

5. Content design
The way GDS analyses and organises content is worth worldwide respect. With that huge amount of content knocking on their door, many would feel a great weight on their shoulders. But, GDS are methodically taking on the job; starting with user needs and working through the subject. If you’re feeling stressed about it – it’s not showing.

6. The user research lab
The user research lab is a gem among your tools at GDS. Eventually we might be able to establish something similar to do the same kind of work and analysis as you do. That’s something to hope for in the future.

7. Pop-up teams
At times we get problems that need to be handled quickly or need to be looked at in more detail. The temporary pop-up team is a perfect answer to that need. We’ll see if we can implement that way of working back home.

8. Start small and scale it up
It might be easier said than done, but when looking at certain services or challenges we have in front of us it’s easy to be overwhelmed. A calming way of handling it is starting small and scaling it up slowly.

So with that said, I would like to say thanks for having me as your guest during these weeks. I really appreciate being here learning from you – you’re building great stuff!

Keep up the good work.

11 February 2016: Sprint 16 live blog

$
0
0

17:50

Thank you for joining us on our first live blog journey. Don't forget, we're keen to hear all your feedback - feel free to comment below.

Applause slide


17:41


17:39


17:37


17:33


17:30


17:25


17:22


17:19


17:16

Aaron Snow from 18F kicks off by declaring that he's come with stickers. He's done his audience research.


17:14


17:11


17:05


17:03


16:49


16:46

Data panel in action:

Data panel at Sprint 16


16:44


16:30

Here's Paul Maltby's talking about government data:


16:27


16:24


16:10

The Show and Tell sessions went down a storm. Lots of happy, engaged audience members learning more about transforming government together.

Here's some highlights:

Audience during this morning's sessions


Next we have the second set of talks. See what's coming up on the agenda.


16:02

And here's some feedback from the agile session:


15:52

Don't forget to tune into the Periscope live feed from the 'How to be agile in a non-agile environment' session. An accessible version of it will be available on YouTube soon.


15:48

From the GOV.UK Verify Show and Tell:


15:09

We're taking a short break now - back soon with updates from the Show and Tells, before the second half of talks start at 4pm.

Find out what's coming up on the full agenda and continue to follow the action on Twitter. See you shortly.

People chatting with coffee at Sprint 16 event


15:04


15:00

You can take a closer look at this map on the GDS Flickr.


14:58


14:47

Pete Herlihy's presenting outfit is proving popular:


14:45


14:41


14:38


14:35


14:28


14:26


14:25

We're going to transform government together


14:19

#Sprint16 is now trending across the UK


14:18


14:08

Interesting to see what keywords are being used:


14:00

Eileen Burbidge is up next:


13:50

#Sprint16 is trending in London:


13:47

Matt Hancock talks about collaboration:

 


13:35

Stephen Foreshew-Cain, our Executive Director welcomed everyone to Sprint 16 and said this:

Everyone in the civil service has a part to play in transforming the relationship between the citizen and the state

Matt Hancock, Minister for the Cabinet Office, is our first speaker today.

 


13:03

Registration is almost over - the main event is due to start at 1.15pm.

First up will be our very own Executive Director Stephen Foreshew-Cain, followed by Minister for the Cabinet Office Matt Hancock.

See the full agenda here.

Follow live on Twitter #Sprint16 @gdsteam, and keep checking back here for updates, photos, videos, and quotes.

Empty auditorium with large "Sprint 16" image on the big screen

People queuing to register at Sprint 16 People queuing to register at Sprint 16


12:48

Not sure what #Sprint16 is all about? Here's the highlights from Sprint 15:


11:45

Registration begins shortly. In the meantime, anticipation is building.

Join the conversation #Sprint16  @gdsteam.


11:30

#Sprint16 is about to begin.

Sprint 16 display screen

This is the first time we’ve live-blogged an event. The idea is to share the audience perspective, links to more information, and snippets of the day. We hope to start a conversation that will continue long after #Sprint16 is over.

As with anything new, we’re not sure how this will go. We could end up with a fantastic resource and record of the event, but we might not. We really appreciate your feedback and input: this year’s Sprint is all about transforming government together, and that togetherness starts from the ground up. Live blogs included.

We’ll be updating this blog throughout the day, so bookmark this page and check back now until around 6pm tonight.

Feel free to comment below, or on Twitter @gdsteam #Sprint16.

Transforming government together

$
0
0

Every now and then we do well by taking stock of where we are and to map out the future. Sprint 16 was one of those moments.

Over 450 attendees from across government gathered together to see first-hand the platforms, services and new ways of working happening in the civil service. It was a great day; feedback has been superb, and the energy in the room was fantastic.

We talked about transforming government together. And we talked about the way we do that: by being bold.

For those who weren’t able to be there, here’s a snapshot of the things I highlighted at the end of the day:

We’re moving fast. Let’s keep up the momentum

Since 2010, we’ve been moving at a pace we couldn’t have imagined a few years earlier. Martha’s report drove us to develop a collective will and shared responsibility as we transform government.

Collectively, we’ve made government much simpler for users. We’ve invested in digital skills. We’ve started a two-way conversation with suppliers. And we’ve transformed our relationship with technology. Together we have done a lot. And this is just the beginning.

We now have both the momentum and, following the spending review, the mandate to make real change. We have the foundations to really transform government, together.

When we share our learning, we’re stronger

We learn best when we learn in the open. There are many examples: the Digital Service Standard; Service Design Manual; Technology code of practice; Sprint events; blogs and mailing lists of digital teams across government.

All these are not the work of any one person, agency, or department. They represent what we’ve all learned, collectively: they’re our better practice. I don’t like to say “best practice” because we know someone, somewhere, has just learned how to do it better. That’s why our standards, guides, and codes of practice keep evolving.

Building on our collective knowledge

As our colleagues deliver lasting transformation, GDS will support them. Whether that’s acting as curators and collectors of learning, helping at the sharp-end of delivery, or providing targeted support as people transform their services.

We’ll work together to define new performance measures, that help us all understand how the whole service is doing – not just the digital take-up or cost per digital transaction.

And we’ll provide expert support on things like on digital strategy, service mapping, identifying, and applying service patterns. The support people need, when they need it.

Developing digital capability at every level of government

Transforming services isn’t something only digital teams or operational service teams do in isolation. It is a shared responsibility. We need digital skills to be part of the DNA of the modern civil servant, supported by skilled professionals and specialists when needed.

That means everyone in government has to attract, develop, and keep people who can transform services. At GDS we’ll lead development of the digital, data, and technology profession to do this, and continue to make the Civil Service a destination for people who want their skills to make a real difference to society.

GDS won’t build everything

GDS will remain at the centre, doing the hard work on cross-government platforms and services. We won’t be building all of them. We will be making sure they get built.

Because these platforms and services will be genuinely transformative, and will make building, iterating and retiring services easy for Service Managers and their teams.

We’ll keep leading on:

We’ll work across government to fix data

Data is a vital, shared asset which underpins effective digital services. GDS will work with our colleagues to fix how we manage, maintain and use data, supported by the policies and governance that ensure citizens’ data is secure, and their privacy protected.

We’re building a linked ecosystem of canonical, properly curated and updated registers of data. These will be used to make services efficient, effective and — where appropriate — interconnected. The countries register is just the first example of what this ecosystem will look like.

We’ve got your back

The changes I’m asking us all to make are big, exciting, and challenging; we all need to be bold to make it happen. To do that, people on the frontline need to know the centre will back them up, and will give them the tools they need to do the right thing for their users. We will.

The conversations that happened last Thursday are just the beginning. What matters most is what colleagues take back to their departments, and how we continue the spirit of collaboration that was so palpable in the room. That’s going to have a huge impact on the work we all do over the coming year – and beyond – as we transform government together.

Follow Stephen on Twitter, and don't forget to sign up for email alerts.


Transcript 1: Transforming government together

Phil Mawson, Senior Developer, DWP:

The team I’m working on, they’re an absolutely amazing team, they’re so passionate. I mean, you’ll have seen that from the people you’ve talked to. The passion’s there and it’s all we’re focusing on just to get this thing live.

Souleymane Camara, Senior User Researcher, MOJ

You want to make a difference. Now, you’ve got to be careful about that, how much difference can you make, you know, being a small item in the bigger puzzle? But a little project you may have there could touch millions of people.

Liz Whitefield, Delivery Manager, DWP

It’ s all about public service, delivering things quickly, learning fast.

Jiten Pitamber, Agile Delivery Manager, MOJ:

Redesign the service from the paper form to guidance to the digital service, that’s the challenge. It’s changing culture, changing the way we work.

Kalbir Sohi, Digital Service Manager, HMRC:

We’re just scratching the surface of how good we could be, building simplicity into the services that people need to interact with.

Lauren Tombs, Deputy Product Owner, Office of the Public Guardian:

The staff, they can’t believe it, when they raise an issue or a good idea, they can actually see it being built and then released onto live in such a short amount of time.

Phil Mawson:

You feel like you’ve got the support there to be digital and to be agile and to be innovating all of the time because you’re not constrained by old processes.

Jiten Pitamber:

People want to be connected, people want that information.

Adrian Woodcock, Digital Product Owner, MOJ:

The bar is going to be set really high and we’re going to have to always deliver really good products.

Tom Harrop, Interaction Design Lead, Home Office:

People are starting to see that the way we do things, this user research thing that we do and this user centred design, is actually better.

Charlotte Moore, User Researcher, Home Office:

When you’ve got a team that believe it then we get to do really good, thorough user research so that we know the we’re building the best things.

Rachel Woods, Product Owner, DWP:

Working on policy in a digital environment, you’re getting much better feedback, it’s quicker, it’s from the right people.

Tom Harrop:

Everyone’s fighting for the same thing, everyone wants to do it properly. The real important person is the person who’s going to use this thing and making it easy for them.

Liz Whitefield:

For me there’s only one way to really experience it and that’s to get on the ground and see how it works.

Tom Harrop:

I don’t think we’ll ever be done transforming government, we just need to keep getting better at it.

Transcript 2: Sprint 16 - be bold

Stephen Foreshew-Cain, Executive Director, GDS:

I talked about being bold. Boldness is what's needed to keep the momentum that we have started in the last parliament going. We are a big organisation, four hundred thousand people, we are complicated and we do important stuff and when we don’t get that right people's lives are affected. So we have a duty to one another to make sure we are sharing our learning as and when it happens to make sure when we make a mistake it is safe to make and it doesn't get made again. So one of the things I think a lot about is people. We need talented people who can help us transform government and a day like sprint 16 reminds me how much we already have.

Transcript 3: Sprint 16 Highlights

Matt Hancock, Minister for the Cabinet Office:

Our job is to transform the relationship between the citizen and the state. It is about making sure that when people interact with the state they do it in a way that is as easy and straight forward as possible.

Stephen Foreshew-Cain, Executive Director, GDS:

Everyone in this room, I mean all of us, I mean we government, we’re going to go meet the needs of the citizens in this century and we’re going to do it by transforming government.

Amali de Alwis, CEO, Code First: Girls:

The role that all of us separately can play, so not to just work within sort of silos in whether it’s education, whether it’s local government, but to actually see how can we cross over the two sides, coordinate together to have programmes which actually work.

Paul Maltby, Director of Data, GDS:

Across departments we need to do the hard work to make data simple.

Jeni Tennison, Technical Director and Deputy CEO, Open Data Institute:

When you’re building on top of data you need to be able to rely on it, you need to be able to trust it.

Alison Daniels, Digital Transformation Leader, Foreign and Commonwealth Office:

The country register has those 195 countries and this is now the list, the canonical list that you can come to, know it’s produced by a trusted source and it is the latest, most up to date list.

Caron Alexander, Director of Digital Services, Department of Finance and Personnel NI:

Really it is about all having the same goal about making citizens’ services better and if we work collaboratively to do that really much better services at the other end.

Aaron Snow, Executive Director, 18F, US government:

I am tremendously gratified and thrilled to hear about the incredible transformations taking place here in the UK. We’re not out to transform services just to have shiny new services, what we really mean is we want to transform people’s lives.

Stephen Foreshew-Cain:

We have a real momentum behind us to make real change, we have the foundations in place to really transform government together.

Hosting codebar at GDS

$
0
0

We recently hosted our first codebar event in our offices at Aviation House, near Holborn.

Photo of students and coaches of Codebar working at the GDS offices in Aviation House, Holborn.

What codebar is all about

Codebar is a tutoring programme that helps women, LGBTQ, and people belonging to underrepresented ethnic groups in tech learn programming in a safe and collaborative environment and expand their career opportunities. Their work was recognised last year by a Points of Light Award delivered by the Prime Minister’s office.

During these weekly events, experienced developers volunteer their time to help students go through tutorials or build their own project. This help is invaluable.

My codebar journey

I learned coding from scratch a couple of years ago, and it is very much an emotional roller coaster - when you are able to build something, you feel so empowered, but there will also inevitably be times where you are stuck for hours and that can be quite discouraging if you are by yourself.

Going to a codebar event was my first experience of getting face to face help after going through online tutorials, and it made a world of difference having a real person there to answer my questions and give me tailored advice. It is also a great experience attending as a coach, which is what I do now. Explaining concepts that I have learned quite recently help me consolidate that knowledge, and it feels good to be able to give back when so many experienced developers are still helping me learn.

Our codebar event

No wonder codebar events always have a waiting list, whether you are a student or a coach. At our codebar at GDS event last month, nearly 50 people attended. After having some refreshments and a chat, they listened to a short talk I gave about my 20% project at GDS. Coaches and students were then paired up to go through tutorials or build projects over two hours in a variety of languages: HTML, CSS, Javascript, Ruby, and more.

We received good feedback and we will now be hosting codebar events every two months, with a larger capacity of 70 attendees.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

Writing content for everyone

$
0
0

I work as a content designer on the Digital Marketplace and for over a year now, I’ve also been working as a volunteer in adult literacy classes. I’ve been using my experiences in the classroom to help me write simpler, more accessible content.

Users with low literacy

Most of the students I work with fell out of a formal education system early. They face different challenges including dyslexia, poor vision and previously undiagnosed learning difficulties. Some of them have simply never found a learning environment that met their needs before.

The impact of not being able to read and write well means they can struggle to find work, organise accommodation, and get social support when they need it. They’re some of the people who depend on government services the most so understanding their needs is really important.

It can be hard to find the right service

It’s worth remembering the hoops people often have to jump through before they even come to use a service. It took me a long time to find a literacy lesson I could work in. I searched the internet, phoned local volunteering centres, looked at teaching courses, and eventually found a local college where I could help. I have a high level of literacy but people with lower literacy levels would have to be very motivated to find the same course.

Content designers need to remember that sometimes users have to do a lot of stressful work before they even reach their service. It’s our job to make sure that finding the service is as easy as possible. That means using words and phrases that users are likely to search for.

Confidence is fragile

It takes a lot to come to adult literacy lessons and ask for help so building up confidence is important. Asking a student to read content that’s written in long, complicated sentences can shake their confidence and make them quickly give up on a task. Users of government services are no different. Keeping content short, clear, and simple can help them use a service without getting discouraged.

Less is more

Sometimes content writers are asked to include as much detail as possible to make sure every angle has been covered. This can be a disaster for users with low literacy who can struggle to:

  • identify the main points in large blocks of text
  • concentrate on reading for long periods of time
  • retain the information they’re reading as they read it

You can help people of all literacy levels understand what they need to know by:

  • only including content that meets a specific user need
  • organising information into manageable chunks
  • using bullet points to break up long lists

Punctuation can slow people down

When people have to use a government service online, it’s unlikely to be the focal point of their day. Content designers must write for quick and easy reading.

We have to remember that it can be hard to read things like:

  • capital letters
  • contractions, eg ‘would’ve’
  • apostrophes

Readers with low literacy often don’t recognise the meaning of certain types of punctuation at a glance, eg an apostrophe showing possession. Even readers with higher literacy levels can find that reading words all in capitals slows them down. Using common words and simple sentence structures can have a big impact on reading speed.

Be direct

When people are concentrating on reading and understanding each word, there’s no room for subtle implications. If someone has to do something to use a service, you can’t hint at it, you have to tell them quickly and clearly. Using phrases like ‘you must’ can help users understand when there’s a step they have to follow.

Accessible and inclusive content

At GDS, we always try to design for the least experienced user so no one is excluded from understanding and using a service. We also try to apply the same principle to users with low literacy. By writing for all literacy levels, it means more people can use the government services they depend on.

Low literacy isn’t something that only affects a few people. Around 10% of the UK population has some degree of dyslexia according to the British Dyslexia Association. This means it’s likely that all government services have a number of dyslexic users. If a service wasn’t written with them in mind, it’s probably not meeting user needs. That’s why writing accessible, inclusive copy shouldn’t be an optional approach to writing content. It should be best practice.

Read the GOV.UK guidance on content design and how to write well for your audience. Find out more about adult literacy on the Literacy Trust and Reading Agency websites.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

Let's talk about service patterns

$
0
0

We’ve talked elsewhere about how to make and share service patterns, but now seems a good time to explain in more detail what they do and how important they are.

Service patterns are sets of practical guidelines for building a services (or bits of services) that are repeated across government - something like getting a licence or exchanging the ownership of something.

Right now, services like this are repeated hundreds of times across government in completely different ways, with completely different technology, policy and operational processes underpinning them.

Our theory is that by identifying and refining what good looks like for these types of service, it will make it quicker and easier to build better services that focus on users and easier to link these services across government to meet user needs. They’re one of the tools we’ll be using to make transforming services easier over the next five years.

We have rules for colour and fonts - we can have them for services too

We have established interaction and graphic design patterns for much of the user-facing aspects of government services. From the typography we use to the way we ask a user to complete a form, design patterns guide us.

These patterns help us to create a consistent, but not uniform experience of government. Service patterns are a way of extending this logic. By isolating processes within a service we can improve the way these component parts work and create a truly consistent experience of services across government.

They remove duplication of effort and improve interoperability between services and are crucially - generated from experience and iterated by the design community across government.

In the next five years, service patterns will become consistent standards for the way repeated activities should work, both for users and government.

Like other design patterns, service patterns can be isolated, tested, and iterated on.

A quick example: licences

Caseworkers at one of Defra's Environment Agency’s offices

Caseworkers at one of Defra's Environment Agency’s offices

In our Discovery with DEFRA, we found there were lots of services which fell under the category of licenses.

Though they had many different names - permits, exemptions, certificates, accreditations - and different purposes - registering the birth and death of cattle, movement of livestock, getting a fishing license - they all amounted to the same thing.

They were all licenses, of a sort. They all involved someone or something getting permission from the government to do something (or not do something). But each user journey was different, many were complicated and not user-centred. What became clear was that we could improve the way licenses were granted, and in doing so articulate a service pattern which could be used in other contexts.

The prototype: what we’re aiming for

We need a common format to present the pattern as practical guidance for service managers to build, run and improve services. This format will help us meet user needs at all stages. And having these at our disposal will make the build of services faster and easier.

Our theory is that by using the pattern we can:

  • remove the bulk of applications that aren’t eligible or necessary
  • and make it quicker and easier for users to get the right permission

This project - identifying existing processes and exploring how they may be optimised in a service pattern - is now in alpha. We are starting to prototype the licensing pattern by working with a team in DEFRA building a service.

Once we’ve tested it the licensing pattern will become practical guidelines on GOV.UK. Service patterns will help us make services cheaper, easier to make and more closely aligned to user needs. That’s why they’re important.

Join the conversation on Twitter, and don't forget to sign up for email alerts.


Guest post: building a digital standard for local government

$
0
0

Local government workshop

Phil works as the Digital Services Manager at West Berkshire Council. He’s also vice-chair of LocalGov Digital, a collaborative network started by local government officers Sarah Lay and Carl Haggerty.

LocalGov Digital do a number of things, including:

What local government is

Let’s take a step back as not everyone knows how local government is set up.

GDS has 24 ministerial departments and 331 other agencies and public bodies on GOV.UK. In local government, there are over 400 councils, each with many departments themselves meaning there are thousands across the country. You can begin to understand the enormity of the task for anyone trying to do what GDS did, in local government.

That said, a group of local government officers through LocalGov Digital are working to see how the Digital by Default Standard could be used in local government. This might seem like an impossible task, but we’ve had help.

With a little help from our friends

GDS speaker talking at the Digital by Default Assessment

On 5 February 2016 people from over 30 councils came to listen to speakers from GDS talk about the Digital by Default Assessment. They took part in workshops to see how the Digital by Default Standard might be used or adapted in local government.

We could have filled a room twice the size, and this is testament to both the reach of LocalGov Digital and to the high esteem that GDS is held in.

Work has taken place since and today we release the first public draft of the Local Government Digital Standard, for consultation.

Not the Digital by Default Standard

So why not just use the existing Digital by Default Standard? Some points aren't applicable to local government. For example, councils don't have ministers, so "test the service from beginning to end with the minister responsible for it" doesn't work in that form.

There's also nothing about re-use of authoritative data or registers in the Digital by Default Service Standard. This is something that will become increasingly relevant in the coming year and hopefully another area where local and central government can work together.

Transforming together

Local government visitors at GDS

I’d like to thank GDS for their help so far. If you care about how local services are delivered please get involved by viewing the Standard. We want your help to deliver, not a business case or a nudge in the right direction, but the first Local Government Digital Service Standard for councils.

This is particularly important if you are elected to, or work for a council. To make this happen it needs advocates embedded in local government as well as assistance from outside. The more of us there are, the stronger it will be, which can only be a good thing for the people we all serve.

Join the conversation on Twitter and don't forget to sign up for email alerts

GDS and gender diversity at conferences and events

$
0
0

Equality and diversity matters a lot to me, and to everyone here at GDS. I wrote about it a couple of weeks ago in my role as Cabinet Office LGB&TI Champion:

Making the department one of the most inclusive and diverse organisations in government is something I care passionately about.

There is a gender diversity problem in the digital industry. There are still many more men employed in it than there are women, a problem that's made (and looks) even worse at the conferences and events we host and attend. Too often, the speakers on stage at those events are mostly, sometimes even entirely, male. That has to change.

Taking action

Photo of a woman giving a talk in front of an audience. Slide on the screen reads "Transparent and collaborative". Audience look engaged, and speaker is gesticulating.

Today is International Women's Day, and I'm committing, in public, to the first of several actions that GDS is going to take to help improve gender diversity.

So. In future, no-one from GDS will take part in a panel discussion of two or more people unless there is at least one woman on the panel, not including the chair. (Yes, that comes from Owen Barder's Pledge).

In future, no-one from GDS will speak at an event unless the event's organisers are clearly working hard to address gender diversity on stage. It's hard to put a number on this sort of thing, so we will make that decision based on what we see on each event's draft agenda.

We'll hold ourselves to the same standards where GDS is the host, for internal events and public ones too.

Ideally, when GDS is invited to supply a guest speaker for an event, we’d like to send women to speak just as often as we send men. That means that sometimes, some of our male staff (especially those on our management team) will be encouraged to step aside and suggest a female colleague to speak instead of them. There are plenty of women at GDS who are excellent speakers and experts in their field - but the opportunities to speak need to be present for them.

Our Sprint 16 event in February had some women as speakers and panel members on the main stage, as well as leaders of break-out sessions and discussions. But not enough. We want to do better. The theme of the day was “Transforming government together,” and that’s impossible without meaningful diversity. (Not just gender diversity, but also diversity of ethnicity, age, ability, sexual orientation and more. There’s work to be done in all those areas. We won’t ignore them.)

For our next big event - whether it's Sprint 17 or something else - we aim to have an even gender split, 50-50.

Our new GDS advisory board, announced by the minister at Sprint 16, is evenly split like that from the start. A sign of how we want things to be, and how they will be.

This is not tokenism. This is important. This is us doing our bit, and taking action.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

Digital principles for a better GDS

$
0
0

Photo of GDS team listening to an impromptu talk in the Aviation House offices. Bunting, macbooks, signage.

GDS is approaching its fifth birthday. It’s grown from a small organisation that delivered the prototype of GOV.UK in 12 weeks to one with responsibility for a number of transformation programmes, services, and standards. And it will continue to grow through the £450m investment government is making to help departments transform government.

Growth will always bring issues as organisations try to scale in a sustainable way, particularly when an organisation grows at the rate we have. Even without rapid growth, any large organisation will have issues and things it needs to improve. What’s important is that running any organisation shouldn’t be any different from building and running great public services. You always start with user needs, and then iterate, and iterate again.

How we’re improving

We’re aiming to bring together how we apply a digital way of thinking and our own design principles to make GDS a better place to work. The People Board have already taken the data from our most recent Civil Service People Survey and ran a number of workshops and one on one conversations to prioritise the areas for improvement.

These include:

  • making it easier to know who does what, so work has clear ownership and it’s clearer how to get things done
  • improving performance management so it provides an opportunity for feedback on progress towards personal development goals
  • developing a stronger career offer, making it easier for individuals to develop within the organisation through visibility and fair access to different roles

This is in addition to some other changes we’re currently testing., For example, we’re expanding the role communities of practice have within the organisation and delegating more responsibility and operational decisions to teams.

We want GDS to be a great place to work and an exemplar organisation for the rest of the Civil Service. We’re not there yet but I hope that by sharing our learning (and mistakes) we’ll help other parts of the Civil Service improve too.

Join the conversation on Twitter and don't forget to sign up for email alerts.

Getting from data to registers

$
0
0

Registers poster featuring list of characteristics available here: https://gds.blog.gov.uk/2015/10/13/the-characteristics-of-a-register/

There is plenty of value in individual registers as authoritative sources of trustworthy core reference data - the first beta register, the country register, is being used by services such as the e-petition service already. Over time the country register will also replace many of the country lists published on GOV.UK. So individual registers are good but an ecosystem of linked registers is even better. That’s why every register needs to be designed with the wider ecosystem in mind.

The Register Design Authority

And that’s the focus of the Register Design Authority, which sits in the GDS data group - making sure that registers accurately and helpfully reflect the interconnectedness of government data.

This team has domain control for the register.gov.uk domain. It will work with the register custodians who are responsible for running registers and are the domain experts, to ensure that the data in their registers is modelled in ways that meet users’ needs, and work with other registers in the government data ecosystem.

This is how we will avoid unhelpful and confusing replication of data and ensure that registers really are trustworthy.

The process for determining which registers get built

There are a number of factors the Register Design Authority team considers when it comes to the creation of a register. These considerations have implications for the modelling of the data within registers and the way the registers are run. Only once these conditions have been met can the register begin operating on the register.gov.uk domain.

One of the things the Register Design Authority team thinks about is where a new register would sit within the linked ecosystem of registers. By definition, data in canonical registers isn’t replicated elsewhere. For example, we shouldn’t have more than one country register. Having a single register means establishing agreement and saves services having to decide which list to use. So given there’s already a country register, the register design authority won’t support the creation of another “nation” register on register.gov.uk, unless that proved to be a different concept.

Another thing the team looks at is whether the register data constitutes a ‘minimum viable dataset’ - one of the characteristics of registers. This isn’t just because it makes for cleaner, more modular structuring of data, but also because it makes it easier to align the operation of registers with the underlying processes for data collection and maintenance.

We want registers to work across government, and not just for a single service or organisation. That’s why the team needs to spend time working with the custodian and services, to ensure that the data in the register can be kept as accurate and as up to date as possible. Users need to be confident about these things and have the appropriate access tools, for the data held in registers to be considered good enough to build services.

When there is a conflict over which part of government should be the source of data for a register, the team looks at who can provide regular, accurate data, that allows for the ongoing feedback loops that are a characteristic of registers. If it’s still not obvious who is best placed to be run a register, we will escalate this decision to the Data Leaders Network for review.

Standards help build trust

One of the most important aspects of registers is that they provide data that’s good enough to build services on. We build trust in registers both by having clear technical specifications and clear processes for how and why they’re built. Registers are long-lived, so an important part of the specification is consideration of how the API and data can change over time without breaking services, and to enable feedback loops from services to ensure the data in a register is accurate, and kept up to date.

In an earlier blog post we were clear that building the foundation of the government’s data infrastructure is a work in progress, that is still the case. These standards will evolve, as good standards do, as more registers come online and we learn from custodians, data users and ongoing development of the Registers platform.

You provided us with helpful feedback following the beta release of the country register at SPRINT 16 and we’d like to hear your thoughts on the approach we’ve outlined here and the draft specifications we’ve linked to. We want this to be part of the way we transform government together and we’d like your help.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

An open address register

$
0
0
Image of a row of houses
Licence: Creative Commons Attribution Sludge G

The UK government is regularly recognised for being a global leader in making public data openly available. Ministers have committed to being the most transparent government ever. We are determined to make sure that we keep producing high quality data and that we make it as accessible as possible.

What the Budget said

Last week’s Budget contained the following commitment:

The government will provide up to £5 million to develop options for an authoritative address register that is open and freely available. Making wider use of more precise address data and ensuring it is frequently updated will unlock opportunities for innovation.

Building the UK’s data infrastructure

This supports work that is already underway, across government, to improve how data is used. Data has become a part of our core national infrastructure, and a huge driver of innovation. Countries where businesses and public services have reliable access to trusted data reap similar benefits to countries that led the world with access to transport, water and sewage infrastructure in previous centuries.

Registers, canonical lists of core reference data, are at the forefront of the government’s effort. They enable a standardised way of storing and accessing data, independently of the technology platforms and digital services that use them. Government’s expectation is that over time they will form the basis of government’s data infrastructure, helping people put government data to work.

Making geospatial data even more usable

Nearly everything that happens has a link to a physical location. Address data serves a broader purpose than the delivery of post, parcels and services. It anchors everything to a specific place, and it’s often this anchor that’s used to connect other types of data together. So for a modern economy, high-quality geospatial data, linked to the addresses that people use on a day to day basis, is incredibly important.

The Budget announcement is an exciting government commitment to explore how an open address register can enable innovation, meet user needs, and deliver substantial and tangible benefits to the public and the economy by enabling new products and services.

Work ahead

GDS Data Group and the Department for Business, Innovation and Skills (BIS) are working in conjunction with a range of other stakeholders to explore how to fully exploit the benefits of open and freely available address data.

We know that we have a lot of work to do, and a lot of people to engage, as we move forward. We are aware of the fundamental role played by local authorities in the creation and maintenance of addresses, and the important contributions of Geoplace, Ordnance Survey and Royal Mail. We look forward to continuing these conversations over the coming months.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

An open letter to our new Advisory Board

$
0
0

Dear Advisory Board members,

In the spirit of publish, don’t send (“A good blog post can do the work of dozens of emails”), we thought we’d write to you here before our first meeting next month. Some of you have been with us from the beginning, others will be less familiar with our work.

For all of you, here’s a very brief summary of what we’re doing, and how we’re doing it.

GDS is part of the Cabinet Office. We’re here to make sure that the internet is as much a part of the fabric of government as it is a part of people’s lives. Our goal is government that understands and embraces the digital age.

We've asked you to help us because you believe in the same things that we believe. We summarise those things in our Design Principles. We are agile. We put users first.

Our first few years were about disruption. Our strategy was delivery: we had to prove that things could be done by actually doing some of them. We had to show what was possible. That government could use the digital thinking to redesign and rebuild public services to be simpler, clearer and faster.

Now we’ve started a new phase - teams all over government are working together on digital services, platforms, standards and everything behind the scenes that brings them all together. It’s not about computers and IT - it’s about people, skills, and how we work. It’s about organisational change.

Our new focus is transforming government together. We recognise that we cannot do all the work of transformation by ourselves, and we don’t intend to try. We need help from departmental teams, just as much as they need help from us. It's a mutually beneficial, two-way relationship.

We have amazing support from our minister Matt Hancock, and in the last spending review we were granted a budget of £450 million. We’re growing, and we’ll be helping government to grow too. Not just in terms of numbers of people, but in terms of the digital skills and expertise they bring.

We've invited you to join our Advisory Board because we value your collective experience and wisdom. We’ll be turning to you for advice, guidance and honest feedback in the years ahead.

Thank you for agreeing to help us. We can't wait to start working with you. See you on the 11 April 2016.

Stephen Foreshew-Cain

Building the service manager community

$
0
0

Eddie Davies is a service manager at Land Registry. Today he shares the experiences of the first cross-government service manager community meeting.

Last week around 40 service managers and colleagues from Government Digital Service (GDS) met at the Land Registry for the first cross-government service manager community meeting.

Service Managers community meeting

What service managers discuss when we get together

The day began with me sharing my experiences of the Service Standard assessment that I'd been to the day before. I talked about some of the successes and challenges my teams faced in developing new services. I also spoke about the need for service managers to engage more with each other and form a community.

Ben Welby, service manager for Government as a Platform services spoke next, updating the group on progress including payments and notifications.

What we wanted to achieve

When arranging the day I said I wanted 3 things to come from it:

  1. To debate some of the key issues slowing down digital delivery within government from a service manager point of view.
  2. Develop a community feel to the group and seek to re-run the meetings every quarter.
  3. Capture 3 things on each topic debated which we can share on a blog for others to relate with and act as a reference point for future meetings.

Following a vote the first 3 hot topics to debate were:

  • internal and external spend approval processes
  • the role of the service manager
  • digital delivery models

Spend approval process

The group debating this issue agreed that our approval processes should be smooth, streamlined and add value, rather than being seen as a blocker. This didn’t appear to be where we are currently, so we plan to review and revise the current process.

One idea from the group was to bundle assessment and approval together, meaning pass the assessment and you get approval to advance for the next 12 months. It would mean someone from approvals sitting on the assessment board – we didn’t see this as being too arduous. GDS are undertaking a discovery into the service assessment process and will consider this as part of that work.

Role of the service manager

The nature of the service manager role will depend upon a number of factors eg size/impact of service, volume of services managed. One challenge that was identified in this discussion was the end to end ownership of online and offline services.

This was a common challenge for many service managers and an area that will be considered again in future meetings. One thing the group did agree was, leaving banding and grading aside, we should agree on core accountabilities as a community we see as being fundamental to the role of a service manager.

Digital delivery models

Many departments have embraced agile ways of working in their digital delivery, but challenges are still met. Some departments are more mature and better resourced to support agile delivery than others. Sharing good practice was one of the main opportunities identified here. The distinction between ‘being’ agile rather than ‘doing’ agile was also highlighted.

Another interesting discussion was to do with the different challenges between co-location and working in multiple sites. An alternative to these ways of working was mentioned including the concept of no-location where a base location is not defined. This would open it up to all and encourage the use of digital collaboration tools in cultures that need encouragement or additional support to use new technologies.

After lunch, 3 more sessions were held discussing the next hot topics:

Continuous improvement

A common problem was balancing the need for continuous improvement of services after they are live, against other competing priorities.

A number of departments are able to keep a small team for iterating improvements, but for many the need to move to the next big thing means that investment in continuous improvement is less than service managers would like. Another one to discuss next time.

Beta vs live

The group questioned whether the bar was set too high and if improvements are needed. The view in the room was many had not successfully passed beta first time, possibly pointing to the fact we are all just still learning (maybe); or that the bar is too high and public beta really means live (possibly).

Building a community

Visibility and collaboration is essential for this to happen. An interesting idea from this group was that every community meeting should focus on solutions to problems identified in the previous meeting.

When the sessions were complete Steve Railton, transformation lead at GDS, ran a final session. Steve invited service managers to tell him what they wanted from GDS.

The main themes to emerge were support, guidance, and expertise, collaboration, help with assessments and controls and clarity around how GDS is structured and where to go for support. Steve will feed these points back into GDS to be actioned.

Looking back on the session

Overall, the event went well and can be built on to develop a strong service manager community. It was clear that many service managers find themselves with similar challenges.

This event gave us the opportunity to share good practice and get advice from others doing the same thing. Also, learning from their mistakes can prove really useful.

It was great to see everyone getting involved in the discussions. We were all open, inclusive, and honest. Which I guess made for a great day and positive atmosphere.

The important issues, and, therefore, those that offer the greatest opportunities, remain:

  • approvals
  • assessment criteria
  • managing continuous improvement and service delivery
  • effective delivery models
  • developing communities

We’re already looking forward to the next service manager meeting soon.

Join the conversation on Twitter, and don’t forget to sign up for email alerts.


Guest post: looking at the different ways to test content

$
0
0

Today we hear from two content experts sharing their thoughts about testing content. Christine works with GDS as a trainer, and is a content strategist. Emileigh is a lead content designer and strategist working at 18F in the USA.

They met for the first time on a sweltering summer day in Washington, DC. A quick cup of (iced) coffee turned into a months-long, transatlantic conversation on the different ways writers can test online content to see whether it needs improving.


Much like Supreme Court Justice Potter Stewart’s famous saying, we know good content when we see it.

Good web content is clear. It’s actionable. Readers find what they’re looking for — and they’re looking for a lot these days. People rely on websites to conduct research, fill out tax forms, read the news. We know good content when we see it, and we’re frustrated when we don’t.

Keeping this in mind, are there ways that writers can quantify and measure their writing? We’ve looked at different tests you can run depending on the age of your audience. Finding appropriate ways to test our content helps us improve and find best practice patterns for creating copy.

Hand-drawn diagram on graph paper. Graph shows a set of axis reading Comprehension (north); Success (east); Confusion (south); Failure (west). Star is located equidistant between comprehension and success.

Christine’s graph of good content. The star marks the sweet spot.

Who you are writing for

Readers will come to your content with varying levels of existing knowledge and different educational backgrounds. This has a huge impact on how you create content. Tell knowledgeable users what they know and you’ll bore them. Assume they know more than they do and you’ll frustrate or even lose them.

Here’s a good rule: if you’d like to reach a broad range of users, you should strive to write at a middle-school level. A 2003 Department of Education assessment showed ‘average’ Americans read at a seventh/eighth grade level, and in the UK it’s been reported that the average reading age is 9 years old (15 would be the maximum).

Whenever possible, keep things simple, short, and clear.

Testing your content depends on your audience

When it comes to seeing if the content you’ve written is working, the way you test it will depend on who you’ve written it for. We need to pay particular attention to how we frame the exercise, because of the stress associated with taking a ‘test’. It’s the content that’s being tested, of course, not the person, but this distinction needs to be made clear.

Open-ended questions

Asking open-ended questions such as “What does this mean to you?” is helpful when you’re creating content for people with different cognitive needs. Maybe they have learning difficulties or aren’t familiar with the language. On GOV.UK we might look to ask open-ended questions to those using the PIP checker or who want to apply for a visa to see how much they understand.

If you’re writing content for children, using open-ended questions is a good way to see if they understand the information.

In 2015, Emileigh led the content strategy for Every Kid in a Park, the website for a Barack Obama initiative to let all US fourth graders and their families visit national parks for free.

Using open-ended and task-orientated content questions allowed me to keep pressure low and still measure how well kids understood the programme and their overall enthusiasm for the site. For example, “How would you use this website to sign up for Every Kid in a Park?”

Let people choose their own words

When you let people tell you how they feel in their own words, you can use the same language in the copy, thereby letting your audience have a direct influence on the content. This technique can be used on sensitive content such as dealing with health, relationship breakdown or loss. For example, GOV.UK has content on what to do after someone dies, not after someone ‘passes away’.

Christine recently worked on an app that helps young people in care prepare for meetings. They can also use it to help them talk about their feelings, for example to a social worker.

In the app, young people can choose the feelings that they’re experiencing, plus add their own if they want. We wanted to test whether the feelings we’d chosen were representative and appropriate.

In testing, target users were asked to list all the feelings they’d experienced in the previous two weeks. We then matched these to the ones we had in the app, plus the feelings people had written into the ‘add your own’ field.

Screen shot of the app showing the option to choose "how you feel right now". Choices include 'unsure', 'ok', 'excited', 'angry' etc. There's also the option to add your own by typing it into the app.

By letting users identify their own words we could see if the assumptions we’d made about people’s state of mind were accurate or not.

A/B testing

This kind of testing compares two versions of content to see which performs better. It’s also a good way to test how users connect with your content. Maybe your site is easy to read and understand, but users aren’t interacting with it in the way you hoped.

The organ donation sign-up case study shows how A/B testing works. Because this message appears after booking a driving test, we know users will be over 17 years old.

The National Health Service (NHS) wrote eight variations of content asking users to sign up as organ donors. For example:

Please join the NHS Organ Donor Register.
Please join the NHS Organ Donor Register. Three people die every day because there are not enough organ donors.
Please join the NHS Organ Donor Register. You could save or transform up to 9 lives as an organ donor.

The sign-up rate for each piece of content was measured and the most successful was:

Screenshot of the successful organ donation page. Reads "Thank you. Please join the NHS Organ Donation Register. If you needed an organ donation, would you have one? If so please help others".

Each content variant the NHS tested was plain language and are easily understood. The A/B test showed which call to action was most effective (though not why).

Cloze testing

For content about sensible subjects such as finance, regulation and health, the Cloze test is ideal to help measure your readers’ understanding.

In the Cloze test, participants look at a selection of text with certain words removed. Then they fill in the blanks. When creating a test, you can delete words using a formula (every fifth word), or you can delete selectively (key words). You can accept only exact answers, or you can accept synonyms. Sample as many readers as possible for greater accuracy.

When developing Cloze tests for betaFEC — the US Federal Election Commission’s new web presence — Emileigh selected passages of at least 150 words, deleted every fifth word, and accepted synonyms as answers. The target was 50% or greater accuracy; in practice, FEC’s Cloze test scores ranged from 65% to 98%.

Screen Shot of the Getting a tax ID and bank account page on the US Federal Election Commission’s website.

Preference testing

Christopher Trudeau, professor at Thomas M. Cooley Law School in Michigan, did research into legal communication to find out ‘to what degree do clients and potential clients prefer plain language over traditional legal language’.

He found that the more complex the issue, the greater the reader’s preference if for plain English and that the more educated the person, the more specialist their knowledge, the greater their preference is for plain English.

He employed a range of ways to test content for his research, including A/B testing and asking respondents:

“Would you prefer this or this version”

then following up with:

“Why / why not?”

He then asked longer, qualitative question series eg:

“Have you ever read a document that was difficult to understand?”

“Did you persevere?”

“Why did you stop reading it?”

He named the method of using a mixture of A/B then qualitative questions ‘preference testing’.

For checking whether people understand risks (in informed consent cases) he says the best way to check comprehension is for the person who has read the document to be asked follow-up questions, eg: “Based on what you read in the document, can you explain the main risks to me ...”

This means a real person - not a computer - uses their judgment to assess whether they understood the content.

Measuring what you’ve written

Over time, organisations have developed reading scores and indexes for measuring the ‘readability’ of content. For example, the Coleman-Liau index, the SMOG index, and the Gunning fog index.

One that we find consistently suits our needs is the Flesch-Kincaid grade level. Developed for the US Navy, Flesch-Kincaid measures sentence and word length. The more words in a sentence (and the more syllables in those words), the higher the grade level.

Using these formulas will help you quickly estimate how difficult your text is. It’s a clear metric that can help you advocate for plain language. But, like every formula, Flesch-Kincaid misses the magic and unpredictable nature of human interaction.

They also can’t help you figure out that “Patience you must have my young padawan,” is harder to read than “You must have patience, my young padawan.”

Close up of Yoda (Star Wars)

The only difference between standard English and 'Yodish' is the word order; but this change can make it harder to understand.

Licence: Creative Commons Attribution Angelo Yap

We’d love to hear about your ways of testing content and comprehension.

Follow Christine on Twitter, Emileigh on Twitter, and don’t forget to sign up for email alerts.


Further reading

Our user research team put together tips for testing your words when doing research.

Giving clear presentations

$
0
0

Like ‘bunting in the office’ and ‘cake on release days’, ‘slides with big words’ has become one of GDS’s hallmarks. A few weeks on from Sprint 16 I wanted to write about why we encourage that.

Applause slide

Our slides are very simple

Presentation software, like most software, gets used in lots of different ways. That’s normally fine – if you want to use slides to do wireframes then go for it – but it’s a problem when someone’s used presentation software to make, say, an organogram and then gets up to present it without changing a thing.

We’ve all sat through the presentation that ought to be a table emailed to the finance team. Or been shown the complex user journey that ought to be printed out on a wall. Or asked to approve copy on a slide that should, instead, have been emailed. It’s tedious. So we’ve deliberately constructed a template that forces the writer to think of the presentation as a thing they’ll be presenting.

The typical GDS slide is designed to;

  • be easy to read (even at the back of a large room, or on a small screen)
  • keep the emphasis on the speaker
  • force the writer to be extremely clear about what they’re saying

Our ‘normal’ slide is designed to support a single short line of text. Our ‘heading slide’ is designed for even fewer words. We try to make sure our images illustrate the point the speaker is making. We enforce a strict ‘no metaphors’ policy. And, wherever possible, we encourage speakers to use screenshots or demos so they actually show the services or tools they’re talking about.

On the whole, it’s a pretty simple setup.

Clarity comes with preparation

A very plain template gets you about a third of the way. The rest comes with preparation. If you use the template but don’t prepare then it’ll be very obvious that you haven’t given much thought to what you’re saying. You have to put the work in.

The three things you should be asking yourself as you prepare are:

  1. What is the main point I want to make?
  2. What else does this particular audience need to know to understand that point?
  3. What is the best order for those things?

As you ask those questions your answers will start to change. You might realise your audience knows more than you thought initially, so you need to make a different point. Or you’ll see a different order emerge as you rehearse it. Like anything else, iteration will get you where you’re going. Iteration, and deleting things.

Russell Davies used to tell people that each minute onstage should equal about an hour or preparation. It’s a good rule of thumb. (He also wrote a great series of blog posts about preparing talks that’s worth reading).

Oh, and rehearse. Loads. Giles Turnbull wrote a nice thing about that on his own blog a few weeks ago.

Slides aren’t your only tool

You don’t have to rely on a presentation alone to get the job done. Need people to approve some text? Send it before or after the meeting. Need to share a chart in a meeting? Email it round or print it out (and use a placeholder slide to prompt people to look at it). Got a big diagram you want to walk people through? Print it out really big and literally walk people through it. It's ok to point to things on the internet too, as long as you use short URLs they can copy from slides quickly, or take a picture of.

We’re not the only bit of government that works like this; DVLA digital, MoJ and much of Cabinet Office use similarly plain slides and often have similar ‘rules’ about what people should include in presentations.

The end results might look extremely plain, but the slides are clear and, more often than not, gel together into a cohesive argument.

Join the conversation on Twitter, and don't forget to sign up for email alerts.

Where we’re at, and where we’re going

$
0
0

Matt Hancock at Sprint 16 on stage - screen reads "the journey ahead".

Back in February, our Minister Matt Hancock launched the Sprint 16 event with this message: "We're transforming the relationship between citizen and state."

That's the goal. GDS exists to help make that happen. Our job is digital transformation of government, and now feels like a good time to outline how we are going to do that.

The message I told Sprint 16 attendees on the day, and I've been telling other people since, is by working together. Transforming government, together. Our future is not about GDS doing things to departments, but doing things with departments, and helping departments to do things with one another.

How we got here

For our first four years or so, the strategy was simple: delivery.

We had to deliver, because decades of inaction and inertia in government had shown that starting with piles of paper and years-long IT contracts doesn’t work. Instead, we had to actually change things, and show how that change could be done well.

So we started with the GOV.UK alpha, which became the GOV.UK beta, which became GOV.UK.

We brought in the Identity Assurance Programme, which became GOV.UK Verify.

And we took on what used to be G-Cloud, transforming it into the much larger and more ambitious Digital Marketplace, which has already reached £1bn of sales.

We showed colleagues in government and beyond what was possible by putting users first, and being agile.

We learned a huge amount, changed the approach as we learned, iterated the build, and moved on.

What we learned

We learned that 19th century organisational models and 20th century technology were serious constraints to 21st century service demands.

We learned that transforming separate, siloed services one-by-one will never be good enough, or fast enough.

We learned that government needs to rethink how it works, and what sort of people it employs.

And we learned that in order to make this big change - to transform the relationship between citizen and state - we need to collaborate. Everyone in government needs to work together.

Government has been ruled by silos for too long. Not just organisational silos, not even just technical ones, but silos of knowledge and experience that make service delivery more difficult than it should be.

Three strategic themes

So what does all that mean for our work over the next few years? People ask me: "What's the GDS vision, Steve?"

The short answer to that is: we want to help departments work together to transform government to meet user needs.

There are three themes underpinning that. They are:

  • standards and assurance
  • shared resources
  • people and capability

Standards and assurance is about defining, and collectively agreeing, what good looks like. We intend to provide standards, policy, support, and guidance so that services and technology work effectively and consistently for the public and government.

We’re where the buck stops. For the common good, we'll be holding the rest of government to account for building things that meet those standards. That means holding ourselves to account too: we have a responsibility to do that, particularly where we are building the shared digital infrastructure the rest of government relies on.

Shared resources: this is government as a platform in action. We'll help departments identify the things that can be shared components, part of an interconnected ecosystem that they can use to quickly assemble services. Build once. Build well. Use everywhere.

The list of components is long and going to grow much longer. Things like Verify, the Marketplace, all the new up-and-coming platforms like Pay and Notify, the data registers, emerging design patterns — all of them are part of the ecosystem.

Finally, people and capability. Too often overlooked.

Doing all this work (developing standards, building shared resources) means that civil service must attract, develop and keep people who have the right skills.

We need to make it easier to get them in, by simplifying recruitment; and we need to motivate them to stay, by developing more flexible career paths and structures, and building the digital, data and technology profession within the civil service. It will be a valuable and powerful way of sharing skills and knowledge, and of maintaining some degree of institutional memory.

It’s not about computers

The important thing that's changing here isn't the IT, it's the people. It's us.

Ultimately, this is organisational change on a huge scale. In the longer term, it has potential to radically alter the structure of government -- not just the services it provides, not just the way it builds and maintains them, but the way it operates itself. Civil servants don’t often talk about upending the status quo, but I think we’d be fools to ignore what digital transformation really means, or to pretend that huge change isn’t inevitable. It is. It’s our job to manage how it happens. We’re not the only ones treading this path: look at what’s happening in Greater Manchester right now. There’s so much that everyone on that path can learn from everyone else, but only if we share the same values and the same collaborative spirit.

People are the catalyst for change. "The unit of delivery is the team," as we've said for years now. The team I'm talking about here isn't GDS, it's all of government. It's the suppliers we deal with too. Transforming government, together.

Change is hard

Overcoming fear of change - transforming government so that it embraces the change, rather than trying to avoid it - is the biggest challenge we face.

We collaborate because people need reassurance. They need that support. They need to know that someone’s got their back when things go wrong. That’s what we’re here for.

I said at Sprint 16: "We've got your back."

I realised afterwards that the reverse is true: everyone else, all the departments and suppliers we deal with every day -- they've got our back too.

They understand their users and services better than we ever will.

They know the policy, the intent of that policy, and the legislation that sits behind it.

They know their users better than anyone. They are by far the best people to meet those user needs.

It’s a mutually beneficial, two-way relationship.

Here's what it looks like

Screen shot of Country Register

If you want an example of what transforming government together actually looks like, let me point you to the Country Register, announced by Alison Daniels from the FCO at Sprint 16.

To the casual observer, it doesn't look like much. But it's a big deal. It's the official, canonical UK list of countries, maintained and overseen by the Foreign & Commonwealth Office - the FCO's Tony Worron is the named registrar.

The Register Design Authority worked with Tony and Alison and others from FCO to get this register built, and built to the right standard. The register platform is a shared resource for government, and the FCO team used it to create a register, a new part of a wider ecosystem that everyone in government can benefit from.

The Country Register makes it easier for other government teams to build and run their services - the Petitions service is already doing this. It's one of those interconnected components, one small part of the ecosystem. It's one small step on the path towards transforming the relationship between citizen and state. One of the first steps of many, many more to come.

Follow Stephen on Twitter, and don't forget to sign up for email alerts.

What we mean by service design

$
0
0

Poster on a door - "I want to fish: digital service" - blurred office scene in background

Our aim over this parliament is to transform the relationship between the citizen and state: to transform government, together. Service design is a big part of how we plan to do that, so it seemed timely to give a short outline on what we mean by it.

What we mean by service design

First, let’s be clear - service design is the design of services.

To a user, a service is simple. It’s something that helps them to do something - like learn to drive, buy a house, or become a childminder.

However, search online for service design right now and you’ll find a seemingly endless array of ‘toolkits’ and ‘design processes’. Five circled grids. Double diamonds. Mental models. You’d be forgiven for thinking that it was about the process of design, rather than changing outcomes for users.

This is changing though. Service design is moving inside organisations, and inside government. For us, service design isn’t about mental models or double diamonds. It’s about working with users and delivering services.

Redesigning services in government is difficult

Government is the UK’s oldest and largest service provider - providing services is our main function. Just as if your business was making chairs, you’d hire a furniture designer - government needs service designers to design services.

With that history, comes challenges. Government services are sometimes split into tiny pieces: lots of isolated transactions, products, and content provided by different parts of government that need to be used together by a user to achieve their goal.

Service design is the activity of working out which of these pieces need to fit together, asking how well they meet user needs, and rebuilding them from the ground up so that they do.

It’s not complicated, but it is hard.

There’s lots to be done

Government delivers a lot of services - it’s what accounts for the majority of our spending.

If these services aren’t immediately understandable and easy to use it can confuse users and lead to mistakes being made. This increases casework and phone calls for government - and the amount of time spent by users trying to fix their problem. All of this costs money.

Basically, bad services are expensive and require more time investment from the point of the user. This has a knock-on impact on user’s ability to do to other things and the economy itself.

The other unwanted consequence of bad service design is that we neither meet a policy intent or a user need.

That’s why we’re interested in service design.

Common problems

Unfortunately, the operational needs of government often overshadow the needs of the end user. It’s not surprising - operating government services in a digital age is hard work. Especially given that the way our services work largely has its origins prior to the adoption of the internet, and in some cases computerisation.

But just because something's hard, doesn’t mean it can’t be done.

Good services should reflect what the user wants to do and don’t require a working knowledge of the inside of government to use. As I’ve written before: good services are verbs, bad services are nouns.

Quite often that means interacting with more than one part of government to get something done, meaning that users have to act as go-between, working out how multiple licences, forms or regulations relate to their needs and sequencing them appropriately into a ‘service’ on their own.

How we work

Digital capability in government has grown beyond all recognition in the recent years.

Alongside other important digital, data, and technology skills, there are now over 300 designers in government - a mixture of service designers, interaction designers, and graphic designers.

Service design is a relatively new addition to this. I was one of the first back in 2014 and since then we’ve developed a new generation of service designers who’re moving inside government to get close to hard problems and design solutions to fix them at scale.

We work fast and we make things in code - not wireframes or diagrams. We test our assumptions through research. It’s the results that matter - better services.

Given the vast, defracted nature of pre-internet services - the job of a service designer in government is 90% archeology - finding out which transactions are involved in which user need, what their original purpose was and whether they’re still effective at doing that.

The next 10% is a lot harder - stitching them together into a coherent service that a user can use unaided.

The work of government service designers is informed - and often driven by - digital but we don’t exclusively work building websites or digital things. Some of the biggest challenges in service design are in the transitions between physical, offline, and digital transactions.

We design whole services:

  • from end-to-end: this means from when the user starts trying to achieve a goal to when they finish - including both content and transaction agnostic to the department providing it
  • from front to back: this means the user-facing service, internal processes, supporting policy or legislation and organisational, financial and governance structures of the service
  • in every channel: digital, phone, post, face to face and physical elements

How we’re scaling up

With so many services, our biggest challenge is how we scale.

Just as we’ve used interaction design patterns to speed up how we deliver online services, we’re now starting to develop service patterns. These are ways of identifying and standardising commonly-used transactions, so that when teams are building a service they can reach for off-the-shelf solutions to common problems and save their energies for focussing on difficult, unique problems.

But we can only get there together. At GDS we’re working with the rest of government to formalise the design profession to do that. We need more designers in government, and more friends and allies for them to work with at the very top of our organisations.

I’ll talk more about this in another post.

Follow #ServiceDesign this week

We’re talking about #ServiceDesign on social media for the week, sharing lots of new videos, case studies, images and blog posts.

Join our live Periscope Q&A where I'll be talking about service design in government and taking your questions. It's on Thursday 21 April at 11.30am. See you there.

Thank you Liam

$
0
0

Liam Maxwell

As some of you may have already heard, we’re delighted to announce that Liam Maxwell has been appointed as National Technology Advisor. It’s a new role, and a great next step for Liam after four years as Chief Technology Officer.

Needless to say, we shall be sad to see him leave GDS; but we’re pleased that he’s staying in government.

In his new job, Liam will be in charge of coordinating various strands of technology policy across the Department for Culture, Media, and Sport (DCMS) and Cabinet Office. He’ll be promoting and supporting digital industry in the UK and internationally.

It’s all part of the spreading the digital revolution across Whitehall.

We're extremely proud of everything Liam's achieved at GDS. Among many other things, he:

What this means for GDS

Liam will make the transition to his new role over the coming weeks. He’s leaving behind an excellent and highly skilled team. Andy Beale will take over Liam’s responsibilities as Acting CTO pending a competition for the role. Alongside him Iain Patterson will continue to lead the Common Technology Services programme. Andy and Iain will report to me and join the Executive Management Committee. The senior leadership of the Technology Group remains in place, with Olivia Neal overseeing the Standards and Assurance team, and James Stewart heading up Technical Architecture at GDS.

To ensure we have a Board that fully represents GDS’ programme of work, I am pleased to also announce that Olivia Neal will join our Executive Management Committee, alongside Janet Hughes, Programme Director for Verify.

On behalf of everyone at GDS, I want to say very clearly: thank you Liam. You've worked extremely hard to make a difference, armed with your constant refrain of "Yes, but what is the user need?"

That's the question all civil servants should be asking, all the time. You lead by example.

Viewing all 965 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>