The learner can match an elicitation method (interview, observation, document analysis, workshop, survey, prototyping) to a given situation and justify the choice.
Six elicitation methods and when to use them
Six elicitation methods and when to use them
Elicitation is the process of drawing out requirements from stakeholders and other sources. Each method has its own strengths, and choosing the right one for the situation is a core analyst skill.
Interview — a structured or semi-structured conversation with one stakeholder (or a small group). Best for: exploring a new domain, understanding decision-makers' goals, or digging into sensitive topics. Weakness: time-intensive; you can only reach one person at a time, and stakeholders sometimes say what they think you want to hear.
Observation (also called job shadowing) — you watch users doing their actual work. Observation can be passive (watch without interrupting) or active (ask clarifying questions while watching). Best for: uncovering tacit knowledge and workarounds that stakeholders have forgotten to mention, or that they cannot articulate. Weakness: the observer effect — people may change behavior when watched.
Document analysis — reviewing existing materials: policies, manuals, forms, reports, legacy specs, org charts. Best for: understanding the current state quickly, especially when key people are unavailable or the domain is regulated. Weakness: documents may be outdated or incomplete.
Workshop (facilitated session) — structured meeting with multiple stakeholders at once. Best for: resolving conflicting requirements, building shared understanding, or producing a deliverable (e.g. a process map) collaboratively. Weakness: requires skilled facilitation; dominant voices can suppress quieter ones.
Survey / questionnaire — structured questions sent to many respondents. Best for: gathering quantitative data or opinions from a large, geographically distributed audience. Weakness: low response rates; no follow-up possible on ambiguous answers.
Prototyping — creating a mockup, wireframe, or working model to elicit feedback. Best for: clarifying UI/UX requirements, or when stakeholders struggle to articulate needs in the abstract. Weakness: stakeholders may treat a prototype as a finished product and resist changes later.
A common beginner mistake is relying only on interviews. Real-world elicitation almost always combines several methods: for example, document analysis to prepare interview questions, then a workshop to resolve conflicts surfaced by the interviews.
Lesson notes
Six elicitation methods and when to use them
Elicitation is the process of drawing out requirements from stakeholders and other sources. Each method has its own strengths, and choosing the right one for the situation is a core analyst skill.
Interview — a structured or semi-structured conversation with one stakeholder (or a small group). Best for: exploring a new domain, understanding decision-makers' goals, or digging into sensitive topics. Weakness: time-intensive; you can only reach one person at a time, and stakeholders sometimes say what they think you want to hear.
Observation (also called job shadowing) — you watch users doing their actual work. Observation can be passive (watch without interrupting) or active (ask clarifying questions while watching). Best for: uncovering tacit knowledge and workarounds that stakeholders have forgotten to mention, or that they cannot articulate. Weakness: the observer effect — people may change behavior when watched.
Document analysis — reviewing existing materials: policies, manuals, forms, reports, legacy specs, org charts. Best for: understanding the current state quickly, especially when key people are unavailable or the domain is regulated. Weakness: documents may be outdated or incomplete.
Workshop (facilitated session) — structured meeting with multiple stakeholders at once. Best for: resolving conflicting requirements, building shared understanding, or producing a deliverable (e.g. a process map) collaboratively. Weakness: requires skilled facilitation; dominant voices can suppress quieter ones.
Survey / questionnaire — structured questions sent to many respondents. Best for: gathering quantitative data or opinions from a large, geographically distributed audience. Weakness: low response rates; no follow-up possible on ambiguous answers.
Prototyping — creating a mockup, wireframe, or working model to elicit feedback. Best for: clarifying UI/UX requirements, or when stakeholders struggle to articulate needs in the abstract. Weakness: stakeholders may treat a prototype as a finished product and resist changes later.
A common beginner mistake is relying only on interviews. Real-world elicitation almost always combines several methods: for example, document analysis to prepare interview questions, then a workshop to resolve conflicts surfaced by the interviews.