Ali Demirbaş - Lab
TRGet in touch

Forms & Signup

Should a Multi-Step Form Show a Back Button? A/B Test

A visible back button gives users a clear way to correct earlier answers, but adds another navigation step.

  • Forms & signup
  • Form completion rate

Control vs Variant

Absent on one side, present on the other.

Changed
Presence
Page
Forms & signup
Difference
added

Hypothesis

Compare completion only after verifying that answers are preserved when users go back.

How to run this test

Primary metric

Form completion rate

Compare successful submissions to see whether adding a back button affects completion.

Other metrics

  • Form data loss rateCheck whether previously entered information is lost when visitors go back and forward.
  • Step-level abandonment rateCompare exits at each step of the form.
  • Validation error rateTrack validation errors that appear when submitting or moving between steps.
  • Form completion timeMeasure time from form start to successful submission.

What to check before and during the test

  • Back controlAdd a visible back button without changing the existing forward action.
  • Keep constantKeep steps, fields, validation and data persistence the same in both arms.
  • UsageTrack use of the button within the variant; compare overall completion across assigned arms.
  • Browser behaviorCheck how browser-back navigation works alongside in-form navigation.
  • Separate testA final summary screen with edit links is a separate variable.

Setup mistakes to avoid

  1. 1Do not test the back button before implementing data persistence; that would measure your own data-loss bug.
  2. 2Do not change the number of steps in the same test.
  3. 3Do not block browser-back navigation.
  4. 4Do not treat low back-button usage as proof that the control is unnecessary; it can be a rare but important recovery path.
  5. 5Do not weaken payment security checks when testing back navigation in payment.