Elicitation Techniques (Business Analysis)
Elicitation techniques are structured methods used by business analysts to gather requirements and information from stakeholders, including interviews, workshops, observation, surveys, document analysis, prototyping, and brainstorming.
Explanation
Elicitation is the process of drawing out requirements from stakeholders and other sources. It goes beyond simply asking people what they want. Effective elicitation uses multiple techniques to uncover stated requirements, unstated assumptions, and tacit knowledge that stakeholders may not think to mention. No single technique captures all requirements, so business analysts typically use a combination.
Common elicitation techniques include interviews (one-on-one or group conversations), facilitated workshops (structured group sessions to reach consensus), observation (watching users perform their work, also called job shadowing), surveys and questionnaires (gathering input from large groups), document analysis (reviewing existing documentation, systems, and reports), prototyping (creating mockups to validate understanding), and brainstorming (generating ideas without judgment). Each technique has strengths and is suited to different situations.
Elicitation is iterative, not a one-time event. Initial elicitation uncovers high-level requirements that are then refined through follow-up sessions. The business analyst must prepare for each elicitation activity, conduct it effectively, and document the results. Confirmation of elicited information with stakeholders is essential to ensure accuracy. On the CAPM exam, know the purpose, advantages, and appropriate use of each technique.
Key Points
- •Multiple techniques should be used in combination, as no single technique captures all requirements
- •Common techniques: interviews, workshops, observation, surveys, document analysis, prototyping, brainstorming
- •Elicitation is iterative and requires preparation, execution, and confirmation of results
- •Uncovers both explicit requirements and tacit knowledge stakeholders may not initially express
Exam Tip
Know when to use each technique. Interviews work for deep exploration with key stakeholders, surveys for large groups, observation for understanding actual workflows, and workshops for building consensus.
Frequently Asked Questions
Related Topics
Stakeholder Requirements
Stakeholder requirements describe the needs of individual stakeholders or stakeholder groups, including what they need the solution to do for them in order to meet the business requirements.
Business Analysis Planning
Business analysis planning defines the approach, activities, deliverables, and resources needed to perform business analysis on a project, ensuring requirements work is structured and aligned with project objectives.
Requirements Prioritization
Requirements prioritization is the process of ranking requirements by importance, urgency, risk, and business value to determine the order in which they should be addressed given constraints on time, budget, and resources.
Business Analysis Frameworks (CAPM Domain)
Business Analysis Frameworks is a CAPM exam domain (27%) that covers needs assessment, stakeholder analysis, requirements management, traceability, and solution evaluation from a business analysis perspective.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.