3.2 Conduct Elicitation (Task 4.2)

CCBA Certification of Capability in Business Analysis Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CCBA Exam Foundation

1.1 CCBA Exam Structure, Eligibility & IIBA Framework 1.2 The Business Analysis Core Concept Model (BACCM™) 1.3 Requirements Classification Schema & Architecture 1.4 CCBA Competency & Proficiency Levels (Level 2 — Skilled)

2 Chapter 2: Business Analysis Planning and Monitoring

2.1 Plan Business Analysis Approach (Task 3.1) 2.2 Plan Stakeholder Engagement (Task 3.2) 2.3 Plan Business Analysis Governance (Task 3.3) 2.4 Plan Business Analysis Information Management (Task 3.4) 2.5 Identify BA Performance Improvements (Task 3.5)

3 Chapter 3: Elicitation and Collaboration

3.1 Prepare for Elicitation (Task 4.1) 3.2 Conduct Elicitation (Task 4.2) 3.3 Confirm Elicitation Results (Task 4.3) 3.4 Communicate Business Analysis Information (Task 4.4) 3.5 Manage Stakeholder Collaboration (Task 4.5)

4 Chapter 4: Requirements Life Cycle Management

4.1 Trace Requirements (Task 5.1) 4.2 Maintain Requirements (Task 5.2) 4.3 Prioritize Requirements (Task 5.3) 4.4 Assess Requirements Changes (Task 5.4) 4.5 Approve Requirements (Task 5.5)

5 Chapter 5: Strategy Analysis

5.1 Analyze Current State (Task 6.1) 5.2 Define Future State (Task 6.2) 5.3 Assess Risks (Task 6.3) 5.4 Define Change Strategy (Task 6.4)

6 Chapter 6: Requirements Analysis and Design Definition — Modeling & Architecture

6.1 Specify and Model Requirements (Task 7.1) 6.2 Verify Requirements (Task 7.2) 6.3 Validate Requirements (Task 7.3) 6.4 Define Requirements Architecture (Task 7.4)

7 Chapter 7: Requirements Analysis and Design Definition — Design & Value

7.1 Define Design Options (Task 7.5) 7.2 Analyze Potential Value and Recommend Solution (Task 7.6) 7.3 Estimation Techniques & Solution Trade-Offs 7.4 Acceptance and Evaluation Criteria Definition

8 Chapter 8: Solution Evaluation

8.1 Measure Solution Performance (Task 8.1) 8.2 Analyze Performance Measures (Task 8.2) 8.3 Assess Solution Limitations (Task 8.3) 8.4 Assess Enterprise Limitations (Task 8.4) 8.5 Recommend Actions to Increase Solution Value (Task 8.5)

9 Chapter 9: Essential BABOK Techniques

9.1 Core Elicitation & Analysis Techniques 9.2 Process, Data & Non-Functional Requirements Modeling 9.3 Financial Analysis & Business Case Techniques 9.4 Prioritization & Scope Techniques 9.5 Root Cause & Decision Analysis Techniques

10 Chapter 10: Underlying Competencies & Perspectives

10.1 Analytical Thinking, Problem Solving & Systems Thinking 10.2 Behavioral Characteristics, Communication & Interaction Skills 10.3 Business Acumen, Solution Knowledge & BA Tooling 10.4 The Five BABOK Perspectives in Practice

11 Chapter 11: CCBA Exam Mastery & Scenario Strategy

11.1 Deconstructing CCBA Scenario Questions & BABOK Logic 11.2 Common Traps, Distractors & Subtle BABOK Distinctions 11.3 Comprehensive 8-Week Study Plan & Exam Day Strategy

3.2 Conduct Elicitation (Task 4.2)

Key Takeaways Explain This Topic AI

Elicitation is an active, exploratory process of drawing out, uncovering, and synthesizing business analysis information across three modalities: Collaborative, Research, and Experimental.

Collaborative elicitation (workshops, focus groups, games) builds consensus and explores divergent viewpoints through direct human interaction.

Research elicitation (document analysis, data mining, benchmarking) discovers baselines and constraints without direct stakeholder querying.

Experimental elicitation (prototyping, observation) uncovers tacit knowledge and operational reality through practical interaction and visual proof.

The direct output of Task 4.2 is Elicitation Results (unconfirmed), which captures raw findings that require subsequent validation.

Last updated: August 2026

3.2 Conduct Elicitation (Task 4.2)

Quick Summary: BABOK v3 Task 4.2 ( Conduct Elicitation ) is the execution phase of discovery. Business analysts guide stakeholders through collaborative discussions, research repositories, and experimental trials to uncover stated and unstated business needs. The output of this task is Elicitation Results (unconfirmed) , representing raw, unvalidated findings.

The Three Modalities of Elicitation

BABOK v3 categorizes all elicitation activities into three foundational types. High-performing business analysts combine these types into a cohesive elicitation strategy rather than relying on a single method. +-----------------------------------------------------------------------------------+

| The 3 Types of Elicitation |
+-----------------------------------------------------------------------------------+
| |
| 1. COLLABORATIVE 2. RESEARCH 3. EXPERIMENTAL |
| * Direct human dialogue * Systematic inspection * Practical interaction |
| * Workshops & JAD * Document Analysis * Prototyping (Lo/Hi-Fi) |
| * Focus Groups * Data Mining & Telemetry * Active Observation |
| * Brainstorming * Benchmarking * Passive Observation |
| * Collaborative Games * Market Analysis * Simulations |
| |
+-----------------------------------------------------------------------------------+
1. Collaborative Elicitation

Collaborative elicitation relies on direct interaction between the business analyst and human stakeholders to explore ideas, discover needs, and build alignment.

Workshops / JAD (Joint Application Design): Structured, timeboxed sessions with cross-functional participants led by a neutral facilitator and documented by a scribe. Ideal for resolving cross-departmental conflicts and mapping end-to-end value streams.

Focus Groups: Representative groups of users or consumers guided by a moderator to elicit qualitative feelings, attitudes, and perceptions about a proposed concept or product.

Brainstorming: Creative ideation sessions designed to produce a high volume of ideas without immediate judgment or critique.

Collaborative Games: Structured experiential activities (such as Product Box , Speed Boat , or Fishbowl ) designed to break down psychological barriers, encourage creative participation, and reveal hidden assumptions.

2. Research Elicitation

Research elicitation extracts information systematically from organizational assets, historical data, or external sources without querying stakeholders directly.

Document Analysis: Scrutinizing contracts, technical specifications, regulatory filings, error logs, and operating manuals to establish a baseline of current-state rules and operational boundaries.

Data Mining & Analytics: Analyzing structured database records, transaction logs, and user telemetry to uncover behavioral trends, data anomalies, and transaction volumes.

Benchmarking & Market Analysis: Comparing internal processes and metrics against industry leaders, competitors, or recognized international standards to identify capability gaps.

3. Experimental Elicitation

Experimental elicitation uncovers tacit knowledge—insights that stakeholders possess and execute instinctively but cannot easily articulate in an interview or workshop.

Prototyping: Creating interactive wireframes, mockups, or functional proofs-of-concept. Prototypes stimulate stakeholder feedback by providing a concrete visual artifact.

Observation (Job Shadowing):

Active Observation: The BA sits with the user and actively interrupts to ask probing questions during task execution ("Why did you copy that value into Notepad before pasting it?"). Excellent for uncovering the rationale behind workarounds, though it temporarily disrupts user workflow.

Passive Observation: The BA observes silently from a distance without interrupting, taking timestamped notes and debriefing with the user afterward. Ideal for measuring natural task durations, ergonomic flow, and high-speed, safety-critical environments where interruption introduces risk.

Elicitation Modalities & Techniques Comparison

Modality Key Techniques Primary Strengths Inherent Limitations

Collaborative Workshops, Focus Groups, Collaborative Games Fast-tracks consensus; surfaces divergent viewpoints; builds stakeholder ownership Susceptible to personality conflicts, social loafing, and executive dominance

Research Document Analysis, Data Mining, Benchmarking Highly objective; independent of stakeholder schedules; establishes concrete baselines Outdated documentation may reflect obsolete processes; cannot explain why deviations occur

Experimental Prototyping, Active/Passive Observation, Simulation Reveals tacit knowledge; validates operational reality; uncovers hidden workarounds Prototypes can set unrealistic expectations; observation may trigger Hawthorne effect

Facilitation Dynamics & Probing Questioning

Conducting elicitation requires advanced interpersonal and facilitation competencies. The business analyst must actively steer group dynamics and dig beneath superficial requests.

Questioning Frameworks

Open-Ended Questions: "How does the claims team handle discrepancies in foreign currency invoices?" (Used to open broad exploration and uncover context).

Closed-Ended Questions: "Does the audit rule require dual authorization for wire transfers over $50,000?" (Used to confirm specific business rules and boundary conditions).

The Funnel Technique: Starting with broad, open-ended questions to explore the problem space, progressively narrowing to probing questions, and concluding with closed-ended questions to lock in specific constraints.

Root Cause Probing (The 5 Whys): Asking sequential "Why" questions to drill past operational symptoms to the underlying organizational or systemic root cause.

Managing Difficult Workshop Dynamics +-----------------------------------------------------------------------------------+

| Facilitation Intervention Matrix |
+-----------------------------------------------------------------------------------+
| SITUATION: | RECOMMENDED BA INTERVENTION: |
| -------------------------------------|------------------------------------------ |
| Dominant Stakeholder / HiPPO | Use anonymous ideation (sticky notes, |
| (Highest Paid Person dominates) | dot voting, silent brainwriting). |
| -------------------------------------|------------------------------------------ |
| Silent / Reticent Subject Matter | Direct gentle, targeted questions to |
| Expert | their specific domain expertise. |
| -------------------------------------|------------------------------------------ |
| Tangential Debates / Rabbit Holes | Log items in a visible "Parking Lot" and |
| | enforce timebox discipline. |
| -------------------------------------|------------------------------------------ |
| Hostile or Cynical Participants | Acknowledge frustrations openly; refocus |
| | on shared objectives and pain points. |
+-----------------------------------------------------------------------------------+
Real-Time Information Capture

During Task 4.2, the business analyst must ensure that findings are captured accurately in real time without stalling conversational momentum:

Visual Scribing: Using interactive digital whiteboards, concept diagrams, or process flowcharts visible to all participants during the session.

Separation of Roles: In complex workshops, pairing a lead facilitator with a dedicated scribe ensures that the facilitator remains fully engaged in active listening while the scribe logs detailed inputs, decisions, and open questions.

Recording Protocols: When recording audio or video, always obtain explicit participant consent in accordance with organizational governance.

Tip

CCBA Exam Tip: On the CCBA exam, when a scenario describes stakeholders who have difficulty expressing what they need or who give contradictory statements about their daily work, the correct next step is almost always an Experimental technique (Prototyping or Observation). When stakeholders "don't know what they want until they see it," prototyping is the gold standard.

Warning

CCBA Exam Trap: Remember that the direct output of Task 4.2 is Elicitation Results (unconfirmed) . The business analyst has not yet confirmed that these findings are accurate, consistent, or representative of the true business need. Confirmation occurs exclusively in Task 4.3.