Requirements Elicitation
The collaborative practice of drawing out and confirming needs, constraints, rules, and knowledge relevant to a proposed change.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/requirements-elicitation/
01What 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.[1][2]
02Why 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.
03When 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.
04How it works
- Define the decision, scope, existing knowledge, gaps, and relevant participants.
- Choose techniques such as interviews, observation, workshops, document analysis, or interface analysis.
- Explore goals, current behavior, rules, exceptions, constraints, and conflicting perspectives.
- Record findings separately from untested solution assumptions.
- Confirm the captured information with appropriate sources.
- Feed confirmed findings into analysis, prioritization, and validation.
05A 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.
06Where 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.
07Sources
- Business Analysis Knowledge AreasInternational Institute of Business Analysis · Professional standardBusiness Analysis Knowledge Areas
- ISO/IEC/IEEE 29148:2018 — Requirements EngineeringInternational Organization for Standardization · International standardISO/IEC/IEEE 29148:2018 — Requirements Engineering