Purpose
Choose and plan the right elicitation mix across interviews, questionnaires, workshops, observation, and prototypes.
Use when
- requirements are incomplete or unreliable
- stakeholders need structured elicitation
- you must decide how to gather evidence, not just what the requirements are
Inputs
- project or problem context
- goals and constraints
- known stakeholders, systems, and documents
- level of formality required
Procedure
- Clarify elicitation objectives and scope.
- Decide which techniques fit the context and why.
- Produce interview plans and question banks where needed.
- Produce workshop agenda and facilitation plan where needed.
- Produce questionnaire or observation plan where needed.
- Recommend prototypes/mock-ups if textual requirements are insufficient.
- Consolidate findings into a structured requirements discovery pack.
- Highlight contradictions, missing stakeholders, and follow-up actions.
Outputs
- elicitation strategy
- interview packs
- workshop plan
- questionnaire or observation plan
- prototype recommendation
- findings summary
Guardrails
- Explicitly separate fact, inference, and assumption.
- Prefer evidence-backed conclusions over polished speculation.
- Where conflict exists, record it rather than smoothing it away.
- Produce artifacts that can be inspected, edited, and reused.
Completion criteria
- deliverable pack exists
- tradeoffs are explicit
- unknowns are logged
- next decisions are obvious