1 / 35

Cognitive Walkthroughs

marina
Download Presentation

Cognitive Walkthroughs

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Cognitive Walkthroughs

    2. Memphis Timecards... Hall of shame.

    3. First, login.

    4. Wrong login...

    5. Okay...

    10. ?

    11. What now?

    12. WRONG

    13. Oops

    14. Well, okay, but why don't you...

    15. Tabs... So many tabs...

    16. Okay, but what does it all mean?

    17. Problems... Ungraceful error checking & Ungraceful default values Login Changes to caps upon unsuccessful entry No clue on which login to use Missed a time card Entered time before choosing hour

    18. Problems... Not easy to use for a first-time user Which login? Where to click-> Gulf of evaluation What I really want is a huge CLICK HERE TO FILL OUT A TIMECARD button, and a huge I'M DONE NOW What does the submit screen mean?

    19. Problems... Not easy for a proficient user either! ALWAYS enter time before type If time is always NOT OVERTIME, just DEFAULT Tabs visit non-entry fields VERY FRUSTRATING to miss a timecard deadline No clue on how to fill it out after deadline is missed

    20. Questions?

    21. Evaluation Without Users Quantitative Methods back-of-the-envelope action analysis GOMS/keystroke analysis Qualitative Methods expert evaluation cognitive walkthrough Discuss today Perform Wednesday Paperwork due Friday heuristic evaluation (after break)

    22. Evaluation Without Users But, WHY evaluate the interface without the users? Helps get rid of obvious problems that would waste your users time May catch problems that testing with a few users will miss

    23. Cognitive Walkthroughs CONCEPT : A formalized way of imagining people’s thoughts and actions when they use an interface for the first time. THEORY : A user sets a goal to be accomplished by the system. The user will search the system for the action that seems likely to make progress towards that goal. By putting yourself in the user’s shoes you can figure out where the “gulfs” might occur.

    24. Cognitive Walkthroughs – how and why Goals imagine user’s experience evaluate choice-points in the interface detect confusing labels, icons, images or options detect likely user navigation errors improvement, not defense Start with a complete TCUID scenario never try to “wing it” on a walkthrough

    25. Cognitive Walkthrough How To - I Begin by collecting: An idea of who the users will be and their characteristics Task description Description of the interface (a paper prototype) Written list of the actions to complete the task given the interface (scenario)

    26. Cognitive Walkthrough How To - II For each action in the sequence (scenario) tell the story of why the user will do it ask critical questions (4 plus 1) will the user be trying to produce the effect? will the user see the correct control? will the user see that the control produces the desired effect? will the user understand the feedback to proceed correctly? will the user select a different control instead? Every gap is an interface problem

    27. Making this Approach Work Tell a Believable Story How does the user accomplish the task, action-by-action Based on user knowledge and system interface Work as a group don’t partition the task Be highly skeptical remember the goal!

    28. Benefits of a Cognitive Walkthrough Focus most on first experiences - learnability Easy to learn Can do early in the software cycle Questions the assumptions about what a user might be thinking. Can identify controls that are obvious to the SE but not to the user It can suggest difficulties with labels and prompts It can help find inadequate feedback Can help find inadequacies in the spec

    29. Shortcomings of Cognitive Walkthrough Is diagnostic, not prescriptive Focuses mostly on novice users Relies on the ability of engineers to put themselves in the users shoes

    30. When to do a Cognitive Walkthrough Before you do a formal evaluation with your users Can be done on your own for small pieces of the whole Can do a walkthrough of a complete task as the interface develops

    31. This week’s deliverable Perform the walkthrough for each of 3 scenarios Walkthrough evaluation log At each step/action in the scenario, answer the five questions. In many cases, this should be more than simply Yes/No. Where appropriate, include WHY you think your answer is appropriate. Walkthrough evaluation report Write up a list of interface problems discovered during the walkthrough Add brief notes about how you discovered them Any questions?

    32. Exercise: Cognitive Walkthrough Analysis Let’s have you walk through the actions in a couple of scenarios in groups Form non-project groups of 3-4 Try to: identify problems locate alternative widgets/controls estimate error probabilities (25% intervals) Discuss / brainstorm with others in your group Report findings at the end

    33. Exercise: Cognitive Walkthrough Analysis High-fi prototype: UNI’s Academic Advising and Career Services Tasks: Your user is a “typical” UNI student – for the most part, you, but perhaps a little less computer savvy. Use the site to answer the following questions: “What can I do with a degree in Computer Science?” “Where can I learn about writing a resume?” “How do I calculate my GPA?”

    34. Exercise: Cognitive Walkthrough Analysis Scenarios: Provided in a separate handout along with the prototype Remember the process - at each action step, ask: will the user be trying to produce the effect? will the user see the correct control? will the user see that the control produces the desired effect? will the user understand the feedback to proceed correctly? will the user select a different control instead?

    35. What did you come up with?

More Related