What an Abandoned Form Can Teach a Design Team

An exit is evidence of an exit

A person leaving a form does not explain why they left. They may have lacked required information, misunderstood a question, lost connectivity or decided that the service was unsuitable. My recommendation is to treat abandonment as a signal for investigation rather than a complete diagnosis. Changing the button colour might do nothing if the actual barrier is an unclear eligibility question.

Observe the point of uncertainty

In a fictional usability session, a participant reaches a field asking for a reference number. The form does not explain where the number appears or whether it is essential. The participant searches another document, returns and then stops. Record those actions and the participant’s comments separately from the team’s interpretation. One observation suggests a question to explore; it does not establish how all users behave.

Review what the form asks people to do

Check whether each question has a clear purpose, whether instructions appear at the point of need and whether errors help someone recover. Include keyboard and assistive-technology considerations in the review. GOV.UK’s service standard emphasises helping users complete their task simply. That is a useful design aim, but meeting it requires evidence from the actual service and its users.

Test a specific change

The fictional team could explain where to find the reference number and clarify the permitted alternative. Test the revised wording with an appropriate participant group and compare observations. Keep other changes limited so the team can understand what it is learning. Follow approved research and privacy arrangements when observing real users. Do not publish recordings or personal information without the required permission.

Write the evidence behind the decision

Record the observed difficulty, proposed change, reason for testing it and what happened next. If the evidence is inconclusive, say so. Keep looking at successful completion, understandable errors and accessibility rather than treating fewer exits as the only measure of quality. A useful form supports an informed task, including a legitimate decision not to proceed.

Source and editorial note

Author: Jefferson Otonbara Imgbi. Reviewed 8 October 2026. The recommendations and fictional examples are original RDE editorial learning material. The source below provides background, not endorsement of RDE.

GOV.UK Service Standard: make the service simple to use

Cover image: AI-generated illustrative scene created specifically for this resource.