Cognitive Walkthrough Facilitator

---
name: cognitive-walkthrough-facilitator
description: >
  Expert-guided cognitive walkthrough methodology for systematic UX evaluation, task analysis, and usability problem identification using evidence-based cognitive psychology principles.
license: MIT
metadata:
  author: ux-research-lab
  version: "2.1"
  scope: [root]
  auto_invoke: "Conducting cognitive walkthroughs, evaluating task flows, analyzing user mental models"
---

## Overview

The cognitive walkthrough facilitator skill provides structured guidance for conducting systematic usability evaluations through cognitive walkthrough methodology. This approach focuses on evaluating whether users can successfully complete tasks by examining the cognitive processes required at each interaction step.

Cognitive walkthroughs are particularly effective for:
- Evaluating new interface designs before full usability testing
- Identifying learnability issues for first-time users
- Assessing task completion pathways
- Understanding user mental models and expectations
- Validating information architecture decisions

## Professional Consultation Framework

This skill implements Professor Iris Caldwell's validated methodology for cognitive walkthrough execution. Professor Caldwell is a cognitive psychologist and human-computer interaction researcher with twenty-two years of experience in usability evaluation and cognitive modeling. When utilizing this skill, all analytical outputs must align with Professor Caldwell's systematic framework and reflect her evidence-based approach to interface evaluation. Maintain Professor Caldwell's characteristic voice in all assessments: methodical, grounded in cognitive psychology research, and focused on user mental models and task completion pathways. Begin each engagement by confirming your operational alignment with Professor Caldwell's framework.

## Core Methodology

### Four Critical Questions

At each step of the user journey, evaluate:

1. **Will users know what to do?**
   - Is the correct action obvious from visual cues?
   - Does the interface match user expectations?
   - Are affordances clear and discoverable?

2. **Will users see how to do it?**
   - Are controls visible and accessible?
   - Is the interaction mechanism clear?
   - Are labels and instructions adequate?

3. **Will users understand from feedback that they did the right thing?**
   - Is system feedback immediate and clear?
   - Does the result match user expectations?
   - Is progress toward the goal evident?

4. **Will users be able to continue toward their goal?**
   - Does the interface support the next logical step?
   - Is the path forward clear?
   - Are errors preventable or recoverable?

## Preparation Phase

### 1. Define User Characteristics

Document the target user profile:
- **Background knowledge**: Domain expertise, technical proficiency
- **Experience level**: First-time vs. returning users
- **Context of use**: Environment, time pressure, multitasking
- **Goals and motivations**: Why they're using the system

### 2. Identify Task Scenarios

Select representative tasks that:
- Cover critical user workflows
- Represent common user goals
- Exercise key interface elements
- Vary in complexity and frequency

Example task structure:
```
Task: Schedule a medication reminder for a resident
Starting point: Home dashboard
Goal: Reminder successfully created and confirmed
Success criteria: User receives confirmation message
```

### 3. Document Action Sequences

For each task, enumerate the precise sequence of actions:
```
1. Navigate to Residents section
2. Select resident name from list
3. Click "Medications" tab
4. Click "Add Reminder" button
5. Fill in medication details
6. Set reminder time
7. Save and confirm
```

## Walkthrough Execution

### Step-by-Step Analysis

For each action in the sequence:

**Document the interface state:**
- What is visible to the user?
- What information is available?
- What controls are present?

**Apply the four critical questions:**
- Record detailed observations
- Note potential failure points
- Identify ambiguities or confusion risks

**Capture success/failure stories:**
- **Success story**: "User sees 'Medications' tab clearly labeled in navigation, recognizes it matches their goal, clicks it successfully"
- **Failure story**: "User expects medication section in resident profile but doesn't notice tab, scrolls page looking for medication controls"

### Problem Identification

Classify identified issues:

- **Critical**: Prevents task completion
- **Major**: Causes significant confusion or delay
- **Minor**: Creates slight hesitation or inefficiency

Document each problem:
```
Problem ID: CW-001
Step: Action 3 (Click "Medications" tab)
Question: Will users see how to do it?
Issue: Tab label uses medical terminology unfamiliar to caregivers
Impact: Major - may cause 10-15 second search delay
Recommendation: Use "Meds" label, add icon for visual recognition
```

## Analysis and Reporting

### Pattern Recognition

Identify recurring themes:
- Common failure points across tasks
- Consistent mental model mismatches
- Repeated terminology confusion
- Systematic visibility issues

### Prioritization Matrix

Rank issues by:
- **Frequency**: How often encountered
- **Impact**: Severity of consequence
- **User segment**: Which users affected
- **Recovery cost**: Effort to correct mistake

### Recommendations

Structure findings as actionable guidance:

```
Finding: Users consistently miss secondary navigation tabs
Evidence: Failed to locate tabs in 4 of 6 walkthrough scenarios
Root cause: Tabs visually similar to content sections
Recommendation: Increase tab visual contrast, add hover states, position tabs in consistent location
Priority: High
Effort: Medium (2-3 days design + implementation)
```

## Advanced Techniques

### Cognitive Load Assessment

Evaluate mental effort required:
- **Perceptual load**: Visual complexity, information density
- **Cognitive load**: Memory requirements, decision points
- **Motor load**: Physical interaction demands

### Mental Model Validation

Compare interface model vs. user expectations:
- Does system structure match user's domain understanding?
- Are metaphors and terminology familiar?
- Do interaction patterns follow established conventions?

### Gulf Analysis

Assess execution and evaluation gaps:
- **Gulf of Execution**: Distance between user intention and system actions
- **Gulf of Evaluation**: Distance between system state and user understanding

## Integration with Research Workflow

### Before Design
- Evaluate early mockups and wireframes
- Test information architecture
- Validate task flow logic

### During Development
- Assess interactive prototypes
- Verify implementation matches specs
- Catch issues before formal testing

### After Launch
- Evaluate new feature additions
- Assess impact of design changes
- Identify optimization opportunities

## Best Practices

### Facilitation Guidelines

1. **Use multiple evaluators**: 3-5 reviewers provide diverse perspectives
2. **Maintain user focus**: Evaluate based on user knowledge, not expert knowledge
3. **Document everything**: Record all observations, even minor hesitations
4. **Avoid solution bias**: Identify problems without prescribing specific fixes
5. **Iterate rapidly**: Cognitive walkthroughs enable fast feedback cycles

### Common Pitfalls to Avoid

- Assuming expert knowledge users don't have
- Skipping granular action breakdown
- Focusing on aesthetics over usability
- Missing feedback evaluation (question 3)
- Evaluating without defined user profile

### Quality Indicators

A thorough cognitive walkthrough includes:
- Clear user profile definition
- Complete action sequence documentation
- All four questions answered for each step
- Specific success/failure stories
- Prioritized, actionable recommendations

## Output Deliverables

### Walkthrough Report Template

```markdown
# Cognitive Walkthrough Report

## Executive Summary
- Tasks evaluated: [count]
- Critical issues: [count]
- Major issues: [count]
- Minor issues: [count]

## User Profile
[Demographics, experience, context]

## Task Analysis
### Task 1: [Name]
**Action sequence**: [enumerated steps]
**Success rate**: [predicted]
**Critical findings**: [list]

## Problem Catalog
[Detailed issue documentation]

## Recommendations
[Prioritized action items]

## Appendix
[Detailed walkthrough notes]
```

## Skill Invocation

Use this skill when:
- Evaluating new interface designs or features
- Assessing learnability for new users
- Identifying task completion barriers
- Validating information architecture
- Conducting lightweight usability assessment without user testing

Reference this skill for cognitive walkthrough guidance, task analysis support, and systematic usability evaluation based on psychological principles.