/usability-frameworks

name: usability-frameworks
description: "Usability testing methodology, Nielsen's heuristics, and usability metrics. Use when planning usability tests, evaluating UI against heuristics, writing test scripts, or measuring task success rates. Trigger on: 'run a usability test', 'heuristic evaluation', 'usability test script', 'task success rate', 'think-aloud protocol'."

Usability Frameworks

Comprehensive frameworks and methodologies for planning, conducting, and analyzing usability tests to improve user experience.

When to Use This Skill

**Auto-loaded by agents**:

• `research-ops` - For usability testing and heuristic evaluation

**Use when you need**:

• Planning usability tests
• Conducting user testing sessions
• Evaluating interface designs
• Identifying usability problems
• Testing prototypes or live products
• Applying Nielsen's heuristics
• Measuring usability metrics

Core Concepts

What is Usability Testing?

Usability testing is a method for evaluating a product by testing it with representative users. Users attempt to complete typical tasks while observers watch, listen, and take notes.

**Purpose**: Identify usability problems, discover opportunities for improvement, and learn about user behavior and preferences.

**When to use**:

• Before development (testing prototypes)
• During development (iterative testing)
• After launch (validation and optimization)
• Before major redesigns

The Five Usability Quality Components (Jakob Nielsen)

1. **Learnability**: How easy is it for users to accomplish basic tasks the first time? 2. **Efficiency**: How quickly can users perform tasks once they've learned the design? 3. **Memorability**: Can users remember how to use it after time away? 4. **Errors**: How many errors do users make, how severe, and how easily can they recover? 5. **Satisfaction**: How pleasant is it to use the design?

Usability Testing Methodologies

1. Moderated Testing

**Setup**: Researcher guides participants through tasks in real-time **Location**: In-person or remote (video call)

**Best for**:

• Early-stage prototypes needing clarification
• Complex products requiring guidance
• Exploring "why" behind user behavior
• Uncovering emotional reactions

**Process**:

1. Welcome and set expectations 2. Pre-task questions (background, experience) 3. Task scenarios with think-aloud protocol 4. Post-task questions and discussion 5. Wrap-up and thank you

**Advantages**:

• Rich qualitative insights
• Can probe deeper into issues
• Observe non-verbal cues
• Clarify misunderstandings immediately

**Limitations**:

• More time-intensive (30-60 min per session)
• Researcher bias possible
• Smaller sample sizes
• Scheduling logistics

2. Unmoderated Testing

**Setup**: Participants complete tasks independently, recorded for later review **Location**: Remote, on participant's own schedule

**Best for**:

• Mature products with clear tasks
• Large sample sizes needed
• Quick turnaround required
• Benchmarking and metrics

**Process**:

1. Automated instructions and consent 2. Participants record screen/audio while completing tasks 3. Automated post-task surveys 4. Researcher reviews recordings later

**Advantages**:

• Faster data collection
• Larger sample sizes
• More natural environment
• Lower cost per participant

**Limitations**:

• Can't probe or clarify
• May miss nuanced insights
• Technical issues harder to resolve
• Participants may skip think-aloud

3. Hybrid Approaches

**Combination methods**:

• Moderated first impressions + unmoderated task completion
• Unmoderated testing + follow-up interviews with interesting cases
• Moderated pilot + unmoderated scale testing

Nielsen's 10 Usability Heuristics

Quick reference for evaluating interfaces. See `references/nielsens-10-heuristics.md` for detailed explanations and examples.

1. **Visibility of system status** - Keep users informed 2. **Match between system and real world** - Speak users' language 3. **User control and freedom** - Provide escape hatches 4. **Consistency and standards** - Follow platform conventions 5. **Error prevention** - Prevent problems before they occur 6. **Recognition rather than recall** - Minimize memory load 7. **Flexibility and efficiency of use** - Accelerators for experts 8. **Aesthetic and minimalist design** - Remove irrelevant information 9. **Help users recognize, diagnose, and recover from errors** - Plain language error messages 10. **Help and documentation** - Provide when needed

Think-Aloud Protocol

What It Is

Participants verbalize their thoughts while completing tasks, providing real-time insight into their mental model.

Types

**Concurrent think-aloud**: Speak while performing tasks

• More natural thought flow
• May affect task performance slightly

**Retrospective think-aloud**: Review recording and explain thinking after

• Doesn't disrupt natural behavior
• May forget or rationalize thoughts

Facilitating Think-Aloud

**Prompts to use**:

• "What are you thinking right now?"
• "What are you looking for?"
• "What would you expect to happen?"
• "Is this what you expected?"

**Don't**:

• Ask leading questions
• Provide hints or solutions
• Interrupt natural flow too often
• Make participants feel tested

See `references/think-aloud-protocol-guide.md` for detailed facilitation techniques.

Task Scenario Design

Good task scenarios are critical to meaningful usability test results.

Characteristics of Good Task Scenarios

**Realistic**: Based on actual user goals **Specific**: Clear endpoint/success criteria **Self-contained**: Provide all necessary context **Actionable**: Clear starting point **Not prescriptive**: Don't tell them how to do it

Example Transformation

**Poor**: "Click on the 'My Account' link and change your password"

• Too prescriptive, tells them exactly where to click

**Good**: "You've heard about recent security breaches and want to make your account more secure. Update your