User Testing
A research method where real users interact with a product or prototype while researchers observe their behavior, collect feedback, and identify usability issues before or after launch.
Definition
User testing observes real users interacting with a product, prototype, or design to identify usability issues, validate assumptions, and gather feedback. Unlike surveys that ask what users think, testing reveals what users actually do.
Types of User Testing
Moderated Testing
A researcher guides participants through tasks in real-time, asking follow-up questions. Higher quality insights but more time-intensive.
Unmoderated Testing
Participants complete tasks independently using testing software. Scales better but lacks ability to probe deeper.
Prototype Testing
Tests designs before development. Validates concepts using Figma, Sketch, or other design tool prototypes.
Live Product Testing
Tests features in production. Captures real user behavior with actual product functionality.
When to Use User Testing
Pre-Development
Validate design concepts before building. Catch usability issues early when changes are cheap.
During Development
Test with working prototypes. Identify friction in actual interactions.
Post-Launch
Understand how users actually use features. Find unexpected behavior patterns.
Before Major Changes
Validate redesigns before rolling out. Reduce risk of negative user impact.
Key Metrics
- Task completion rate — Can users accomplish the goal?
- Time on task — How long does it take?
- Error rate — How often do users make mistakes?
- User satisfaction — How do they feel about the experience?
Tools for User Testing
- Maze — Unmoderated prototype testing with Figma integration
- Sprig — In-product research with contextual surveys
Frequently Asked Questions
How many users do I need to test with?
5-8 users typically uncover 80% of usability issues. More users help for quantitative metrics but show diminishing returns for qualitative insights.
Should I test prototypes or live products?
Both. Test prototypes to validate before building. Test live products to understand real usage and find issues analytics miss.
What’s the difference between user testing and A/B testing?
User testing reveals why through observation and feedback. A/B testing reveals what works through statistical comparison. They’re complementary.