Do you include a “Back” button in multi-step wizards?

Loading last updated info...

When building multi-step wizards (e.g. forms, onboarding flows, or setup processes), always provide a "Back" button, unless there's a very good reason not to.

A "Back" button gives users confidence that they can safely navigate through the steps without fear of losing progress. It helps reduce frustration and increases completion rates, especially when users need to review or correct something in earlier steps.

Image

❌ Figure: Bad example - User hits "Next" and can't go back to change their answer

Image

✅ Figure: Good example - "Back" button is clearly visible

Implementation tips

According to Design Specifications and Guidelines - User Assistance, the commands for navigating through a wizard should be "< Back" and "Next >".

Exception

Disabling or hiding the Back button is OK when:

  • The previous step doesn’t exist (e.g. it's the first step)
  • It's a single-step flow with no navigation needed

Authors

Need help?

SSW Consulting has over 30 years of experience developing awesome software solutions.

We open source.Loving SSW Rules? Star us on GitHub. Star