Government Digital Service (GDS)
|Printable version||E-mail this to a friend|
It takes 2: how we use pair writing
I’m Sue. As a content designer at GDS, it’s my job to write content for everyone. This means I write in the simplest way to help our users do things that are often complex. To make sure the words we use are both clear and accurate, we often need input from experts in a particular area like law, policy or product. We’ve found that working together to ‘pair write’ is a good way to do this.
I’ve run quite a few pair writing sessions and I’m constantly tweaking them depending on where in the country the 2 people are, and how quickly the content needs to be written. However, in all cases so far, I’ve found that this 4-step process works well and makes sure your content meets user needs.
1. Make sure you’re starting on the same page
The best way to kick off is, like always, to start with user needs. There’s a chance that the subject expert might not be familiar with a user-needs-centred approach, so it’s worth spending time focusing on what user needs are. This will help you both work with the same thing in mind.
Then work out the ‘user acceptance criteria’ for the piece of content you’re going to write. These are the things that the piece of content will need to include to be useful to the user. To do this, I usually ask the pair writers to think about the main questions users will have about the thing they’re trying to do.
And finally, before you start writing, the subject expert should flag if there’s any information you have to include for legal reasons. I’d recommend writing down anything you have for each of the categories and keep them in mind throughout the process.
2. Agree on a sensible structure
Put yourself in the user’s position and think about the questions they’re likely to have, and the order they’re likely to have them in. This will give you a starting point and an idea of a sensible order for the content.
3. Write words. Get rid of jargon.
You can both sit at one screen or use Google Docs on separate screens. The subject expert should be in control of the keyboard in the beginning to give them the opportunity to get their specialist knowledge down. The content designer’s role is to challenge jargon. Sometimes, you can’t get rid of tricky words or phrases for legal reasons but you should always explain what they mean in plain English. As they watch the subject expert write, content designers ask questions like:
- is there another way of saying that?
- what do you mean by...?
- should this part come further up?
Usually, I’ve found it works well if the pair swaps who types every now and then.
You’ll know you’ve finished when you’ve addressed all the user needs you wrote at the start of the session.
4. Ask for input (but put a time limit on feedback)
Most of the time, the thing you produce on the day won’t be a super shiny ‘finished’ thing - you’ll need to polish and tweak afterwards. Sometimes, you’ll need experts in other areas to fill in a couple of gaps here and there.
It’s really good to get input from relevant and knowledgeable people but it’s always worth giving very strict deadlines for feedback and amends. If you don’t, the polishing process can be never-ending and you risk delaying getting the content to your users.
Near, far, wherever you are
Pair writing sessions are great in person but they work equally well if you have access to collaborative software. Google Hangouts allows both people to speak on a video call and see each other’s screens. Trello lets you group and order cards in online lists, which is really useful at the start of the pair writing process when you work out user needs and acceptance criteria. When you start writing, do it in Google Docs and share the document between you. You can see each other typing in real time.
Pair written guides in practice
Earlier in 2016, I worked on the Digital Marketplace. We launched a new way for the public sector to find what it needs to buy for its digital projects. When we launched the minimum viable product (MVP), users needed to complete some steps outside the Digital Marketplace. This meant we needed to write acollection of 17 guides, in less than 3 months, to make sure buyers knew how to do the right things at the right time. Content lead Roz Strachan explained more about how we wrote content as a team.
Pair with us
We’re running training sessions on how to pair write. To find out more, email
You may also be interested in:
Latest News from
Government Digital Service (GDS)
National Get Online Week: what we’ve been doing21/10/2016 12:10:00
Blog posted by: Chad Bond and Jacob Bonwitt, 20 October 2016 — Events, GDS team.
Designing the register creation process20/10/2016 12:15:00
Blog posted by: Martin Jordan and Tom Hughes, 18 October 2016 — Data group.
How the Sexual Health: 24 service used GOV.UK patterns17/10/2016 16:25:00
Blog posted by: Harry Trimble, 14 October 2016 — Service standard, Services Programme.
Platform as a Service team takes even-handed approach to meetings10/10/2016 10:20:00
Blog posted by: Dan Carley, 7 October 2016 — Accessibility, GDS team, Platform as a Service.