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

1724RE: [agile-usability] user expertise and progressive usage (was RE: norman)

Expand Messages
  • Desilets, Alain
    Nov 3, 2005
    • 0 Attachment
      And if I may slip in one more UI praise for Word that in my opinion makes up for a lot of bad, the red squiggly. I'm talking about underlining misspelled words right away instead of waiting for a spell check. Brilliant. Of course, they ended up taking the superficial element of the concept too far with the Smart Tags. Talk about missing the point. 
      -- Alain:
      Yeah, I LOVE this kind of unobtrusive decorator. When used properly, they can provide a lot of additional information right away when it becomes relevant, but without interrupting the normal flow of work.
      The Eclipse IDE is great in that way. For example, as soon as I type a syntax mistake, the culprit token is underlined, plus a red stop sign and a light bulb appear in the margin. Clicking on the red stop sign shows the exact error message from the compiler, and clicking on the light bulb brings up a list of automatic fixes for the error (ex: replace "okBitton with okButton").
      Jade Ohlhauser
      Product Manager
      RPM Software                                 
      www.rpmsoftware.com 403-265-6727 x704

      From: agile-usability@yahoogroups.com [mailto:agile-usability@yahoogroups.com] On Behalf Of Larry Constantine
      Sent: Wednesday, November 02, 2005 8:02 AM
      To: agile-usability@yahoogroups.com
      Subject: [agile-usability] user expertise and progressive usage (was RE: norman)

      Jon Kern wrote:
      a valuable addition to something like Word would be the magic customizer
      slider (that i have invented in my head for years when i was building a very
      complex, somewhat horrid at times UI in the incarnation of TogetherSoft's
      ControlCenter UML modeling tool) that would allow features to go from novice
      to power user in terms of: visibility and depth and degree of user control.

      It's cute, been proposed many times by many people in one form or another,
      but whether it's a slider or a series of radio button, it turns out to be a
      bad idea.

      (1) A user is not across the board novice, intermediate, or expert in
      interaction style, but varies from one part of the UI to another. Typical
      users are improving intermediates for the 10-20% of the UI they use fairly
      regularly, expert for a few percent of over-learned features, and novices
      for the remaining bulk. But that changes over time and even with respect to
      what they are using the system for at a given moment.

      (2) Having the entire configuration of the user interface change because the
      user slips the slider up or down a notch is extremely disruptive user

      (3) Most users do not actually know at what level they are operating or what
      they should tell the system. Even making the choice on setup causes great
      anxiety, as many users fear that if they set the level too low, they will be
      prevented from doing things but if they set it too high they will be
      overwhelmed. Interestingly, when allowed to choose between so-called short
      menus (with reduced options and only basic features) and full menus, the
      vast majority of users prefer long menus.

      A far better approach is based on the progressive usage model (the ski-slope
      model, as it is sometimes known) which supports continuous and incremental
      in-context adaptation of the UI by users to fit evolving interaction style
      and level of expertise. (Covered in our book and several papers.)

      --Larry Constantine, IDSA

    • Show all 21 messages in this topic