top of page

The problem space

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

Designer techniques

  • Discover what the user is doing now

  • Present our requirements gathering findings

Techniques for discovery (How is the user currently accomplishing the task?)

  • Naturalistic observation

  • Survey

  • Focus groups

  • Interviews

Techniques for representing requirements gathering findings (about the user)

  • User characteristics tables

  • Personas

Techniques for representing requirements gathering findings (about the task)

  • Scenarios

  • 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

Recent Posts

See All


Formative evaluation conducted early on in the design process with low-fidelity prototypes Summative evaluation conducted with high-fidelity prototypes or final interface The type of data we collect i


The goal of a novel design: will be better at meeting the needs of the users than the existing design Prototype: an early model of the novel design; manage resources; iterate on the design Low fidelit


bottom of page