Requirements Traceability Matrix for UX

Description

Links each research finding to requirements, design decisions, implementation items and verification tests so user insights are not lost between research and development.

The treatise describes a once-productive exchange between UX and requirements engineering: UX contributed ethnographic methods, requirements engineers contributed formal specification, traceability matrices and verification procedures. That intersection dissolved, and UX now produces user stories, JTBD statements and journey maps rarely integrated with formal requirements, creating a gap where insights are lost in translation. A UX traceability matrix restores the link: each requirement traces backwards to evidence (study, participant, observation) and forwards to design artefacts, tickets and acceptance tests, including usability acceptance criteria. Bidirectional traceability makes it possible to see which insights were never implemented and which features lack evidence.

Attributes

Loss type
Unmigrated
Effort
Days

Steps

  1. Assign identifiers to research findings and store them in a repository.
  2. Write requirements, including measurable usability requirements, each citing finding IDs.
  3. Link requirements to design artefacts and backlog items.
  4. Define verification for each requirement (usability test criterion, analytics metric).
  5. Maintain the matrix through releases, flagging orphan findings and unsupported features.
  6. Review coverage at release gates.

Sources

  • Lost Methods in UX — A Complete Treatise (Gopinath)
  • Gotel OCZ & Finkelstein ACW (1994) An analysis of the requirements traceability problem. ICRE
  • Sommerville I & Sawyer P (1997) Requirements Engineering: A Good Practice Guide

Also known as

  • UX requirements traceability
  • Research-to-requirements traceability

Categories

  • Research Operations
  • Research Design & Rigor