Running your digital project - tips from MOJ Digital

Written by Martin Oliver on 15 December 2015 in Features
Features

What lessons can local authorities learn from the Ministry of Justice's digital unit in running digital projects? Martin Oliver explains.

Stopping the ‘cut and shut’ approach to projects

We’ve all seen examples of ‘cut and shut’ digital projects. These involve running the build and development work independently of the content and user experience before bolting the elements together at the end.

The results are rarely pretty.

Luckily, the MOJ Digital content team is a pretty experienced bunch (among other achievements we delivered four exemplar services last year). We're using what we've learnt to make sure development works hand-in-hand with content and design.

A content designer at work
A content designer at work

Start off in the right way

The discovery phase of any project is the ideal time to focus on identifying key content and interaction issues. You should:

1. Get content, research and design working together ASAP

As Ben Terrett, ex-design director at Government Digital Service said, ‘words are as much the interface as design’. Your content person, designer and researcher are all responsible for the user experience so make sure they're working together up front.

2. Go as deep into your content and design as quickly as you can

Get your content, research and design team deep-diving into the content. The more they learn about users, the quicker they can ask important questions and make structural decisions.

3. Test high-fidelity content with low-fidelity technology

Focus on detailed content with the lowest-fidelity technology available (like paper) to understand user problems and test how to answer them. This will save you building components later that are no longer needed.

Photo of pieces of paper
Paper prototype

Moving on to build

Your research, content and design will want to test numerous options but your coders can’t (and shouldn’t) be keeping pace.

This can lead to a growing gap which then cause issues with implementing the latest versions of content and design. Our teams have worked in different ways to solve this challenge.

Using a detailed prototype

One of our teams maintains a high-fidelity prototype of the service using a tool called Axure (other prototyping tools are available).

The designer set up everything up initially, ensuring that screens mimics the look and feel of the service, and now uses it to show and test interactions.

It also offers an environment where the content designer works with the content ‘in situ’. This means that the content designer can see how the content fits with the design and make as many changes as necessary directly into it.

Designing content in Axure - making the words part of the process.
Designing content in Axure – making the words part of the process

When the latest interactions and content versions have been tested with users, this version of the tool is released to the developers who update their work accordingly.

It works for remote teams because screens can only be checked out by one team member at a time.

Building with content in mind

Other teams have adopted a different approach. They’ve collaborated with the developers who have build the application in such a way that enables content designers to work with the code.

This has meant that the developers keep the majority of content in one place and write automated tests that don’t break every time the copy changes.

The teams have also discovered that it’s helpful if content files are created using basic html formats such as Markdown or Slim. Doing this means that they’re easy to edit and update using a basic text editor like Sublime.

Screen containing editable code
Content file that can be easily edited using basic html

Setting up the project in this way means that content designers can then take some of the burden from developers by making small copy changes directly into the application’s source code.

Martin Oliver is Head of Delivery, MOJ Digital at UK Ministry of Justice​

This article was published under the  Open Government Licence v3.0

Share this page

Tags

Comments

Peter Jordan (not verified)

Submitted on 18 January, 2016 - 16:56
All good advice, but surprised you've not mentioned quant data and analysis. Even at the discovery stage there is usually data available to analyse from legacy/off line services and search analytics is an important input to content design - to understand users' language. And when you are in beta and then live, you'll have data from users who are 'actually using' the service. Analysing their behaviour will identify issues for user researchers to explore. Vice versa, you can explore the data to see if issues identified by researchers are replicated at volume.

Add new comment

Related Articles

Oliver Dowden given ministerial responsibility for GDS
15 January 2018

Hertsmere MP’s brief as minister for implementation also includes IPA, CCS, and cybersecurity initiatives

The government should be a role model on IT reuse
18 December 2017

Remanufactured computers could provide 95% of the performance of a new PC at a fraction of the cost to the environment; it is time for the civil service to set an examples, argues professor Mark...