User Days
by Markus Latzina, SAP AG, Usability Engineering Center – Last changed on 06.02.2003
This paper is outdated.
Basics | Overview and Effort | Working Materials
Basics
Why?
Create a usable product by involving the user at an early stage and testing with the user continuously during the design and realization phases.
When?
You can start testing once you have an initial paper prototype.
How?
Invite future users:
- Have them test your prototypes and get their feedback
- Learn more about their tasks
Where and Which Kind of User Day?
|
User Day Type
|
OFF-Lab
|
Lab
|
On-site
|
|---|---|---|---|
| Single Sessions | Sequential Testing | Usability Lab Test | Site Visit with prototype or alpha testing |
| Parallel Sessions | Parallel Testing |
Overview and Effort
|
Activity
|
Effort
|
|---|---|
| Planning Meeting | ~3h |
| Preparation | depends on type of User Day |
| User Day | depends on type of User Day |
| Debriefing | ~3h |
Planning Meeting
- What are the areas we need user feedback on?
- What have we got that can be tested? Prototype? First electronic version?
- Which users or customers do we invite?
avoid hierarchical or competitive relations - What type of User Day is appropriate?
Preparation
- Determine customer names, and room requirements
- Preparation of test: prepare system or prepare paper prototypes
- Training for test methodology and Usability Round Table
User Day
|
Method
|
Comments
|
|---|---|
| Parallel Testing | ~3/4 day test and discussion; several customers |
| Sequential Testing | several half-days; single test users |
| Usability Lab Testing | (2-3 days in Lab; UEC test leader support) |
| On-site Testing | several site visits; present prototype |
Debriefing
- Consolidate results
- Prioritize problems
- Identify solutions, collect design ideas
- Update user roles and scenarios
Working Materials
- User Day Toolkit: Basic Principles of a User Day, self-study text with detailed hints for all phases
- SAP UIDs will find more information on internal Websites
