|
Comparative
Tests |
Prototype
Tests |
Interactive
Tests |
Validation
Tests |
| When |
Pre-design,
to uncover market need |
In
early design,
to test design ideas |
During
design, to ensure designs stay on target |
Before Re-design to
uncover UI issues At Release,
to measure success
|
| Good
for |
Comparing:
- Features
- Usefulness
- Ease of Use
- Problems |
Exploring:
- Design concepts
- Terminology
- Navigation
- Structure |
Iterating
Testing:
- Interactions
- Animations
- Integrations
- Processes
|
Verifying:
- Baseline usability
- Overall Experience
- Success metrics |
| Goal |
Guide design
- Sets features
- Identifies needs
- Spots problems & solutions |
Test structure
- User Goals
- Mental Models
- Architecture
|
Inform design
- Integrations
- Iterations
- Interactions |
Set benchmarks
- Performance
- Actual usage
- Total process |
| Benefit |
Fewer changes
- Features are based
on market
- 10-20 users
- 60-90 mins./test |
Lowest $
- Changes are made before
coding
- 3-4 users
- 30-60 mins./test
|
Low $$
- Changes are made on
components
- 5-8 users
- 60-90 mins./test |
High $$$
- Changes are made before
release
- 8-12 users
- 90-120 mins./test |
| Challenges |
Not enough
- Features based on market
only
- Innovation avoidance |
Lower validity
- Incomplete experience
- Fewer users |
Incompleteness
- Partial experience
- Fewer elements |
Too Late
- Costly changes or no
changes
- Unmet customer need |
