New answers tagged

0

I would disagree with your product team. Wizards are created just for that to give orientation to the users where they are in the process (especially if its a long task). However, having more steps in a process doesn't gives you necessarily worse performance than having just one or 3 steps, it depends on a lot of variables. You should strive to divide the ...


1

I have to say, I agree with your product team. Although there is no rule that states that you must not exceed the number of steps required for a wizard. Ideally you should strive to keep the number of steps to its minimum (short and concise). This is to prevent user from dropping off half way when they are going through your wizard. Or worst going back and ...


0

For a complex branching system, you could explore using a dynamic wizard. You don't have to construct the entire flow (start to end) since the steps are going to change dramatically based on what the user keyed in. Where should we tell the user that they are about to over-write everything past this point? When they start entering information into a ...



Top 50 recent answers are included