1

A customer is buying a medical product. During the checkout process, she's configuring the product. She has two configuration choices to make:

  1. The physical unit that the product uses (choose from 2 options)
  2. The UI language of the product (choose from 2 options)

This is in the context of a ~10 step process from choosing the product -> configuration -> shipment info -> payment info -> overview -> checkout. There might be more configuration steps in the future, but for now there's only 2.

I can show both configuration choices on the same screen, or break them up to have one screen for each choice. Both approaches have their own advantages:

Advantages to having both on one screen:

  • Fewer steps
  • Checkout flow bread crumbs don't have to change (there's only one "Product configuration" step)

Advantage to having a separate step for each choice:

  • Fewer things to understand on a screen

Questions:

  • Do you have tips for this particular issue?
  • Are there studies or best practices on reducing the number of choices per screen?
  • Well you already have the advantages listed. I think you just need to make a judgement call on which option best suits your specific application. Not everything has a hard and fast rule that you can apply to all scenarios. If you expect to expand on the options in the near future, then probably best to just split them out now as you will find it hard to justify the change later down the line once it's implemented. – musefan Jul 15 at 14:24
0

The breadcrumbs don't have to change

I understand that one page is the easiest to implement. My advice would be to create a prototype this way and do some hallway tests or test it on potential users. If the form is really long you will almost likely come to the conclusion that breaking it up is preferred. Long forms often perform better when broken up; whether it is because it reduces cognitive load and takes users less long to fill-in or make fewer mistakes, that can only be concluded when it is tested.

Second, breaking a form up to reduce cognitive load doesn't mean you have to introduce extra steps in the process. You can group form parts together under tabs or categorized sections that can be shown with a click etc.

At last I want to give the advice to ask the right questions and have realistic requirements, because you are probably stuck on your definition of what the "advantages" are. Fewer steps on the screen isn't immediately an advantage for your users, but it can be if more steps is becoming a problem. "The breadcrumbs don't have to change" sounds like a requirement made-up by a developer. Fewer things to understand on a screen can be a good requirement when it is made specific and can be proven that more things are problematic.

| improve this answer | |
0

In my opinion, either option will work, it just depends how they are presented to the user.

I prefer the single page design, but that's without more context of the project.

For example, having a combobox for a language next to a combobox for the physical unit would be no problem if there are few options.

If there are hundreds of options, it may be best to separate these two more, which depending on screen size for the application to be used on would vary. Small screens like phones, multiple pages may be a better idea.

Another option is using a modal over top of the current page to make selections in, it would simulate another page without the need to load another page.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.