Loading ...
Sorry, an error occurred while loading the content.

Re: [agile-usability] Label Pushbuttons in a Process

Expand Messages
  • Anoop Jayakumar
    Hello Stefan, This sounds like a standard wizard type design. The key is to clearly indicate the progress of the process and what step you are currently in.
    Message 1 of 3 , Nov 14, 2008
    • 0 Attachment
      Hello Stefan,
      This sounds like a standard wizard type design. The key is to clearly indicate the progress of the process and what step you are currently in. The 'Previous' and 'Next' are the actions the users need to take to navigate through the process and hence are best left as they are. As a general rule it is best to avoid explaining the whole action on the button label. A better approach here would be to use the presentation of the page to convey the context of the action.
      Hope this helps.
      Cheers,
      ----
      Anoop Jayakumar
      User Experience Consultant
      anoop@...
      (408) 398 6080
      www.uxbay.com





      On Fri, Nov 14, 2008 at 1:07 PM, Stefan <stefan@concept7. nl> wrote:

      Visitors can complete a transaction to buy an insurance online by taking all the six steps
      in a process. A typical step in the process consist of a webform and two buttons. One
      button to go back one step in the process and one button to take them to the next stap.
      Usually we see this buttons labeled as `Previous' and `Next'. From literature (Research-
      Based Web Design & Usability Guidelines, 13:2 Label Pushbuttons Clearly) and own
      experience i know that the label of the button has influence and the exit percentages per
      step.

      The common labels `Previous' and `Next' tell the how they can browse through process
      and if combined with a good progress indicator (above the form) might work fine.
      However if the form of one single step is long then the progress indicator is out of sight of
      the visitor once they `reach' the next button. So i would plea for more informative labels
      of pushbuttons. But what information should the label consist? If you don't have a process
      it's easy because this button will inform the user what information it will get. For example
      three input field where the user can enter his/her birthdate and a pushbutton labeled `Get
      My Horoscope'. The relation between the form and button is clear. In a proces however it's
      more and indication of what the user has to do in the next step. The relation between the
      entered form and the pushbutton is less clear.

      Usually i would go for an a/b experiment to find the answer. In this particular case
      however this is not technically feasible.

      Are there any good papers about this subject? what do you advise me to do?

      Kind regards,

      Stefan


    Your message has been successfully submitted and would be delivered to recipients shortly.