Study guide
9.5 Root Cause & Decision Analysis Techniques
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
9.5 Root Cause & Decision Analysis Techniques
Key Takeaways Explain This Topic AI
Root Cause Analysis diagnoses foundational systemic breakdowns rather than treating superficial symptoms, using Fishbone (Ishikawa) Diagrams and the 5 Whys technique.
Fishbone diagrams categorize causal factors using standard industry taxonomies: 6Ms (Manufacturing), 8Ps (Services), and 4Ss (Office/Administrative).
Decision Trees evaluate complex multi-stage choices under risk by calculating Expected Monetary Value (EMV) at Chance Nodes and evaluating choices at Decision Nodes.
Decision Tables and Matrices formalize multi-variable conditional business rules into exhaustive condition and action grids, eliminating logical gaps and contradictions.
SWOT Analysis evaluates internal Strengths/Weaknesses against external Opportunities/Threats, while Risk Analysis quantifies uncertainty using Probability x Impact matrices.
Last updated: August 2026
9.5 Root Cause & Decision Analysis Techniques
Quick Summary: Business analysts must resolve complex organizational problems and evaluate high-stakes choices under uncertainty. BABOK® Guide v3 details diagnostic techniques ( Fishbone / Ishikawa Diagrams, 5 Whys ) alongside structured decision models ( Decision Trees with EMV, Decision Tables, SWOT Analysis, Risk Matrices ) to uncover true root causes and optimize strategic decisions.
1. Root Cause Analysis: Fishbone (Ishikawa) & 5 Whys
Root Cause Analysis systematically identifies the foundational, underlying reasons for an undesirable business outcome, defect, or process failure, preventing teams from merely treating surface-level symptoms. +-----------------------------------------------------------------------------------+
- | Fishbone (Ishikawa) Diagram Architecture |
- +-----------------------------------------------------------------------------------+
- | Category Branch 1 Category Branch 2 Category Branch 3 |
- | \ \ \ |
- | \── Primary Cause \── Primary Cause \── Primary Cause |
- | \ \── Sub-cause \ \── Sub-cause \ |
- | ═════════════════════════════════════════════════════════════════> [PROBLEM HEAD]|
- | / / / (Defect Statement)
- | /── Primary Cause /── Primary Cause / |
- | / / / |
- | Category Branch 4 Category Branch 5 Category Branch 6 |
- +-----------------------------------------------------------------------------------+
- The Standard Fishbone Category Taxonomies
Industry Domain Taxonomy Framework Constituent Category Ribs
Manufacturing / Operations 6Ms Machine (equipment, tech), Method (procedures, SOPs), Material (raw inputs, data), Measurement (metrics, inspection), Manpower / Mindpower (personnel, skills), Milieu / Mother Nature (environment).
Service Organizations 8Ps Product (service offering), Price (pricing model), Place (channel, location), Promotion (marketing), People (staff, training), Process (workflow, handoffs), Physical Evidence (documentation, UI), Productivity & Quality (efficiency).
Office & Administrative 4Ss Surroundings (work environment), Suppliers (vendors, external data), Systems (software, hardware), Skills (competency, training).
The 5 Whys Technique
An iterative questioning technique that drills down through successive layers of causation by repeatedly asking "Why?" (typically 5 times) until the systemic process or policy defect is revealed. Problem: A major online banking outage occurred during Friday peak hours.
├── Why 1? The primary transaction database crashed from memory exhaustion.
│ └── Why 2? An unindexed batch reconciliation query consumed 100% of RAM.
│ └── Why 3? A junior developer deployed the query directly to production.
│ └── Why 4? The automated CI/CD deployment pipeline bypassed query testing.
│ └── Why 5 (ROOT CAUSE)? There was no mandatory peer code review policy
│ or automated query linting gate for database changes.
2. Decision Trees and Expected Monetary Value (EMV)
A Decision Tree is a graphical, predictive decision-modeling tool that evaluates sequential choices, uncertain outcomes, and financial payoffs under conditions of risk. +-----------------------------------------------------------------------------------+
- | Decision Tree Node Notation |
- +-----------------------------------------------------------------------------------+
- | 1. DECISION NODE (Square - ▢): |
- | Represents a choice controlled directly by the decision-maker. |
- | |
- | 2. CHANCE / EVENT NODE (Circle - ◯): |
- | Represents an uncertain event; branches must show probabilities summing to 1.0|
- | |
- | 3. TERMINAL / END NODE (Triangle - ▷): |
- | Represents the final financial payoff or net outcome of a branch pathway. |
- +-----------------------------------------------------------------------------------+
Expected Monetary Value (EMV) Calculation EMV at Chance Node = ∑ i = 1 n ( Probability i × Financial Payoff i ) \text{EMV at Chance Node} = \sum_{i=1}^{n} (\text{Probability}_i \times \text{Financial Payoff}_i) EMV at Chance Node = i = 1 ∑ n ( Probability i × Financial Payoff i ) Decision Node [Build Custom vs. Buy SaaS]
- │
- ├── BRANCH 1: Buy SaaS (Upfront Cost = -$200K)
- │ └── ◯ Chance Node: Market Adoption
- │ ├── [High Demand (P = 0.70)] ──> Payoff = +$800,000
- │ └── [Low Demand (P = 0.30)] ──> Payoff = +$200,000
- │ EMV = (0.70 * $800K) + (0.30 * $200K) = $560K + $60K = $620,000
- │ Net Value = $620K - $200K = $420,000
- │
- └── BRANCH 2: Build Custom (Upfront Cost = -$500K)
- └── ◯ Chance Node: Market Adoption
- ├── [High Demand (P = 0.70)] ──> Payoff = +$1,200,000
- └── [Low Demand (P = 0.30)] ──> Payoff = +$100,000
- EMV = (0.70 * $1.2M) + (0.30 * $100K) = $840K + $30K = $870,000
- Net Value = $870K - $500K = $370,000
- *DECISION: Select Branch 1 (Buy SaaS) because Net EMV ($420K) > Branch 2 ($370K).*
- 3. Decision Tables and Matrices
Decision Tables formalize complex, multi-variable conditional business rules into a structured tabular grid, guaranteeing that all possible combinations of conditions are evaluated without logical gaps or contradictions.
Decision Table Anatomy (Four Quadrants) +-----------------------------------------------------------------------------------+
- | Decision Table Architecture |
- +-----------------------------------------------------------------------------------+
- | CONDITION STUB (Inputs) │ CONDITION ALTERNATIVES / RULES (R1 - R4) |
- | • Credit Score >= 720? │ Y Y N N |
- | • Debt-to-Income <= 36%? │ Y N Y N |
- | ────────────────────────────────────┼──────────────────────────────────────────── |
- | ACTION STUB (Outputs / Decisions) │ ACTION ENTRIES |
- | • Auto-Approve Prime Loan Rate │ X - - - |
- | • Refer to Senior Underwriter │ - X X - |
- | • Decline Application │ - - - X |
- +-----------------------------------------------------------------------------------+
Note
Rule Completeness Formula: A decision table with N N N binary (Yes/No) conditions has exactly 2 N 2^N 2 N possible rule combinations. For example, 3 conditions yield 2 3 = 8 2^3 = 8 2 3 = 8 rules. If a table contains fewer rules without intentional collapsing, an unhandled logic defect exists.
4. SWOT Analysis
A SWOT Analysis is a foundational strategic evaluation framework that examines the internal and external factors influencing an organization or proposed change initiative. ┌─────────────────────────────────────────────────────────────────────────────┐
- │ SWOT 2x2 Matrix │
- ├─────────────────────────────────────────────────────────────────────────────┤
- │ INTERNAL FACTORS │
- │ (Controllable by the Enterprise) │
- │ │
- │ STRENGTHS (S) WEAKNESSES (W) │
- │ • Proprietary patented technology • Legacy mainframe technical deb│
- │ • Highly skilled engineering talent • High operational cost base │
- │ • Robust balance sheet / cash reserves • Fragmented customer data silos│
- │ ─────────────────────────────────────────────────────────────────────── │
- │ EXTERNAL FACTORS │
- │ (Uncontrollable Environmental Forces) │
- │ │
- │ OPPORTUNITIES (O) THREATS (T) │
- │ • Emerging open banking regulations • Aggressive venture-backed apps│
- │ • Growing millennial market segment • Stricter data privacy fines │
- │ • Rapid growth of mobile payments • Rising interest rate headwinds│
- └─────────────────────────────────────────────────────────────────────────────┘
- 5. Risk Analysis & Risk Matrix
Risk Analysis evaluates uncertainties that could negatively impact project objectives, quantifying their Probability (Likelihood) and Impact (Consequence) to determine overall Risk Exposure . Risk Exposure Score = Probability (1 to 5) × Impact (1 to 5) \text{Risk Exposure Score} = \text{Probability (1 to 5)} \times \text{Impact (1 to 5)} Risk Exposure Score = Probability (1 to 5) × Impact (1 to 5)
The 4 BABOK Negative Risk Response Strategies
Strategy Mechanism Enterprise Scenario
Avoid Eliminate the risk entirely by altering project scope, architecture, or approach. Canceling a high-risk custom payment gateway in favor of an established certified vendor.
Mitigate Implement specific actions to reduce the probability or impact of the risk. Implementing redundant multi-region cloud servers and automated load balancers to prevent downtime.
Transfer Shift financial or operational impact to a third party (insurance, warranties, contracts). Purchasing commercial cyber-liability insurance and negotiating SLA penalty clauses with vendors.
Accept Acknowledge the risk and take no proactive action, establishing a contingency reserve if it occurs. Accepting minor UI rendering quirks on deprecated legacy browser versions.
Enterprise Scenario: Hospital Emergency Department Triage Bottleneck
A regional hospital network experienced critical patient wait-time spikes in its emergency department (ED):
Fishbone Analysis: Facilitated a session using the 8Ps Framework . Process: Triage nurses used duplicate paper intake forms; People: New nursing staff lacked triage protocol training; Physical Evidence: Room signage was confusing; Productivity: Lab blood tests averaged 90 minutes.
5 Whys: Drilled into lab delays: Why? Phlebotomy tubes sat in queues -> Why? Order transport was manual -> Why? Pneumatic tube station was broken -> Why? Maintenance contract lapsed -> Root Cause: Vendor SLA tracking was unassigned.
Decision Tree: Evaluated replacing the pneumatic tube system ($120K cost, Net EMV = +$450K) vs. hiring 4 courier staff ($180K annual OpEx, Net EMV = +$280K), leading to a high-confidence recommendation to replace the mechanical system.
Tip
CCBA Exam Tip: On the exam, when calculating Expected Monetary Value (EMV) for Decision Trees, remember to evaluate backward from right to left (Rollback method). At each Chance Node (circle), multiply branch probabilities by payoffs. At each Decision Node (square), choose the branch with the highest net payoff.
Warning
CCBA Exam Trap: Be careful not to confuse Internal with External factors in SWOT questions. A company's outdated IT infrastructure is a Weakness (Internal), NOT a Threat. A new competitor launching an AI platform is a Threat (External), NOT a Weakness.