3.1 Prepare for Elicitation
Key Takeaways
- Elicitation preparation (BABOK Task 6) establishes the scope, objectives, techniques, logistics, supporting materials, and stakeholder readiness for all elicitation activities.
- Technique selection requires evaluating project constraints, stakeholder geographic distribution, domain complexity, and required output depth using an elicitation selection matrix.
- Logistics preparation encompasses scheduling, facility configuration, collaborative tooling, agendas, and pre-reading distribution to optimize session productivity.
- Preparing stakeholders involves setting clear expectations, defining session outcomes, framing domain context, and mitigating anxiety regarding proposed changes.
- The primary output of Task 6 is the Elicitation Activity Plan, which guides the execution of collaborative, research, and experimental elicitation.
3.1 Prepare for Elicitation
Core Purpose and BABOK v3 Context
Elicitation and Collaboration is one of the six core Knowledge Areas in A Guide to the Business Analysis Body of Knowledge (BABOK® Guide v3). Within this knowledge area, Task 6: Prepare for Elicitation serves as the foundational planning step. Elicitation is not merely a passive exercise in gathering requirements; it is an active, iterative discovery process designed to draw out, synthesize, and clarify information from stakeholders, enterprise systems, and business domain research.
Preparing for elicitation ensures that business analysis activities are purposeful, structured, efficient, and aligned with organizational objectives. Conducting elicitation without rigorous preparation often leads to wasted stakeholder time, missed implicit business rules, scope creep, and incomplete requirements baselines. The primary output of Task 6 is the Elicitation Activity Plan, an artifact that details the scope, technique selection, schedule, logistics, supporting materials, and stakeholder roster for upcoming elicitation initiatives.
Key Elicitation Inputs and Preparation Tasks
To prepare effectively, a Business Analyst (BA) relies on the two inputs BABOK Guide v3 defines for this task: Needs (the business problem or opportunity being addressed) and the Stakeholder Engagement Approach (who must be involved, their roles, and how they prefer to collaborate). Existing business analysis information, business objectives, and potential value support the work as guidelines and tools — they are not inputs. Using these inputs, the BA executes five core preparation activities:
- Defining Elicitation Scope & Objectives: Establishing explicit boundaries for what will—and will not—be explored during elicitation sessions. Objectives should articulate the specific information required (e.g., business rules for loan origination, user interface expectations, security compliance constraints).
- Selecting Elicitation Techniques: Matching appropriate elicitation techniques to project constraints, domain complexity, and stakeholder characteristics.
- Securing Logistics: Organizing physical or virtual environments, scheduling participants across time zones, configuring whiteboards and recording tools, and assigning session roles (e.g., facilitator, scribe, timekeeper).
- Assembling Supporting Materials: Gathering context-setting documentation, pre-readings, sample data, process blueprints, agendas, and seed questions.
- Preparing Stakeholders: Educating participants on session objectives, framing expectations, explaining how their contributions impact project success, and addressing anxieties surrounding organizational change.
Elicitation Technique Selection Matrix
No single elicitation technique is sufficient for a comprehensive business analysis initiative. BAs must select a balanced combination of techniques based on stakeholder group size, availability, geographic dispersion, domain literacy, and project urgency. The matrix below outlines the primary BABOK elicitation techniques evaluated during Task 6 preparation:
| Technique | Optimal Stakeholder Group | Primary Strengths | Limitations / Risks | Ideal Scenario |
|---|---|---|---|---|
| Interviews | 1-on-1 or small group (2-3) | Deep, confidential insights; builds strong rapport; allows custom follow-up questions. | Time-intensive; risk of interviewer bias; difficult to scale across large groups. | Uncovering executive vision or sensitive operational pain points. |
| Workshops | Cross-functional team (6-12) | High velocity; rapid consensus; immediate cross-departmental alignment. | Requires expert facilitation; vulnerable to dominant personalities and groupthink. | Complex business process redesign and multi-departmental alignment. |
| Surveys / Questionnaires | Large, dispersed population (50+) | Quantitative data gathering; low cost per respondent; asynchronous completion. | Low response rates; risk of ambiguous questions; no opportunity for real-time clarification. | Gathering feedback from thousands of retail customers or remote employees. |
| Observation (Job Shadowing) | Individual operational SMEs | Uncovers implicit (tacit) knowledge; validates actual vs. documented practices. | Disruptive to daily work; observer effect (Hawthorne effect); time-consuming. | Verifying complex manual operational workarounds or factory floor workflows. |
| Document Analysis | Independent BA research | Establishes baseline context; zero stakeholder time drag; uncovers legacy business rules. | Outdated or inaccurate documentation; lacks context regarding modern usage. | Preparing for initial stakeholder interviews in legacy system migrations. |
| Focus Groups | Homogeneous cohort (6-10) | Rich qualitative sentiment; interactive group dynamics; tests potential features. | May turn into complaint sessions; non-statistically representative sample. | Testing customer sentiment on brand design or new mobile app concepts. |
| Prototyping | Technical & End-User teams | Tangible visual feedback; validates usability early; clarifies ambiguous user stories. | Stakeholders may mistake prototype for finished product; potential scope creep. | Eliciting complex user interface (UI) interactions and workflow logic. |
Logistics and Supporting Material Preparation
Logistics preparation extends beyond booking a conference room or sending a video link. A CBAP must systematically address administrative and operational parameters:
- Role Allocation: Designating a dedicated Scribe to capture notes enables the Facilitator to maintain energy, monitor body language, and manage session dynamics. A Timekeeper ensures agenda compliance.
- Virtual Collaboration Tooling: Configuring digital canvases (e.g., Miro, Mural) with pre-formatted templates, voting dots, and breakout rooms prior to remote sessions.
- Pre-Session Distribution: Transmitting agendas, contextual domain glossaries, and pre-reading materials at least 48 hours in advance to allow participants to prepare thoughtful responses.
BACCM Connections in Preparation
The Business Analysis Core Concept Model™ (BACCM™) provides a lens for evaluating Task 6:
- Change: Define the elicitation scope to explore necessary organizational transitions.
- Need: Clarify the specific gaps or business problems elicitation must investigate.
- Solution: Prepare materials that allow stakeholders to evaluate potential capability enhancements.
- Stakeholder: Identify and prepare the right individuals based on authority, domain expertise, and operational impact.
- Value: Structure elicitation to capture high-priority value drivers while minimizing stakeholder time expenditure.
- Context: Tailor logistics and techniques to enterprise culture, regulatory constraints, and geographic boundaries.
Worked Example: Global Claims Processing System Preparation
Scenario: A global insurance enterprise plans to replace its legacy regional claims platforms with a unified cloud-based solution. The Lead Business Analyst must prepare for elicitation across five international regional hubs.
BA Action Plan:
- Document Analysis: The BA spends the first week reviewing legacy technical manuals and regulatory compliance specs across all five regions to build a baseline feature inventory.
- Observation: Recognizing that regional adjusters use unwritten manual workarounds, the BA schedules 3-day active job shadowing sessions with local claims adjusters in two major hubs.
- Workshops: To reconcile conflicting regional workflow rules, the BA designs a series of 3-hour virtual cross-functional workshops featuring Miro digital whiteboards and breakout rooms.
- Stakeholder Readiness: The BA conducts 15-minute alignment calls with regional VPs to explain the session objectives, address fears regarding operational headcount reduction, and distribute a pre-session survey on claims volume bottlenecks.
Outcome: The resulting Elicitation Activity Plan aligns executive vision with operational reality while maintaining strict schedule discipline across time zones.
CBAP Exam Tips & Common Pitfalls
💡 Exam Tip: On the CBAP exam, if a scenario describes stakeholders who are geographically distributed with tight schedules and limited availability, prioritize Surveys, Document Analysis, and targeted Asynchronous Reviews over mandatory co-located multi-day workshops.
⚠️ Common Trap: Watch out for questions where a BA jumps directly into holding workshops without conducting preliminary Document Analysis. The BABOK framework emphasizes establishing baseline domain knowledge first so stakeholder time is not wasted explaining documented business rules.
A Lead Business Analyst is preparing to elicit requirements for a complex core banking migration. Documentation for legacy business rules is severely outdated, and key subject matter experts (SMEs) are distributed across four time zones with tight calendar availability. Which initial combination of elicitation techniques should the BA select during preparation to maximize efficiency while building a credible baseline?
A business analyst is tasked with eliciting requirements for a new regulatory reporting module. The BA suspects that front-line operational staff perform informal workarounds that differ significantly from official Standard Operating Procedures (SOPs). Which technique should the BA prioritize in the Elicitation Activity Plan to uncover these unwritten operational practices?
During the preparation stage for an elicitation workshop on enterprise resource planning (ERP), a business analyst identifies that two key executive stakeholders hold deeply conflicting strategic visions for the solution scope. How should the BA handle stakeholder preparation prior to the joint session?
Which artifact represents the formal primary output of BABOK Task 6 (Prepare for Elicitation)?