So I am redesigning a configuration page and I feel that our current flow is overcompensating for user error too much. Basically, when you want to make a change on a device there are four steps:
- Make the change (or multiple changes)
- Hit "Apply" (There are about 5 submenus each with multiple changes possible, each submenu has 1 apply button)
- Hit "Submit Changes"
- Look at list of changes you made, hit confirm.
The reasoning for step 3 + 4 was because we did not want to make too many calls to the server, so all the changes should be submitted at once. I suggested we remove step 2 (the apply button) so that the user can make 1 or multiple changes, hit "submit change" and preview their list before confirming their changes. I was told that the apply button will act as a safeguard to make sure the user is sure about their changes, but I figured step 4 takes care of that. Do you think having 2 safeguards (step 2 to make sure the you want to save the changes, step 4 to preview them all before actually making a request to the server to make those changes) is necessary? The user will be making multiple changes at once in the beginning, then most likely minimal changes once everything is set up.
Edit: I realize user testing here would provide the best evidence, but my company does not provide the resources necessary to user test. Best I can do is ask around my company, but most potential users are familiar with our ui/ux already