usability-testing
Installation
SKILL.md
Usability Testing
Scope
Covers
- Designing task-based usability studies tied to a specific product decision
- Testing live flows, prototypes, and “faked” implementations (fake door, Wizard of Oz)
- Running moderated sessions (remote or in-person) and capturing high-quality evidence
- Turning findings into a prioritized fix list (including high-ROI microcopy/CTA improvements)
When to use
- “Create a usability test plan and script for .”
- “We need to test a prototype with 5–8 users next week.”
- “Validate a value proposition before building (fake door / Wizard of Oz).”
- “Help me synthesize usability findings into a prioritized backlog.”
When NOT to use
- You need statistically reliable estimates or causal impact (use analytics/experimentation)
- You need open-ended discovery (“what problems do users have?”) without a specific flow to evaluate (use
conducting-user-interviews)
Related skills
More from liqiongyu/lenny_skills_plus
problem-definition
Define a product problem: problem statement, JTBD, alternatives, evidence, metrics. See also: writing-prds (solution spec).
13giving-presentations
Plan and deliver presentations: brief, narrative, slide outline, Q&A bank, rehearsal plan. See also: written-communication (async writing).
13competitive-analysis
Produce a Competitive Analysis Pack (alternatives map, landscape, battlecards, monitoring plan).
11pricing-strategy
Create a Pricing Strategy Pack (value metric, packaging, price points, conversion mechanics, rollout).
11startup-ideation
Generate and evaluate startup ideas: theses table, scorecard, top idea brief, validation plan. See also: startup-pivoting (existing product).
11writing-prds
Write a decision-ready PRD for cross-functional alignment. See also: writing-specs-designs (build-ready spec).
11