Twitter Updates

    follow me on Twitter

    March 2014

    Sun Mon Tue Wed Thu Fri Sat
                1
    2 3 4 5 6 7 8
    9 10 11 12 13 14 15
    16 17 18 19 20 21 22
    23 24 25 26 27 28 29
    30 31          

    « Sketching Design | Main | Design Partners: Passing on the Knowledge of UX »

    August 14, 2009

    TrackBack

    TrackBack URL for this entry:
    http://www.typepad.com/services/trackback/6a01127908c29528a40120a4f44429970b

    Listed below are links to weblogs that reference Usability Testing with User Proxies: When is "Close" Close Enough?:

    Comments

    I know you guys are busy, but in the hope of spurring more of these interesting posts, here is a thought on the time factor of high velocity usability testing.

    Tools you use in a 30 minute test vs tools you use in a 30 month project.
    Using Revit 2010 as an example:
    File>New>Project vs File>New>Family
    In any test of the software, you will need to use new>project and are unlikely to spend enough time in the program to use new>family so the interface gets skewed toward new>project. However, in the real world, you only use new>project once per project... maybe two or three times at the beginning as you work through false starts. Then you use new>family often at certain phases of the project. Again, testing at the wrong time and the choice doesn't get used at all, testing at another time and the tool gets used every day, several times a day. In Revit, either a flow chart or a bad test nested new>family below new>project adding clicks to a frequent process over the old interface which had them equal (technically the same number of clicks but in a slower interface it takes longer)

    High velocity here doesn't get you accurate data... for a simple function which probably wouldn't warrant user testing.

    The comments to this entry are closed.

    RSS Feed

    • Subscribe