# Requirements Elicitation

The collaborative practice of drawing out and confirming needs, constraints, rules, and knowledge relevant to a proposed change.

- Type: practice
- Domain: Delivery & agility
- Level: Intermediate
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/requirements-elicitation/>)

## What it means

Requirements elicitation is the deliberate discovery of information from stakeholders, users, documents, data, existing systems, and observation to understand needs and constraints. It is not simply asking people what they want; elicited information must be explored, recorded, and confirmed before it becomes a reliable requirement.

## Why it matters

Important needs are often tacit, conflicting, distributed, or expressed as preferred solutions. Elicitation exposes context and exceptions early, reduces misunderstanding, and gives analysis a more credible evidence base.

## When to use it

Use it when defining or changing products, workflows, policies, integrations, and regulated behavior. Select techniques based on stakeholders and risk; avoid workshop-heavy process when direct observation, product data, or a small experiment answers the question better.

## How it works

1. Define the decision, scope, existing knowledge, gaps, and relevant participants.
2. Choose techniques such as interviews, observation, workshops, document analysis, or interface analysis.
3. Explore goals, current behavior, rules, exceptions, constraints, and conflicting perspectives.
4. Record findings separately from untested solution assumptions.
5. Confirm the captured information with appropriate sources.
6. Feed confirmed findings into analysis, prioritization, and validation.

## A practical example

For a refund workflow, a team interviews support and finance, observes agents, reviews policy and ticket data, and traces payment-system exceptions. Confirmation reveals that a requested approval screen addresses only one of three underlying control needs.

## Where it breaks

Participants may omit tacit knowledge, recall inaccurately, or represent only one segment. Facilitation can introduce bias, and elicitation cannot predict every emergent need. Findings still require analysis and validation against intended outcomes.

## Common mistakes

- Asking only what features stakeholders want.
- Using one senior stakeholder as the sole source of truth.
- Confusing notes from a session with confirmed requirements.
- Choosing workshops by habit instead of matching technique to the information need.

## Sources

1. [Business Analysis Knowledge Areas](<https://www.iiba.org/knowledgehub/the-business-analysis-standard/5-applying-business-analysis-tasks/5-3-business-analysis-knowledge-areas/>) — International Institute of Business Analysis · Professional standard
2. [ISO/IEC/IEEE 29148:2018 — Requirements Engineering](<https://www.iso.org/standard/72089.html>) — International Organization for Standardization · International standard

## Related topics

- [User Interviews](<https://wiki.soroush.uk/topic/user-interviews/>)
- [Product Requirement](<https://wiki.soroush.uk/topic/product-requirement/>)
- [Requirements Analysis](<https://wiki.soroush.uk/topic/requirements-analysis/>)
