It is a 'review technique' where 'expert evaluators' construct 'task scenarios' from a specification or early prototype and then role play the part of the user working with that interface. ( esp. for pointing out learnability issues )
Goals -> tasks -> actions (cognitive + physical)
Orig: Code walkthrough by developers.
Established process by Wharton et. al (1994). Hence abbreviated occassionally as WCW.
Every step evaluated using
1. Will the users achieve the right effect?
2. Will the user notice that the correct action is available?
3. Will the user associate the correct action with the effect the user is trying to achieve?
4. If the correct action is performed, will the user see that the progress is being made towards solution of the task?
Outcome: Learnability issues, gap in design, design ideas, faulty task flows.
Constraints: Lengthy design discussions, Design Defensiveness and Time Pressure
See Also:
Rick Spencer, "The streamlined cognitive walkthrough method"
No comments:
Post a Comment