Collecting and Analyzing User Insights: Approaches for Identifying and Documenting User Requirements

Notes

## Bibliographic Reference

Peissner, M., Pollmann, K., & Fronemann, N. (2021). Collecting and analyzing user insights: Approaches for identifying and documenting user requirements. In G. Salvendy & W. Karwowski (Eds.), *Handbook of Human Factors and Ergonomics* (5th ed., Chapter 37, pp. 960-971). John Wiley & Sons.

## BibTeX

```bibtex
@incollection{peissner2021userinsights,
  author = {Peissner, Matthias and Pollmann, Katharina and Fronemann, Nora},
  title = {Collecting and Analyzing User Insights: Approaches for Identifying and Documenting User Requirements},
  booktitle = {Handbook of Human Factors and Ergonomics},
  editor = {Salvendy, Gavriel and Karwowski, Waldemar},
  publisher = {John Wiley \& Sons},
  year = {2021},
  edition = {5th},
  chapter = {37},
  pages = {960--971},
  doi = {10.1002/9781119636113.ch37}
}
```

## Summary

Comprehensive guide to user requirements collection and documentation methods in human-centered design. Covers:

- **User Requirements Definition**: User needs and constraints related to context of use that guide solution development (per ISO 25065)
- **Context of Use**: Users (characteristics, capabilities, limitations), goals/tasks, environments (physical, social, technical, organizational)
- **Three Purposes of Requirements Documents**: Understanding users (personas, empathy maps), defining scope (scenarios, use cases, opportunity areas), guiding design (design principles)
- **Documentation Formats**: Context of use description (ISO 25063), personas, empathy maps, scenarios, use cases, opportunity areas, design principles
- **Collection Methods**:
  - Hierarchical Task Analysis (HTA) for task decomposition
  - Interviews (structured, semi-structured, unstructured)
  - Contextual inquiry (observation + interview in natural context)
  - Focus groups (6-12 participants, synergy effects)
  - Participatory design workshops (users as co-designers)
  - Cultural probes (self-documentation kits for intimate contexts)
  - Ethnography (long-term immersion)

Key distinction: Functional requirements (what system must do) vs. non-functional requirements (qualities like usability, accessibility, security).

## Routing Note

Primary owner: human-centered-design-kb (foundational HCD methods chapter)
Cross-reference: Relates strongly to situation-awareness (SA requirements inform user requirements), mental-workload (workload constraints as non-functional requirements)

Related Articles

Notes