Iterative Design
Hopper
Description | Design
Cycles
Design Cycle 1
- 5 of 7 users recognized need for a Hopper; 2 were “enthusiastic”
- 3 users didn’t understand constraint arrows; 4 expressed concerns
about the scalability of this representation
- Lingering confusion about the Hopper-Editor distinction motivated removal of all editing capabilities from Hopper
- Approximately half of the users expressed concern that the check-out process
was an extra step that would slow them down
- 5 of 6 users instinctively used drag-and-drop to check activities out of the Hopper
- 3 users suggested there be a visual indicator that activities are checked-out
