3.3 Confirm Elicitation Results

3.3 Confirm Elicitation Results

Core Purpose and BABOK v3 Context

Task 8: Confirm Elicitation Results validates that the information gathered during elicitation activities is accurate, complete, consistent, and reflective of stakeholder intent. Raw elicitation notes and whiteboard sketches frequently contain misunderstandings, missing edge cases, conflicting statements from different departments, and obsolete domain assumptions. Confirming elicitation results transforms raw Elicitation Results (unconfirmed) into verified Elicitation Results (confirmed).

Confirmation is a vital quality control gate in business analysis. Identifying errors or contradictions during confirmation costs a fraction of what it would cost to rectify defect-ridden software in production. Task 8 ensures that BAs do not build formal models or software specifications on top of inaccurate baseline assumptions.

---

Distinction: Confirming vs. Verifying vs. Validating

CBAP candidates often confuse Task 8 with downstream requirements tasks. BABOK v3 maintains strict distinctions between these three concepts:

---

Confirmation Mechanisms and Triangulation

BAs employ two main analytical mechanisms during Task 8 confirmation:

1. Comparing Results Against Source Material

BAs cross-reference raw notes against objective secondary sources. This includes reviewing statutory legal texts, legacy database schemas, published enterprise Standard Operating Procedures (SOPs), and vendor documentation to ensure factual consistency.

2. Triangulating Across Stakeholder Groups

BAs compare findings elicited from one stakeholder group against statements made by other groups across the organizational hierarchy:

• Vertical Triangulation: Checking operational staff statements against executive policy mandates.
• Horizontal Triangulation: Cross-referencing requirements between peer departments (e.g., verifying that Sales order inputs match Supply Chain inventory capabilities).

                                ┌──────────────────────────────────┐
                                │ Elicitation Results (Unconfirmed)│
                                └────────────────┬─────────────────┘
                                                 │
                                                 ▼
                        ┌──────────────────────────────────────────────────┐
                        │            TRIANGULATION & CHECKING              │
                        └────────┬────────────────────────┬────────────────┘
                                 │                        │
                                 ▼                        ▼
                  ┌─────────────────────────────┐  ┌─────────────────────────────┐
                  │ Source Material Review      │  │ Cross-Stakeholder Check     │
                  │ (SOPs, Code, Regulations)   │  │ (Frontline vs Mgmt vs IT)   │
                  └──────────────┬──────────────┘  └──────────────┬──────────────┘
                                 │                        │
                                 └───────────┬────────────┘
                                             ▼
                                ┌──────────────────────────┐
                                │  Gap & Conflict Spotting │
                                └────────────┬─────────────┘
                                             │
                                             ▼
                                ┌──────────────────────────┐
                                │ Reconcile & Resolve      │
                                └────────────┬─────────────┘
                                             │
                                             ▼
                                ┌──────────────────────────┐
                                │ Formal / Informal Review │
                                └────────────┬─────────────┘
                                             │
                                             ▼
                                ┌──────────────────────────┐
                                │Elicitation Results       │
                                │       (Confirmed)        │
                                └──────────────────────────┘

---

Identifying Gaps and Resolving Conflicts

Confirmation frequently unearths gaps, omissions, and contradictions. When discrepancies surface, a CBAP must refrain from making unilateral decisions. Recommended conflict resolution approaches include:

1. Root Cause Discrepancy Analysis: Determining whether the conflict stems from simple semantic confusion, differing operational terminology, or genuine policy disagreements between departments.
2. Fact-Based Reconciliation: Presenting documented empirical evidence (e.g., transaction volumes, system audit logs) to help stakeholders reach consensus.
3. Structured Escalation: If stakeholders cannot reach consensus, the BA packages the conflicting options alongside business impact assessments and escalates the decision to the designated Product Owner or Executive Sponsor.

---

Formal vs. Informal Confirmation

The rigor of the confirmation process depends heavily on organizational culture, risk tolerance, and project methodology:

• Informal Confirmation: Common in Agile/Iterative environments. The BA conducts quick 1-on-1 walkthroughs, sends summary emails, or reviews draft user stories with SMEs during daily standups or refinement sessions. Fast, low friction, adaptable.
• Formal Confirmation: Mandatory in highly regulated industries (e.g., aerospace, healthcare, banking) and traditional Waterfall projects. Features formal review meetings, sign-off logs, digital signature capture, and baseline change control. Provides auditability and legal traceability.

---

BACCM Connections in Confirmation

• Change: Validate that confirmed findings accurately define the scope of business transformation.
• Need: Ensure that captured notes accurately reflect the true business problem rather than misunderstood symptoms.
• Solution: Confirm that solution capability expectations align with technical and financial boundaries.
• Stakeholder: Obtain explicit agreement and mutual understanding across all contributing stakeholder cohorts.
• Value: Confirm that elicited requirement details directly map to anticipated business value.
• Context: Cross-reference findings against regulatory, compliance, and organizational cultural contexts.

---

Worked Example: Healthcare Insurance Claims Automation

Scenario: A BA finishes eliciting business rules for an automated health insurance claims processing system. Notes from operational adjusters state that "all claims over $5,000 require two physical manager signatures before approval." However, the compliance officer noted in a separate interview that "recent regulatory updates allow automated digital sign-off up to $50,000 for network providers."

BA Confirmation Actions:

1. Source Material Check: The BA reviews the published State Insurance Commissioner regulatory bulletin from 2025.
2. Triangulation: The BA discovers that frontline adjusters were following an obsolete 2018 internal manual that had never been updated to reflect revised regulations.
3. Reconciliation Session: The BA schedules a brief 15-minute confirmation meeting with the Claims Manager and Compliance Officer, presenting the regulatory text.

Outcome: The Claims Manager confirms that internal procedures should match the regulatory threshold ($50,000 digital sign-off). The BA updates the raw notes to reflect confirmed elicitation results, eliminating a critical operational bottleneck before coding begins.

---

CBAP Exam Tips & Common Pitfalls

💡 Exam Tip: On the CBAP exam, if a question describes a situation where two stakeholders provide conflicting statements during separate interviews, the BA's immediate first step is to check authoritative source materials (SOPs, regulations, system logs) to establish factual reality before escalating or modifying requirement models.

⚠️ Common Trap: Do not confuse Task 8 (Confirm Elicitation Results) with Task 21 (Verify Requirements). Task 8 checks raw, unmodeled notes against sources and stakeholders. Task 21 evaluates formal requirement models for syntax, completeness, and structure quality.