Need navigation help with a complex wizard app

19 Jun 2007 - 3:35pm
7 years ago
1 reply
445 reads
Mark Richman
2006

My company wishes to use a wizard to drive the user through the process --
and I think this is a good idea since it is not something most users will do
very often. More likely, they will struggle through it once, refine it, and
not touch it again for another six months, at which time they will need to
be reimmersed in the process. So some good handholding is a requisite.

How have other designers designed navigation buttons when a process included
a difficult and time-consuming step? One solution that seems plausible is to
have both a 'Save' and a 'Next' button, where 'Save' would perform an
intermediate save, while 'Next' would save and move to the next step.
However, since 'Next' doesn't explicitly state a save, a message might be
needed to let the user know for sure that his work has been saved -- and I
want to avoid making the user read more than she needs to.

Another option might be to call the buttons 'Save Only' and 'Save and
Continue'; wordy but more to the point.

As you can see, I am spinning my wheels. Any ideas? While a wizard might not
be the only solution, a lot of handholding will be needed here and it seems
like a good chocie to me.

Thanks,

Mark Richman
Intelliverse

Comments

19 Jun 2007 - 4:27pm
jstrande
2007

Mark,

Have you considered auto-saving? Every 15/20/60 seconds save the current
state the person is in. GMail does this when you're composing an email,
working in Google Docs, etc.

If the process is mentally taxing, anything you can do to reduce the burden
of extra steps/buttons is helpful (obviously).

Jon

On 6/19/07, Mark Richman <markjrichman at gmail.com> wrote:
>
> My company wishes to use a wizard to drive the user through the process --
> and I think this is a good idea since it is not something most users will
> do
> very often. More likely, they will struggle through it once, refine it,
> and
> not touch it again for another six months, at which time they will need to
> be reimmersed in the process. So some good handholding is a requisite.
>
> How have other designers designed navigation buttons when a process
> included
> a difficult and time-consuming step? One solution that seems plausible is
> to
> have both a 'Save' and a 'Next' button, where 'Save' would perform an
> intermediate save, while 'Next' would save and move to the next step.
> However, since 'Next' doesn't explicitly state a save, a message might be
> needed to let the user know for sure that his work has been saved -- and I
> want to avoid making the user read more than she needs to.
>
> Another option might be to call the buttons 'Save Only' and 'Save and
> Continue'; wordy but more to the point.
>
> As you can see, I am spinning my wheels. Any ideas? While a wizard might
> not
> be the only solution, a lot of handholding will be needed here and it
> seems
> like a good chocie to me.
>
> Thanks,
>
> Mark Richman
> Intelliverse
> ________________________________________________________________
> Welcome to the Interaction Design Association (IxDA)!
> To post to this list ....... discuss at ixda.org
> List Guidelines ............ http://listguide.ixda.org/
> List Help .................. http://listhelp.ixda.org/
> (Un)Subscription Options ... http://subscription-options.ixda.org/
> Announcements List ......... http://subscribe-announce.ixda.org/
> Questions .................. lists at ixda.org
> Home ....................... http://ixda.org/
> Resource Library ........... http://resources.ixda.org
>

Syndicate content Get the feed