Cognitive Walkthroughs

Cognitive Walkthroughs

Testing Usability in User Experience

Overview for this lecture presentation:

Overview of Cognitive walkthroughs

Steps & Examples

Two articles that do a deep dive, for more information

A short video

User Flows

• User flows are the paths users take inside of an interfacfe. They consist of :
• User actions: What can the user do based on the interface available?
• System actions: What does the system do?
• Screens: What pages of the interface are the users brought to?
• Decisions: What does the user think, feel and do when they are interacting inside of a specific system?

User Flows

• Example of a simple ecommerce checkout.
• What does the customer see?
• What does the customer do?
• How does the customer feel?
• Where does the customer go next (decide)?

User Flows

• There are ALWAYS more than one path users can take for each specific screen. User flows help map them out. There can be multiple user flows for one system, and user flows can link to one another. You WILL have a flow for every major activity inside of an app/product.
• User flows can help you map activities for cognitive walkthroughs and define major necessary actions within an interface.

What is a Cognitive Walkthrough?

• Cognitive walkthroughs are an inexpensive task-based evaluation conducted by design/ development staff who attempt to perform tasks a user would.

• Meaning-- you're walking through steps a user would take to understand what it would take for them to do it/ what they would need to do it.

• Cognitive walkthroughs are usually done by members of a deisgn team. They focus on how easy it is for users to accomplish key tasks.
• Someone on the team who is not an "expert user" or someone who build the product is the best candidate for a cognitive walkthrough.
• Generates results quickly and inexpensively and is usually conducted prior to a task-based user study.

Why Do Cognitive Walkthroughs?

• Pros: Relatively low cost, can catch learnability issues early without recruiting many users. Helps generate actionable insights.
• Cons: Because no real users are involved, some problems (especially around satisfaction, longer-term use, emotional responses) may not emerge. Also depends heavily on how well you define the tasks/personas and how thoughtful the evaluators are.

They’re great for quick iterations, but not for knowing if users actually enjoy the product.

4 Questions to Start With

Typically we start with 4 questions when performing a cognitive walkthorugh.

1. Will the user try to achieve the right result? (Do they understand what the goal is?)
2. Will users notice the correct action is available? (button, link, etc)
3. Will the user associate the correct action with what they're trying to achieve? (Is the label/icon/etc meaningful?)
4. Will the user see that progress was made toward their goal? (Does the user get appropriate feedback?)

Developing task scenarios

• This is where it's easy to get hung up-- where you end up asking yourself, "Am I too in the weeds here? Will these tasks be too difficult?" Or on the flip side, "Are my tasks too basic/ easy?"
• Our goal is to develop high-quality tasks on the basis of
• Relevevance of the tasks to the site's mission and stakeholders
• Objectives that explore how well users are able to accomplish MUST-DO, critical tasks (not so much for expert users, rather new users. Focus on Learnability and Memorability).
• Relating tasks to a narrative scenario helps establish "sense-making" during cognitive walkthroughs. In other words, you want to help give users a reason WHY they're performing these tasks, not that they're just random activities. Give them a mission, and help them understand what that mission is along the way. Help them make sense of WHY they're doing it.

Developing Task Scenarios

• Meaningful and reasonable: Make sure there is a reason/point for doing them.
• Motivating: There is a goal that users want to achieve. Which ties into the next👇
• Goal-oriented: When the users achive this, they accomplish a key, nescessary task in the system.
• In a realistic sequence: They are able to perform all steps in a reasonable order.
• Not revealing of tips: We want to know whether a user will want to perform a task on their own. We can't hand-hold.
• Supported: We never want catastrophic error where things aren't working. Step in only when necessary.

Two Readings to Help you:

Evaluate Interface Learnability with Cognitive Walkthroughs

How to Conduct a Cognitive Walkthrough Workshop

Gives you an overview of Cognitive walkthroughs and how they're used.

Walks you step-by-step through a cognitve walkthrough

Read Article

Read Article

Example Cognitive Walkthrough:

Task 1:

Open Instagram & Find “Add to Story”

• For context:Q1: Will the user try to achieve the right goal?
• Yes. The persona wants to share a lunch photo . They’ll look for a “+” or “camera” icon.

• Q2: Will they notice the correct action?
• Yes. On the home screen, the “+” button and the profile picture with a “+” are both visible.

• Q3: Will they understand the action’s meaning?
• Somewhat. The “+” may be confusing (add post vs. add story), but the profile “+” is clearer.

• Q4: Will they get feedback?
• Yes. Tapping opens the camera with clear UI → confirms progress.

Example Cognitive Walkthrough:

Task 2:

Take or Upload a Photo

• Q1: Will the user try the right goal? → Yes, they want to capture or upload.
• Q2: Will they notice the right action? → Yes, camera shutter button is obvious, plus “upload from gallery” icon.

• Q3: Will they understand meaning? → Yes, both icons use standard conventions.

• Q4: Will they see feedback? → Yes, the photo preview appears right away.

Example Cognitive Walkthrough:

Task 3:

Edit Story (stickers/text)

• Q1: Will they try the right goal? → Likely yes, since the icons invite interaction.
• Q2: Will they notice correct action? → Yes, icons for text (Aa), stickers, and draw tool are all visible.

• Q3: Will they understand meaning? → Mostly yes. Some icons may be unfamiliar at first, but tapping gives immediate feedback.

• Q4: Will they see feedback? → Yes, text appears, stickers drop onto the photo.

Example Cognitive Walkthrough:

Task 4:

Post Story

• Q1: Will they try the right goal? → Yes, they want to share → look for “Your Story” button.
• Q2: Will they notice the correct action? → Yes, the “Your Story” button is at bottom left.

• Q3: Will they understand meaning? → Yes, wording is clear: adds content to their story.

• Q4: Will they see feedback? → Yes, after posting, “Your Story” updates with a colored ring.

ETC...

That's it for now!

Same time next week?

Send An Email!

This short video shows an example of how to conduct a user interview.

User flows help us map out the paths users take inside of an interface. Here is an 22 minute video on what user flows are and how they relate to cognitive walkthroughs.