Description
Turn analysed research into user need statements, user stories or 'shall' requirements, add extrapolated needs, organise by task, prioritise and validate with users.
This step converts research data into a form product and engineering teams can act on. User needs are written in users' own words as 'I need/want/expect to... so that...', optionally with role, trigger ('When...') and constraint ('Because...'); they are high level, stable and never 'done'. User stories derive from needs with actor, narrative and goal; a story without a clear goal questions the feature. Hartson and Pyla add rigour by pulling every need-bearing work-activity note, generalising narrow statements, adding extrapolation requirements for obvious unstated needs, recording implied system requirements, and for high-rigour work writing 'shall' statements with rationale under feature headings. Stories are organised under a task hierarchy to check completeness, prioritised separately (for example by MVP release), held in a backlog with acceptance criteria, and walked through with users per work role.
Attributes
- Discipline
- Qualitative Analysis & Synthesis
- Loss type
- Active
- Stage
- Definition
- Data
- Analytical / expert
- Effort
- Days
Steps
- Pull out research notes that express or imply a user need.
- Write each as a need statement ('I need... so that...') in users' words, or as a role-voiced story ('As a... I want... so that...').
- Generalise narrow statements and add extrapolation requirements for obvious unstated needs, recording implied system requirements.
- For high-rigour projects, write 'shall' statements with rationale and notes under two-level feature headings.
- Organise needs and stories under a task hierarchy or by persona, stage or theme to check completeness.
- Prioritise separately, for example by MVP releases, and record them in a backlog with priority, persona, functional requirement and acceptance criteria.
- Walk through the set with client representatives and users for each work role.
Sources
- The UX Book (Hartson & Pyla, 2019)
- User Research: A Practical Guide to Designing Better Products and Services (Marsh, 2018)
- User Research (Marsh, 2022)
Also known as
- User needs statements
- User needs backlog
- UX user stories
- Extrapolation requirements
- GDS user needs
- UX design requirements extraction
Categories
- User Research
- Qualitative Analysis & Synthesis