Elicitation and Collaboration
What this domain covers
Elicitation is not just asking questions; it is drawing out information that people hold but have not articulated. The domain includes preparing for elicitation (choosing techniques, logistics, supporting materials), conducting elicitation (facilitation, active listening, confirming what was heard), confirming elicitation results (validating accuracy with participants), communicating business analysis information (tailoring the message to the audience), and managing stakeholder collaboration (sustained, two-way working relationships).
Concepts to know cold
Know the technique families and when each fits: interviews for depth with individuals; workshops for consensus and conflict resolution; observation (job shadowing) for tacit, hard-to-describe work; document analysis for existing rules and data; surveys for breadth across many stakeholders; prototyping for feedback on something not yet built; focus groups for attitudes. Know that preparation includes deciding who to invite, what artefact to bring, and how results will be captured. Confirmation is a distinct step - elicitation is not finished until participants agree the captured information reflects their intent.
Traps
Questions bait you with technique mismatch: a survey to resolve a disputed process, or an interview to build consensus among twelve departments. Another trap is skipping confirmation and moving straight to specification. A third is treating communication as one-way reporting; it must be tailored and checked for understanding.
Rule of thumb
Choose the technique by the information type and the social goal: tacit knowledge → observation or interview; disagreement → workshop; scale → survey.
Worked example
A claims team cannot explain why some cases stall. Interviews yield opinions. Shadowing reveals a manual cross-check nobody mentioned. Confirm the finding with the team, then communicate it in a one-page process sketch rather than a long report.