Marcus Andrey Study
Ler em português Library

UX Foundations · Labs · 3 min read

Redesign a form

A guided lab: take a real form you've filled in, question every field, rewrite the labels and error messages, split it into simple steps, and sketch the new version on paper with its error and success states. About an hour and a half, with paper and a pen.

Every bad form you've filled in is free practice material. In this lab you'll take one real form and redesign it on paper, as if the organisation had asked you to make it easier. You won't change its purpose; you'll change how it asks.

What you'll do:

  • Pick a real form and list every field
  • Question each field and cut what isn't needed
  • Rewrite labels, hints and error messages
  • Sketch the new form, including its error and success states

You'll need: a real form (paper or online), paper, a pen, about an hour and a half. Optional: Figma or any drawing tool, if you prefer to sketch on screen.


1. Choose a form

Pick a form you've filled in yourself and found annoying: a gym membership, a rental application, a school or clinic registration, a delivery address form. At least eight fields is ideal. Take a photo or a screenshot for yourself, and write the form's goal at the top of your page, for example "join the gym and pay the first month".


2. List and question every field

Write every field in a table, and question it the way GOV.UK's "question protocol" does (GOV.UK, Structuring forms):

# Field (as it is) Who uses the answer, and for what? Needed now? Keep, move or cut
1 "Name" Membership card Yes Keep, as "Full name"
2 "Fax number" Nobody No Cut
3 "How did you hear about us?" Marketing No Move to after sign-up, optional

You won't know every answer for sure. Make your best guess and mark it with a "?"; in real work, you'd ask the team.


3. Rewrite labels, hints and errors

For each field you keep:

  • Write a clear label in plain words ("Date of birth", not "DOB").
  • Add a hint only if people need it ("For example, 27 3 1990").
  • Write one error message: what's wrong and how to fix it ("Date of birth must be in the past"). Avoid "invalid", "please" and "sorry", and don't repeat an example that is already in the hint, as GOV.UK advises (GOV.UK Design System, Error message).

4. Group and order into steps

Group related fields (about you, contact, payment). Order them the way people think: easy questions first, eligibility questions before anything long. For a longer form, put one question or one small group per page, as in Forms. Write the step names in a row: "1 About you · 2 Contact · 3 Plan · 4 Payment · 5 Check your answers" (GOV.UK Design System, Check answers).


5. Sketch the new form

On paper, sketch each step as a phone screen (a rectangle about the size of your hand). Then sketch three extra screens:

  1. One error state: a field with its error message next to it, and the summary at the top.
  2. The check-your-answers page: everything people entered, with a "Change" link for each part.
  3. The success state: what happened, a reference number if there is one, and what happens next (Interface states: empty, loading, error, success).

6. Compare before and after

Count the fields before and after. Then read your new form aloud, as if you were asking the questions to a friend. Any question that sounds strange out loud needs rewriting.


7. Check your work

Reflection questions: Which field was hardest to cut, and why? What would you need to ask the organisation to be sure?

Optional, with others: give your paper sketch to someone and ask them to "fill it in" aloud with a pen, without help. Where did they hesitate?

Forms · Interface states: empty, loading, error, success · Affordances, signifiers and feedback · Test with three people

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close