Accounting too much for user error?

Question

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:

1. Make the change (or multiple changes)
2. Hit "Apply" (There are about 5 submenus each with multiple changes possible, each submenu has 1 apply button)
3. Hit "Submit Changes"
4. 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

Answer 1

"APPLY" and "SUBMIT CHANGES" are misleading. The changes are not actually applied until the Confirm button is clicked. And the changes are not actually submitted to the server until, again, the Confirm button is clicked.

"APPLY" is actually something like "SAVE FOR SUBMISSION". But that is stating the obvious, and therefore an unnecessary step.

"SUBMIT CHANGES" is actually "CONFIRM CHANGES...".

So by eliminating "APPLY" you have:

1. Select submenu.
2. Make Changes (one or more submenus).
3. Open confirmation window by clicking "CONFIRM CHANGES...".
4. Confirm changes.

(The ellipsis ... indicates clicking the button leads to the action, but is not performing the action, in this case CONFIRM.)

 

...we did not want to make too many calls to the server...

Ideally, when the users clicks the "APPLY" button apply the changes to the server. And pop up a temporary confirmation that includes an "UNDO" option.

And get rid of the "SUBMIT CHANGES" and "CONFIRM" steps.

1. Select submenu.
2. Make changes.
3. Apply changes.

A streamlined UX may be of greater value than whatever the cost incurred by multiple trips to the server.

 

By the way, there's currently five steps, and the first one is "Select submenu." ("Main Wi-Fi" in your screenshot), then the other four steps you listed. That's an important distinction because steps 3 and 4 apply to the list of submenus.