The goal of requirements gathering is to understand the problem space
Who are the users?
When, where, why, and how do they currently accomplish the task?
What do users perceive are problems with their current practices?
User's wish list for improving how they currently accomplish their task?
The main pitfall of requirements gathering
Designers start designing alternatives when they do not completely understand the task, user, or how the user currently accomplishes the task
Discover what the user is doing now
Present our requirements gathering findings
Techniques for discovery (How is the user currently accomplishing the task?)
Techniques for representing requirements gathering findings (about the user)
User characteristics tables
Techniques for representing requirements gathering findings (about the task)
Essential use case scenarios
Hierarchical task analysis
Current UI critique
Techniques for representing requirements gathering findings (about the eventual novel interface)
Usability principles that help us evaluate our eventual novel interface