JuniorTechnicalRequirements
Which elicitation techniques do you use and when?
Try answering first
Model answer
I choose the technique by the question I need answered.
- Interviews for deep, individual views, especially with key stakeholders or when topics are sensitive.
- Workshops to align many stakeholders quickly and resolve conflicts in the room.
- Observation (job shadowing) to see how work really happens, which often differs from what people describe.
- Document analysis to learn existing rules, forms and reports before meeting people.
- Surveys to gather input from a large, dispersed group, when answers can be closed-ended.
- Prototyping to make requirements concrete and get fast feedback on ideas that are hard to describe.
In practice I combine them: read documents first, interview a few people, then run a workshop to confirm and prioritize. I also record who said what, so each requirement stays traceable to a stakeholder.
Key points
- Match the technique to the question and the audience
- Observation reveals the real process, interviews reveal intent
- Combine techniques and keep requirements traceable
Likely follow-ups
- When would you choose a survey over interviews?
- How do you prepare for a stakeholder interview?
Common mistakes
- Relying on a single technique for every situation
- Asking leading questions that confirm what you already assume