Cognitive walkthrough: Difference between revisions
m (using an external editor) |
m (using an external editor) |
||
| Line 26: | Line 26: | ||
This project also defines a much more elaborated [http://wiki.fluidproject.org/display/fluid/UX+Walkthrough+Process UX Walkthrough Process]. In particular, it suggest to formalize the inspection process along three axis: | This project also defines a much more elaborated [http://wiki.fluidproject.org/display/fluid/UX+Walkthrough+Process UX Walkthrough Process]. In particular, it suggest to formalize the inspection process along three axis: | ||
{quotationbox|# A protocol that clearly specifies what we are going to do, and what information we are going to capture along the way. | {{quotationbox|# A protocol that clearly specifies what we are going to do, and what information we are going to capture along the way. | ||
# A predetermined clearly specified target that we are going to inspect: (product, version, instance, set of chunks) - the thing we're going to do it to. | # A predetermined clearly specified target that we are going to inspect: (product, version, instance, set of chunks) - the thing we're going to do it to. | ||
# A report template specifying the format, style and content of the report of the information we capture. | # A report template specifying the format, style and content of the report of the information we capture. | ||
Revision as of 12:18, 18 March 2011
<pageby nominor="false" comments="false"/>
Introduction
According to the NASA usability toolkit, retrieved 12:18, 18 March 2011 (CET), A cognitive walkthroug, is a “process of going step by step through a product or system design and getting reactions from key team players and typical users. One or two members of the design team can guide the walk through while one or more users will comment as the walk through proceeds.”
The Fluid project, retrieved 12:18, 18 March 2011 (CET), provides the following definition: “A cognitive walkthrough is a step-by-step exploration of a service to see how well a particular type of user, usually represented by a persona, is able to accomplish a particular objective or set of objectives. The objectives selected for testing are dictated by the persona that is chosen.”
Method
The Fluid project roughly suggest the following procedure.
(1) Choose a user from whose perspective the walkthrough will be done. You may choose a persona for that.
(2) Define what the person wants to achieve
(3) Define the steps that this person should do in order to achive her/his goals
(4) Perform the task and take notes about the following kind of issues for each step:
- Will the user know what to do at this step?
- Is complex problem solving needed to figure out what to do?
- Will they know that they did the right thing (if they manage) and are making progress towards their goal?
- Is complex problem solving needed to interpret the feedback?
This project also defines a much more elaborated UX Walkthrough Process. In particular, it suggest to formalize the inspection process along three axis:
- A protocol that clearly specifies what we are going to do, and what information we are going to capture along the way.
- A predetermined clearly specified target that we are going to inspect: (product, version, instance, set of chunks) - the thing we're going to do it to.
- A report template specifying the format, style and content of the report of the information we capture.
Links
- Introductions
- Cognitive Walkthrough at Fluid. Added by Jonathan Hung, last edited by Allison Bloodworth on May 26, 2009.
- UX Walkthrough Process at Fluid Added by Colin Clark, last edited by Paul Zablosky on Feb 12, 2009