Elicitation and Collaboration
Elicitation and Collaboration draws information out of people and sources, then confirms what was heard and communicates it back in a usable form. The exam tests technique selection and confirmation discipline - the difference between a BA who runs a good workshop and one who records the wrong decision from it.
The five tasks
- Prepare for Elicitation - define the scope of what must be learned, select techniques, choose participants, arrange logistics, and assemble supporting materials so stakeholders react to something concrete.
- Conduct Elicitation - run the activity, guide the conversation, capture the output, and confirm understanding in the room.
- Confirm Elicitation Results - compare captured information against other sources and with participants; this is where conflicting statements surface.
- Communicate Business Analysis Information - package and deliver information in the form the audience needs.
- Manage Stakeholder Collaboration - build and sustain buy-in, negotiate participation agreements, and monitor engagement.
Technique selection is the real subject
Interviews suit one or two informed people and sensitive topics; workshops suit cross-functional conflict resolution and speed; observation exposes workarounds people no longer notice; document analysis is cheap but reflects the past; prototyping elicits requirements for something that does not yet exist; surveys scale but cannot probe.
Worked example
A warehouse operator’s night shift reports that the new scanning process “works fine”, and interviews confirm it. Observing a single shift shows staff scanning pallets in batches and re-keying numbers into a spreadsheet to meet the cut-off time. Reasoning: interviews captured the espoused process, observation captured the actual one. The BA confirms the finding with the shift supervisor, records the manual re-keying as a requirement gap, and communicates it to the sponsor as a costed risk rather than as a complaint.
Traps that cost marks
- Skipping confirmation and letting one stakeholder’s opinion become a requirement.
- Eliciting only from system users while ignoring people who receive the output or enforce policy.
- Asking leading questions (“you’d like a dashboard, right?”) instead of open ones.
- Treating elicitation as a single phase; it recurs whenever the future state shifts.
- Sending raw notes to executives - communication formats must match audience needs.