Cognitive Walkthrough Review

Template Overview

A cognitive walkthrough evaluates whether a first-time user can successfully complete a specific task without formal training. Evaluators analyze every discrete interface action against four foundational psychological questions formulated by Wharton, Rieman, Lewis, and Polson. This template provides a structured step-by-step matrix to document cognitive bottlenecks, missing affordances, and confusing feedback loops before product releases.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Cognitive Walkthrough: [Task Flow Name]"
date: [YYYY-MM-DD]
evaluators: ["[[Evaluator 1]]", "[[Evaluator 2]]"]
target_user_persona: "[Novice Knowledge Worker / Non-Technical Admin]"
happy_path_steps_count: [Number]
tags: [ux-research, cognitive-walkthrough, usability, inspection-method, mental-models]
---

# Cognitive Walkthrough Review — [Task Flow Name]

## 1. Walkthrough Setup & Task Definition
- **Target Task:** `[e.g., Configure local audio recording and export markdown note]`
- **User Background & Knowledge:** User is comfortable with Markdown but has never configured local speech-to-text models.
- **Required Preconditions:** User has downloaded the application to macOS and opened the onboarding window.

## 2. The Four Cognitive Inspection Questions
1. **Intent Question:** Will the user try to achieve the right effect?
2. **Availability Question:** Will the user notice that the correct action is available?
3. **Association Question:** Will the user associate the correct action with the intended effect?
4. **Feedback Question:** If the correct action is performed, will the user see that progress is being made toward their goal?

## 3. Step-by-Step Cognitive Inspection Matrix
| Step # | Action Description | Q1: Intent Formed? (Y/N) | Q2: Control Noticed? (Y/N) | Q3: Action Associated? (Y/N) | Q4: Progress Recognized? (Y/N) | Identified Cognitive Barrier & Recommendation |
|---|---|---|---|---|---|---|
| Step 1 | Click 'Start Recording' button | Y | Y | Y | Y | Clear red microphone icon with prominent placement. Pass. |
| Step 2 | Select model weight size | Y | N | N | Y | Dropdown hidden inside accordion settings. User doesn't know what 'Base' vs 'Medium' means. |
| Step 3 | Click 'Transcribe Audio' | Y | Y | Y | N | Progress bar lacks percentage; user assumes application froze during neural warm-up. |
| Step 4 | Save Markdown to vault | Y | N | Y | Y | Export button styled as secondary gray text link instead of primary action. |

## 4. Deep-Dive Cognitive Barrier Analysis
- **Barrier 1: Jargon in Model Selection (Step 2)**
  - *Failure Mode:* Q2 and Q3 fail. Users do not understand parameters like `ggml-large-v3-q5_0`.
  - *Remediation:* Replace technical filenames with human labels: `Fastest (Basic)`, `Balanced (Recommended)`, `Maximum Precision`.
- **Barrier 2: Silent Neural Warm-up Latency (Step 3)**
  - *Failure Mode:* Q4 fails. When Apple Silicon initializes the Core ML model, the UI displays zero animation for 2.8 seconds.
  - *Remediation:* Add immediate pulsing spinner with text: `Initializing Apple Neural Engine...`.

## 5. Prioritized Design Action Items
- [ ] Relabel model selection options with clear speed vs. precision badges.
- [ ] Implement immediate visual spinner and progress percentage indicator during transcription.
- [ ] Elevate 'Export to Markdown' to prominent primary button upon transcription completion.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Cognitive Walkthrough: Local Markdown Vault Connection"
date: 2026-10-09
evaluators: ["[[Sarah Jenkins]]", "[[Tomás Silva]]"]
target_user_persona: "New Obsidian Note-Taker"
happy_path_steps_count: 4
tags: [ux-research, cognitive-walkthrough, usability, inspection-method, mental-models]
---

# Cognitive Walkthrough Review — Local Markdown Vault Connection

## 1. Walkthrough Setup & Task Definition
- **Target Task:** Link an existing local Obsidian directory to Oyma for automatic meeting note exports.
- **User Background:** Understands local folder paths; expects zero proprietary cloud syncing.

## 2. Step-by-Step Cognitive Inspection Matrix
| Step # | Action Description | Q1: Intent? | Q2: Noticed? | Q3: Associated? | Q4: Feedback? | Identified Cognitive Barrier & Recommendation |
|---|---|---|---|---|---|---|
| Step 1 | Open Settings > Storage | Y | Y | Y | Y | Clear sidebar navigation icon. Clean pass. |
| Step 2 | Click 'Choose Vault Directory' | Y | Y | Y | Y | Native macOS file picker modal launches instantly. |
| Step 3 | Grant local folder permission | Y | Y | N | Y | macOS security modal can startle users. Add helper text explaining why local read/write access is needed. |
| Step 4 | Confirm connected vault status | Y | Y | Y | Y | Displays green status badge: `Connected to /Documents/ObsidianVault`. |

## 3. Deep-Dive Cognitive Barrier Analysis
- **macOS System Security Modal Clarification:** Users hesitate when macOS prompts: `Oyma would like to access files in your Documents folder`.
- **Remediation:** Display an explanatory pre-permission screen stating: `Oyma stores transcripts directly in your personal folder. Your notes never leave this Mac.`

## 4. Prioritized Design Action Items
- [ ] Add pre-permission dialog explaining local macOS directory access before opening system picker.
- [ ] Display recently selected folder path directly in settings card header.
- [ ] Test refined flow with 5 new users during next usability sprint.

When to Use and When to Avoid

When to Use

• Use during early wireframe or interactive prototype stages before conducting expensive user testing.
• Use when evaluating the discoverability of complex multi-step workflows like exports, integrations, or security keys.
• Use to identify subtle cognitive load failures that developers often overlook.

When to Avoid

• Avoid using to measure subjective visual aesthetics or emotional brand appeal.
• Avoid using as a substitute for real empirical user testing with actual target customers.

On-Device AI Integration

Summarize your recording in Oyma with this local instruction:

Analyze the cognitive walkthrough inspection matrix:
1. Identify all steps where Question 2 (availability) or Question 3 (association) failed.
2. Formulate specific UI copy and layout recommendations to resolve identified mental model barriers.
3. Calculate the walkthrough pass rate percentage across all evaluated steps.
Output in structured Markdown.

Your data remains securely on your Mac with zero cloud exposure.