Elicitation and Collaboration Techniques
Key Takeaways
- Document analysis reviews existing business or technical documentation to establish the as-is state before other elicitation techniques begin.
- Brainstorming defers judgment during idea generation to maximize the volume of creative ideas from a group.
- Interviews elicit information one-on-one or in small groups and are best suited to a few knowledgeable stakeholders or sensitive topics.
- Workshops bring diverse stakeholders together in a facilitated session to reach group consensus on requirements quickly.
- Collaborative games use structured, game-like activities to surface information when direct questioning has stalled or stakeholders are entrenched.
Why Elicitation and Collaboration Matter
Business analysis begins with getting accurate information from the people who understand the business need. BABOK Guide v3 Chapter 10 groups five techniques that a business analyst uses to draw out ideas, facts, and requirements directly from stakeholders or from existing materials. On the ECBA exam, expect situational questions that ask which technique fits a described scenario -- the differentiator is almost always how many people, how much structure, and whether the information is new or already documented.
The Five Techniques at a Glance
| Technique | Purpose | When to Use |
|---|---|---|
| Brainstorming | Generate a large volume of ideas quickly from a group | Early elicitation, when many options are needed and no dominant solution exists yet |
| Interviews | Elicit information directly from one person or a small group through structured or unstructured questions | Detailed, confidential, or nuanced information is needed from a few knowledgeable stakeholders |
| Workshops | Bring diverse stakeholders together in a structured, facilitated session to define or validate requirements | Fast group consensus is needed and stakeholders have conflicting views that must be reconciled quickly |
| Collaborative Games | Use structured, game-like activities to surface information stakeholders struggle to articulate directly | Traditional elicitation has stalled, or stakeholders are entrenched, distracted, or communication-averse |
| Document Analysis | Review existing business or technical documentation to identify current-state information, rules, or requirements | Documentation already exists (policies, specs, contracts) and understanding the as-is state is a prerequisite for further elicitation |
Brainstorming
Brainstorming asks a group to generate as many ideas as possible in a short, time-boxed session while deferring judgment. The technique's purpose is creative volume, not immediate analysis -- the BA, often acting as facilitator, separates idea generation from idea evaluation so participants are not inhibited by criticism. It works best with a diverse group and a clearly framed question. A BA should choose brainstorming when a broad range of options -- possible causes, solution ideas, or risks -- has not yet been identified and existing solutions are insufficient.
Interviews
Interviews are a controlled conversation, structured (a fixed question list), unstructured (open exploration), or a blend, used to elicit information one-on-one or in small groups. They allow the BA to probe follow-up questions, build stakeholder rapport, and capture nuance that group settings can suppress. Interviews are the right choice when only a few people hold the needed knowledge, when information is sensitive, or when results from another technique need to be validated or clarified with a subject matter expert.
Workshops
A workshop is a focused, facilitated event that brings multiple stakeholders together to elicit, define, or reach consensus on requirements in a single session. Because participants represent different interests, a skilled facilitator manages the agenda, keeps discussion on scope, and drives the group toward documented decisions. Workshops are efficient when many stakeholders need to align quickly, when conflicting requirements need real-time reconciliation, or when the team needs a jointly-owned outcome rather than a set of individually-collected opinions.
Collaborative Games
Collaborative games use structured activities -- such as prioritization exercises, prototyping games, or storytelling formats -- to lower the barriers that block direct questioning. They are especially effective for surfacing tacit knowledge, encouraging quieter stakeholders to contribute, or resolving entrenched disagreements by reframing the conversation. A BA reaches for a collaborative game when interviews and workshops have not produced enough insight, or when the group dynamic itself needs to change before real information can surface.
Document Analysis
Document analysis is a review of existing materials -- policies, procedures, system documentation, contracts, regulations, or prior project artifacts -- to extract information relevant to the current initiative. It is typically an early technique because it establishes the as-is state, existing business rules, and known constraints before the BA invests stakeholder time in interviews or workshops. Document analysis is the right call whenever authoritative documentation already exists; it reduces the elicitation burden on stakeholders and gives the BA an informed, credible starting point for later, more interactive techniques such as interviews or workshops.
Choosing Between Techniques on the Exam
ECBA situational items typically describe a scenario and ask what the BA should do first, or which technique is most appropriate. Use these cues:
- Group size and diversity -- one or two people with deep knowledge points to interviews; broad or mixed stakeholder groups point to workshops.
- Volume vs. precision -- needing many raw ideas fast points to brainstorming; needing a validated, precise answer points to interviews or document analysis.
- Existing material -- if authoritative documentation already exists, document analysis usually precedes stakeholder-facing techniques.
- Stalled or sensitive dynamics -- collaborative games address situations where direct questioning is not working.
These five techniques are frequently combined in practice: a BA might start with document analysis, use interviews to fill gaps with key stakeholders, run a brainstorming session to generate options, and close with a workshop to reach consensus. Recognizing that sequence -- and why each technique fits its stage -- is exactly what the exam rewards.
A business analyst needs to understand current loan-approval policies before beginning stakeholder interviews, and the compliance department has provided its full policy manual. Which technique should the BA use first to extract relevant rules and constraints from the manual?
Two stakeholder groups have repeatedly disagreed in interviews about how a new intake process should work, and progress has stalled. Which technique is best suited to break the impasse by re-engaging both groups in a structured, game-like activity?