Usual development
stage: During any building stage from the start of on-screen
design until it reaches code freeze or design freeze:
- Initial painted screens or working prototype
- All stages of development
- Until shortly before code freeze (or design freeze)
What this is: Test initial prototypes through
finished builds. Test findings should:
- Identify key user problems and issues
- Suggest solutions
- Find Quick Wins (that is, low cost but high value solutions)
- Learn the larger, long-term issues
- Help prioritize the use of remaining time and resources.
Average turnaround time: One week total time,
by one usability specialist, for all services. This is faster and
cheaper than traditional usability tests, which typically take about
30 days.
With faster and cheaper tests:
- Each project can include more tests, which
produces faster learning, includes more groups of users and makes
greater progress.
- In a 5-6 month fast-time-to-market project, 3 to 4 usability
tests is not unusual.
- In large and open projects, like a major Enterprise Web site,
2 or more tests a month can be a normal schedule.
- This specialist averages 3 to 4 tests each month, with a range
of tests scheduled at any one time.
How it works: While each test is customized for
its team and their development stage, a typical test cycle has three
phases:
Phase 1: Before the test
- Choose a test date and location. Without
these, users can't be recruited.
- Select high-priority target users, determine their characteristics
and recruit them.
- Prepare the test kit for, and with, the development team.
Phase 2: Testing. A typical usability test of a single user
includes:
- Greet the user
- Pre-use questionnaire (user history, skills, experience, etc.)
- Talkaloud instructions (primarily used in qualitative tests)
- Do tasks / Record data
- Post-use questionnaire (user can rate, rank, compare, etc.)
- Debrief the user
- Pay user (if an external user, not an employee)
Phase 3: Data analysis and reporting. This depends on each
team:
- Detailed written report (almost always)
- Presentation (optional)
- Video highlights tape (optional)
- Compilation of several tests in one area (optional)
- Construction of a "reference design" based on test
findings (optional)
Key knowledge questions: To maximize value, do
only what's needed and avoid what doesn't contribute to client and
user success:
- Measure customer (or user) success
- Learn the users' problems
- Develop solutions
- Increase customer (or user) value:
- Help the team achieve its business and customer success objectives
How to get it right: Contact
us.
Top |
