Research / Structure / Validation / 06
Test, synthesize, decide
Run a five-person usability study, separate signals from anecdotes, and prioritize the next iteration.
Before you begin
By the end, you can…
- Write neutral usability tasks
- Identify severity using impact and frequency
- Turn observations into prioritized changes
01 / Understand
A usability test evaluates the design
Five thoughtful sessions can reveal many severe interaction problems, but the number is not a universal law. Recruit people who resemble the intended audience and test representative tasks.
Avoid teaching the interface through the task. “Find out whether this plan supports guests” is better than “Click Pricing, then compare plans.” Ask participants to think aloud without turning the session into an interview.
02 / Apply
Findings need a decision
Record observable behavior: path taken, hesitation, error, recovery, and outcome. A participant saying “I like it” is feedback; failing to find the save action is usability evidence.
Prioritize by severity, frequency, reach, and confidence. Recommend the smallest change that addresses the cause, then retest. Do not convert every comment into a feature.
03 / Make
Your studio task
Make — Facilitate five task-based sessions and turn observations into ranked changes.
- Write three realistic, neutral tasks.
- Run sessions with five representative participants where practical.
- Log observable behavior and quotes separately.
- Rank findings, revise the highest-severity issue, and retest it.
Every recommendation points to evidence, severity, frequency, and product intent.
04 / Check