The NHS digital service manual contains a number of forms components – like buttons and text boxes – that teams in the NHS can use to build accessible, mobile-first products and services.

While it’s easy for teams to find and reuse components like these, it’s not easy to find guidance on putting a good form together. Without guidance, there’s a danger that people will use the components to build ‘beautiful nonsense’ – in other words, branded NHS services that look good but do not meet users’ needs.

The service manual team worked with forms expert Caroline Jarrett to identify what NHS digital teams need to know about forms design. Caroline drew up a ‘forms topics map’ and tested it with public sector design teams, who fed back what they thought we should include. We then tested the topics with some teams at NHS Digital, sat in when Caroline did expert reviews of some NHS forms and took notes when teams asked for her advice.

Some teams clearly needed broad-ranging guidance on building forms. For example, there were delivery managers who needed to get new team members up to speed in forms design and there were content designers who had lots of experience of working on health information but who needed to learn how to write content for forms.

We also found some more specific needs. Some content designers, for example, wanted to know what order to put their questions in, while designers needed to know which questions should be mandatory and which ones should be optional. They also needed to know how to mark mandatory and optional questions.

One of the key things we found was that people generally started out looking for forms components, when in fact they needed to think through the questions they should be asking.

As Caroline Jarrett says, good form design consists of:

We decided that the most useful place for us to start was to publish guidance on writing good questions to get the right answers.

We tested our prototype with people working in NHS Digital teams, in the NHS Business Services Authority, an NHS trust and with a university digital health researcher. Participants included a mix of professions: service and interaction designers, content designers, user researchers, product and delivery managers.

We found a clear need for guidance and what we’d drafted did reflect the issues that digital teams were grappling with. People wanted us to include NHS examples and expected to find some of the guidance in our components and patterns pages. There was a lot of interest in questions about sensitive issues like ethnicity, sex and gender in health - enough interest for them to warrant a section of their own. The guidance also needed to be something that people could dip into to answer an immediate question, but that would also encourage them to read further. 

We’ve published the guidance in ‘beta’ because we want people to start using it and to feed back. There are some areas we know need more work and we’ll come back to these later:

We wanted to make sure that our existing components (such as radio buttons and error messages) reflect the new guidance. We’re also working on some new patterns. In particular, we’ve just published a new pattern for asking users for their NHS number.

You can find our new guidance on how to write good questions for forms here.

Please give us your feedback. You can email us at [email protected], join us on Slack (on our forms channel) and contribute via GitHub.