Overview
Elicitation and Collaboration covers five tasks that run continuously rather than as a single phase. You prepare for elicitation by defining its scope, choosing techniques and setting up logistics; conduct elicitation through collaborative, research or experiment-based activities; confirm elicitation results for accuracy and consistency; communicate business analysis information in packages suited to each audience; and manage stakeholder collaboration so people stay engaged and keep their commitments.
The BABOK Guide treats elicitation as drawing out information, not just asking what people want, so research such as document analysis and experiments such as prototypes count too. This domain consumes the stakeholder engagement approach from Domain 1 and produces the confirmed elicitation results that Domain 4 (Strategy Analysis) and Domain 5 (Requirements Analysis and Design Definition) turn into needs, models and designs.
How it's tested
Questions are short scenarios and case-study items that ask which technique is BEST, what to do NEXT after an elicitation activity, or how to handle a stakeholder issue. The reasoning is to identify the stage the information is in, the constraint that limits technique choice, and the collaboration problem being described, then pick the task that addresses that exact gap.
-
Pick the technique
A stem gives constraints such as hundreds of users, tacit knowledge or a missing system. You choose the technique that fits, such as a survey, observation or a prototype.
-
Name the next step
An elicitation session has ended and you choose what happens next. Usually the results must be confirmed before they are analyzed or approved.
-
Fix the collaboration
A stakeholder stops attending or misses commitments. You choose the response that re-engages them, typically by understanding the cause and renegotiating commitments.
After interviewing warehouse supervisors, a business analyst finds their description of the returns process does not match the written procedure. Options include approving the supervisors' version, updating the procedure, starting design, or comparing the interview results against the procedure and following up on discrepancies. The results are still unconfirmed and conflict with a source, so confirming them by comparison and follow-up is the next step before any analysis or design.
Tasks 5
Official tasks from the IIBA outline, in outline order.
2.1 Prepare for ElicitationBABOK Guide task 4.1: understand scope, select techniques, set up logistics and prepare stakeholders.
- What it means
- The business analyst decides what information the activity must produce, picks techniques, arranges logistics such as participants, location and tools, secures supporting material and prepares stakeholders so they arrive ready. The output is the elicitation activity plan.
- What to understand
- Technique choice follows the need, the stakeholders and the constraints. Preparation includes sending context and questions in advance and understanding what information already exists, which may point to research instead of collaborative sessions.
- How it shows up
- A session failed because participants were unprepared or the wrong people attended, and you pick what should have happened. The answer is preparation activity, not a different technique.
- Common confusion
- Treating preparation as mere scheduling. Understanding the scope of elicitation and securing supporting material are core elements that change which techniques are worth using.
2.2 Conduct ElicitationBABOK Guide task 4.2: guide the activity and capture outcomes from collaborative, research or experiment-based elicitation.
- What it means
- The business analyst runs the elicitation activity, keeping it on scope, and records the outcomes. The BABOK identifies collaborative elicitation, research such as document analysis and data mining, and experiments such as observation studies, proofs of concept and prototypes. The output is unconfirmed elicitation results.
- What to understand
- Good facilitation keeps the activity aligned to its goal and the business need while capturing outcomes accurately. Observation exposes tacit knowledge that people cannot explain; prototypes surface reactions that cannot be described in the abstract.
- How it shows up
- Users describe their work vaguely or the system does not exist yet, and you choose a technique. Observation or prototyping usually beats another interview.
- Common confusion
- Assuming the results of a session are agreed requirements. What comes out of Conduct Elicitation is unconfirmed and must still be confirmed and analyzed.
2.3 Confirm Elicitation ResultsBABOK Guide task 4.3: check results for accuracy and consistency against sources and other results.
- What it means
- The business analyst checks that elicitation results accurately reflect what stakeholders meant and are consistent with source information and with results from other activities. Conflicts are recorded and followed up. The output is confirmed elicitation results.
- What to understand
- Confirmation is about whether information was captured correctly, not about whether the requirement is good or approved. Comparing results across stakeholders and documents exposes gaps and contradictions early, when they are cheap to fix.
- How it shows up
- Two groups give contradictory information, or notes differ from a policy document. The correct next step compares and follows up before analysis or approval.
- Common confusion
- Confusing confirmation with verification, validation or approval. Each is a different check at a different stage in the BABOK flow.
2.4 Communicate Business Analysis InformationBABOK Guide task 4.4: determine objectives and format, then communicate packages to stakeholders.
- What it means
- The business analyst decides what each audience needs, packages the information in a suitable format, such as formal documentation, informal documentation or a presentation, and communicates it through an appropriate platform. The output is business analysis information (communicated).
- What to understand
- Communication is bidirectional and aims for shared understanding, not distribution. The same content may be packaged differently for executives, implementers and testers.
- How it shows up
- Stakeholders signed off but later claim they never understood the content, and you choose what went wrong. The answer is usually a package mismatched to the audience.
- Common confusion
- Thinking that sending a document equals communicating it. The task is complete when the audience understands the information well enough to use it.
2.5 Manage Stakeholder CollaborationBABOK Guide task 4.5: gain agreement on commitments, monitor engagement and encourage collaboration.
- What it means
- The business analyst secures stakeholders' commitments of time and resources, monitors participation and performance, and fosters collaboration toward shared goals. The output is stakeholder engagement.
- What to understand
- Disengagement has causes such as competing priorities, unclear value or conflict. The business analyst diagnoses the cause, renegotiates commitments and escalates only when collaboration cannot be restored.
- How it shows up
- A key subject matter expert keeps missing sessions and you pick the best action. Talking with the person to understand the cause and agree realistic commitments beats escalation or replacement.
- Common confusion
- Confusing this with Plan Stakeholder Engagement. Planning sets the approach in Domain 1; this task is the continuing work of keeping engagement healthy.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Elicitation types
The BABOK groups elicitation into collaborative work with stakeholders, research into documents and data, and experiments such as observation studies, proofs of concept and prototypes.
- Remember
- Elicitation is broader than asking questions; research and experiments draw out information people cannot easily state.
- Tested as
- Technique questions often hinge on recognizing that the best source is data, a document or a test rather than a conversation.
- Trap
- Always choosing an interview or workshop regardless of the constraint.
-
Unconfirmed vs. confirmed elicitation results
Conduct Elicitation produces unconfirmed results; Confirm Elicitation Results checks them for accuracy and consistency and produces confirmed results.
- Remember
- Results are confirmed before they are analyzed, specified and approved.
- Tested as
- What-next questions after a session usually expect confirmation.
- Trap
- Sending raw session notes for approval or modeling them immediately.
-
Tacit knowledge
Knowledge people use without articulating it, such as workarounds and habits performed automatically during a task.
- Remember
- Observation, active or passive, is the classic way to surface it.
- Tested as
- Stems where users say 'I just know when' or skip steps when describing work point to observation.
- Trap
- Running more interviews, which only capture what people can describe.
-
Survey or questionnaire
A set of written questions sent to many stakeholders to gather information efficiently, including quantitative ratings and closed or open questions.
- Remember
- It scales to large, dispersed populations but gives limited depth and no chance to probe in the moment.
- Tested as
- Stems with hundreds of users across regions and a tight timeline favor it.
- Trap
- Using it to explore complex, poorly understood problems that need follow-up questions.
-
Prototyping
Building a model of the solution, from paper sketches to working simulations, to elicit and validate needs through stakeholder reaction.
- Remember
- Throw-away prototypes clarify needs and are discarded; evolutionary prototypes grow into the solution.
- Tested as
- Best when stakeholders struggle to describe an interface or a new capability in the abstract.
- Trap
- Letting stakeholders treat a throw-away prototype as the near-finished product.
-
Elicitation activity plan
The output of Prepare for Elicitation, describing logistics, scope, techniques, participants and supporting material for a planned activity.
- Remember
- It is prepared per activity and guided by the stakeholder engagement approach.
- Tested as
- Failed sessions caused by missing participants or materials point back to this output.
- Trap
- Confusing it with the business analysis approach, which covers the whole initiative.
-
Business analysis information package
A grouping of business analysis information prepared for an audience in a format such as formal documentation, informal documentation or a presentation.
- Remember
- Format, level of detail and platform follow the audience's needs and the information management approach.
- Tested as
- Communication breakdown stems test whether the package fit its audience.
- Trap
- Giving executives detailed specifications and expecting meaningful review.
-
Stakeholder engagement (output)
The output of Manage Stakeholder Collaboration: stakeholders willing and able to participate in business analysis activities and keep commitments.
- Remember
- It is maintained over time through agreed commitments, monitoring and collaboration.
- Tested as
- Attendance and participation problems map here.
- Trap
- Treating replacement of an uncooperative expert as the first option.
-
Workshop
A structured, facilitated session with a defined goal that brings key stakeholders together to collaborate on requirements or decisions.
- Remember
- It needs a neutral facilitator, a scribe, the right participants and a clear agenda; it can resolve conflicts quickly when decision makers attend.
- Tested as
- Best when cross-functional agreement is needed fast.
- Trap
- Choosing it when participants are dispersed or the sponsor cannot commit the right people.
-
Document analysis
Research-based elicitation that reviews existing materials such as procedures, contracts, regulations and system documentation.
- Remember
- It is a good starting point to understand context and prepare questions, but documents can be outdated.
- Tested as
- Appears when stakeholders are unavailable early or when regulation sets the requirements.
- Trap
- Treating document content as current practice without confirming it with stakeholders.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Confirm vs. verify vs. validate vs. approve
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Confirm elicitation results (Domain 2) | Check that captured information is accurate and consistent with sources and other results | About capture: did we record what was meant? | Treating confirmation as stakeholder sign-off |
| Verify requirements (Domain 5) | Check requirements and designs meet quality standards and are fit for use | About quality: are they well formed, clear, consistent and testable? | Thinking verification proves business value |
| Validate requirements (Domain 5) | Check requirements and designs align with the business need and deliver value | About value: are these the right requirements for the goal? | Assuming a well-written requirement is automatically valid |
| Approve requirements (Domain 3) | Obtain agreement from authorized stakeholders to proceed | About authority and decision under the governance approach | Expecting the business analyst to be the approver |
Interview vs. observation vs. survey vs. prototype
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Interview | Structured or unstructured conversation with one or a few stakeholders | Depth and follow-up questions, but slow to scale | Relying on it for tacit knowledge people cannot articulate |
| Observation | Watching people do their work, passively or with questions | Reveals actual practice and workarounds | Forgetting that being observed can change behavior |
| Survey or questionnaire | Written questions sent to many respondents | Breadth and quantitative input at low cost | Using it where exploration and probing are needed |
| Prototype | A model of the solution for stakeholders to react to | Makes abstract needs concrete, especially interfaces | Stakeholders mistaking a mock-up for the near-final system |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Skipping confirmation
- What candidates pick
- Moving straight from a workshop to modeling or sign-off.
- Why it looks right
- The session felt productive and everyone seemed to agree.
- Why it's wrong
- Results from Conduct Elicitation are unconfirmed; inaccuracies and conflicts must be checked before analysis or approval.
Clue to watch for A stem asking what to do NEXT immediately after an elicitation activity usually points to confirmation.
-
Interviewing for tacit knowledge
- What candidates pick
- Scheduling more detailed interviews with users who describe their work vaguely.
- Why it looks right
- Interviews are familiar and allow follow-up questions.
- Why it's wrong
- If people cannot articulate how they work, more questions produce the same gaps; observation shows the actual steps.
Clue to watch for Phrases like experienced staff 'just know' or skip steps when explaining point to observation.
-
Workshop for a dispersed population
- What candidates pick
- A large facilitated workshop with users from many countries.
- Why it looks right
- Workshops build consensus quickly.
- Why it's wrong
- Logistics and time zones make it impractical, and it samples few voices; a survey reaches many quickly.
Clue to watch for Large numbers, many locations and a tight deadline signal a survey or questionnaire.
-
One package for everyone
- What candidates pick
- Sending the full requirements specification to all stakeholders for review.
- Why it looks right
- It seems transparent and complete.
- Why it's wrong
- Communication must fit each audience's objectives and level of detail; executives and implementers need different packages.
Clue to watch for Complaints that stakeholders did not read or understand material signal a packaging problem.
-
Replacing the expert
- What candidates pick
- Asking the sponsor for a different subject matter expert after missed sessions.
- Why it looks right
- It removes the immediate obstacle.
- Why it's wrong
- Manage Stakeholder Collaboration expects you to understand the cause and renegotiate commitments first; the expert may hold unique knowledge.
Clue to watch for If the stem gives no evidence the person refused, choose the option that talks to them first.
-
Trusting documents as current practice
- What candidates pick
- Building requirements directly from an existing procedure manual.
- Why it looks right
- Documents are authoritative and quick to read.
- Why it's wrong
- Documents may be outdated or ignored in practice; results must be confirmed against stakeholders and other sources.
Clue to watch for Mention of an old manual or of staff using workarounds signals the need to confirm.
Answer framework
Use these steps when a scenario involves gathering, checking or sharing information with stakeholders.
- Identify where the information currently sits in the flow: not yet elicited, unconfirmed, confirmed, or ready to be communicated to an audience.
- Read the constraints that limit technique choice, such as population size, location, tacit knowledge, an unbuilt system or available documents.
- Choose the task and technique that closes that specific gap, such as observation for habits or a survey for breadth across regions.
- Before analysis or approval, confirm results against sources and other stakeholders and follow up on every conflict you find.
- If engagement is the problem, diagnose its cause and renegotiate commitments before escalating to the sponsor or replacing anyone.
Practice question
Want more like this? The CBAP practice test has questions for every domain.
Checklist
0 of 11
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Learn the five tasks in their natural order: prepare, conduct, confirm, communicate, and manage collaboration throughout. Anchor them on the state of the information, because the exam often asks what comes next and the answer depends on whether results are unconfirmed or confirmed.
The high-priority concepts are the confirm, verify, validate and approve distinction and technique selection under constraints. Build a one-page table of the common techniques with the situation each fits best and its main limitation. Candidates often underestimate Communicate Business Analysis Information, assuming it is trivial, yet sign-off disputes and misunderstandings are rich material for scenario questions. Manage Stakeholder Collaboration is also underrated because the right answer is often the patient one.
After studying, practice with scenarios that end immediately after an elicitation activity and force a next-step choice. Then mix in Domain 5 questions on verification and validation so the stages stay separate in your head. When you miss a technique question, write down the clue you overlooked, such as dispersed users, unbuilt systems or tacit knowledge.
FAQ
How much of the CBAP exam is Elicitation and Collaboration?
IIBA weights it at 12%, the lowest of the six knowledge areas. That works out to roughly 14 of 120 questions as a planning estimate.
Is elicitation the same as interviewing stakeholders?
No. The BABOK Guide includes collaborative techniques, research such as document analysis and data mining, and experiments such as observation studies, proofs of concept and prototypes.
What is the difference between confirming results and validating requirements?
Confirming checks that elicited information was captured accurately and consistently. Validating, in Domain 5, checks that requirements and designs align with the business need and will deliver value.
Which technique is best for tacit knowledge?
Observation, because it shows how work is really done, including steps people perform without thinking. Prototypes also help when the knowledge concerns how people would use a future interface.
Does Elicitation and Collaboration happen only at the start of an initiative?
No. The tasks are performed whenever information is needed, throughout predictive and adaptive approaches, and collaboration is managed for the whole life of the work.
How does this domain link to Business Analysis Planning and Monitoring?
Domain 1 produces the stakeholder engagement approach and the information management approach, which guide how you prepare elicitation, who participates and how information is packaged.
How should I study this domain?
As a planning estimate, allow about 20 to 25 hours within a 180-hour plan. Focus on the flow of results through the tasks and on matching techniques to constraints.
Other Business Analysis certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
Test your Domain 2 knowledge
You have walked through preparing, conducting and confirming elicitation, communicating packages and keeping stakeholders engaged. Practice questions will test whether you can spot the stage and the constraint that decide each answer.