usability-testing

Files (3)

• SKILL.md
• _claude-frontmatter-extras.yaml · references/
• task-script-patterns.md · references/

SKILL.md (first lines)

# Usability Testing

Plan and run tests that find usability problems before users hit them in production. Stack-agnostic. Tool-agnostic.

This skill is for testing existing designs or prototypes. For broader discovery research, use `ux-research`. For conversion testing in production, use `cro-optimization`.

---

## When to use

- Before launching a new flow or major redesign
- After a redesign to verify it doesn't introduce new problems
- When analytics show drop-off but you don't know why
- When customer support tickets pattern around specific UI areas
- Pre-launch user validation
- Comparing two design directions

## When NOT to use

- Discovery / generative research (use `ux-research`)
- Live conversion optimization (use `cro-optimization`)
- Mapping the broader experience (use `journey-mapping`)
- Pure quantitative measurement (use `analytics-strategy`)

---

## Required inputs

- The design or prototype to test (functional or near-functional)
- Specific tasks users would do
- The audience (who should be tested)
- Testing infrastructure (moderated tool, unmoderated tool, in-person setup)

---

## The framework: 5 phases

### 1. Define what to test

Don't test the whole product. Test specific tasks.

**Task selection criteria:**

- The task represents a real user goal (not "click around and explore")
- The task has a clear start and end
- The task is achievable in 2 to 10 minutes
- The task is one of: most common, most strategic, most problematic

**Examples of testable tasks:**

> "You want to find a contractor near you who can install a fence. Show me how you'd do that on this site."

> "You're a first-time visitor. You want to understand if this product fits your needs. Walk me through how you'd evaluate it."

> "Your team needs a new tool to manage projects. Use this site to figure out which plan is right for a 12-person team."

**Task framing rules:**

- State the user goal, not the system action ("find a place to stay" not "click the search button")
- Provide context (why are you doing this?)
- Don't reveal the path
- Don't use product terminology in the task framing

### 2. Choose moderated or unmoderated

**Moderated** (live, with researcher):

- Researcher observes and probes in real time
- Best for early-stage prototypes, complex tasks, novel concepts
- Higher cost, smaller sample (5 to 8 participants typical)
- Catches surprises and probe deeper

**Unmoderated** (recorded, asynchronous):

- Participant completes alone, often via tool (UserTesting, Maze, Lookback)
- Best for stable designs, simple tasks, larger sample
- Lower cost, larger sample (15 to 30 participants typical)
- Catches patterns at scale, less depth per session

For most teams: moderated for early/critical decisions, unmoderated for ongoing validation.

### 3. Recruit

Target audience - not just convenience.

**Recruit criteria:**

- Match real users (target audience, not just "anyone")
- Mix of experience levels with the product (new and existing if applicable)
- Mix of relevant device types (mobile, desktop, tablet if relevant)
- Exclude friends, family, employees

**Sample size:**

- Moderated: 5 to 8 participants (Nielsen's "5 users find 85% of usability issues" for the most common segment)
- Unmoderated: 15 to 30 participants (more participants compensate for less probing)
- Multi-segment testing: 5 to 8 per segment

### 4. Run the test

**Pre-task setup:**

- Confirm recording works
- Brief participant (purpose, anonymity, recording, "no wrong answers")
- Get verbal consent
- Have participant share screen if remote

**Moderated session structure:**

1. **Warm-up** (2 to 3 min). Easy questions to put participant at ease.
2. **Pre-test questions** (3 to 5 min). Background context, current behavior with similar products.
3. **Task 1** (5 to 10 min). Describe task. Have participant attempt while thinking aloud.
4. **Post-task questions** (1 to 2 min). What was easy/hard? Anything confusing?
5. **Repeat for tasks 2, 3, 4** (typically 3 to 5 tasks per 60-minute session).
6. **Overall debrief** (5 to 10 min). General reactions, comparisons to alternatives, anything else.
7. **Close** (2 min).

**Moderation principles:**

From rampstackco/claude-skills, MIT.

More from rampstackco/claude-skills