5.1 Analyze Current State (Task 6.1)

5.1 Analyze Current State (Task 6.1)

Quick Summary: Strategy Analysis begins by understanding where the enterprise is today and why it cannot remain there. In BABOK v3 Task 6.1 (Analyze Current State), the business analyst identifies the core Business Need, scrutinizes internal organizational capabilities, audits technology and processes, scans external market drivers (PESTLE, Porter's Five Forces), and applies Root Cause Analysis (Fishbone Diagrams, 5 Whys) to define an accurate Current State Description and establish foundational Business Requirements.

---

Purpose and Strategic Role of Task 6.1

The purpose of Analyze Current State is to understand the business need and how that need relates to the way the enterprise functions today. Before an organization can determine where it wants to go (Future State) or how to get there (Change Strategy), it must establish an objective, fact-based baseline of its current operational reality.

In the BABOK® Guide v3, current state analysis is not merely a documentation exercise. It establishes the vital context that prevents organizations from solving the wrong problem, building incompatible technical architectures, or underestimating cultural resistance.

+-----------------------------------------------------------------------------------+
|                             BABOK Task 6.1 Structure                              |
+-----------------------------------------------------------------------------------+
|  INPUTS:                                                                          |
|  * Needs (High-level problem, opportunity, or strategic directive)               |
|                                                                                   |
|  ELEMENTS:                                                                        |
|  1. Business Needs (Problems, opportunities, and strategic goals)                 |
|  2. Organizational Capabilities and Processes (Current performance & capacity)    |
|  3. Technology and Infrastructure (Applications, hardware, technical debt)        |
|  4. Policies and Business Rules (Operating constraints, regulatory rules)         |
|  5. Business Architecture (Structure, value streams, operating models)            |
|  6. Internal Assets (Financial capital, intellectual property, human talent)      |
|  7. External Influences (Industry trends, competitors, macro environment)         |
|                                                                                   |
|  OUTPUTS:                                                                         |
|  * Current State Description (Context, capabilities, assets, and pain points)     |
|  * Business Requirements (High-level goals and desired outcomes of the enterprise)|
+-----------------------------------------------------------------------------------+

---

The BACCM™ in Current State Analysis

The Business Analysis Core Concept Model™ (BACCM™) provides the conceptual foundation for analyzing the current state:

• Change: Understands the forces driving change and the current state's capacity to absorb change.
• Need: Identifies the fundamental pain point, unmet customer demand, or strategic opportunity triggering analysis.
• Solution: Assesses the strengths, weaknesses, and technical debt of existing systems and manual workarounds.
• Stakeholder: Analyzes current roles, power structures, skill sets, and cultural attitudes toward transformation.
• Value: Baselines the value currently delivered to customers and identifies where value leakage or waste occurs.
• Context: Evaluates internal organizational culture and external industry, legal, and economic environments.

---

Analyzing External Influences

Enterprises do not operate in a vacuum. External environmental forces constantly exert pressure on organizational performance. Business analysts apply structured frameworks to analyze these macro and micro environmental factors.

1. PESTLE Analysis (Macro Environment)

2. Porter's Five Forces (Micro / Industry Environment)

                             +----------------------------+
                             |   Threat of New Entrants   |
                             |  (Barriers to entry, tech) |
                             +--------------+-------------+
                                            |
                                            v
+----------------------------+   +----------------------------+   +----------------------------+
| Bargaining Power of        |-->|   Industry Rivalry         |<--| Bargaining Power of        |
| Suppliers (Vendor lock-in) |   | (Price wars, differentiation) | Buyers (Switching costs)   |
+----------------------------+   +----------------------------+   +----------------------------+
                                            ^
                                            |
                             +--------------+-------------+
                             |    Threat of Substitutes   |
                             | (Alternative business models)|
                             +----------------------------+

• Industry Rivalry: The intensity of competition among existing market players. High rivalry compresses profit margins and demands rapid innovation.
• Threat of New Entrants: The ease with which new competitors enter the market. Low capital requirements and cloud platforms reduce barriers to entry.
• Threat of Substitute Products/Services: Alternative ways customers can satisfy their needs (e.g., peer-to-peer payment apps substituting traditional retail bank wire transfers).
• Bargaining Power of Buyers: The influence customers have on pricing and quality. Low switching costs give buyers immense leverage.
• Bargaining Power of Suppliers: The control vendors exert over pricing, availability, and terms (e.g., sole-source ERP vendor contracts).

---

Analyzing Internal Capabilities and Business Architecture

To build a comprehensive Current State Description, the business analyst evaluates several internal enterprise dimensions:

1. Organizational Capabilities & Processes: Mapping existing business processes, evaluating process cycle times, bottlenecks, throughput, and error rates.
2. Technology and Infrastructure: Cataloging existing software applications, hardware assets, integration protocols, database architectures, and technical debt.
3. Policies and Business Rules: Examining the explicit directives, regulatory mandates, and operational guidelines that govern business decisions.
4. Business Architecture: Reviewing the organizational structure, capability maps, information maps, and value streams that depict how the enterprise creates value.
5. Internal Assets: Quantifying tangible assets (cash, real estate, physical inventory) and intangible assets (brand reputation, patents, proprietary algorithms, human institutional knowledge).

---

Root Cause Analysis: Distinguishing Symptoms from Problems

A critical failure in business analysis is confusing symptoms with the underlying root cause. Treating symptoms results in expensive solutions that fail to deliver expected business value.

1. The Ishikawa / Fishbone (Cause-and-Effect) Diagram

The Fishbone diagram organizes potential causes of a problem into structured categories radiating from a central problem statement (the "head" of the fish).

  Methods                 Machines                  People
     \                       \                        /
      \-- Inconsistent SOP    \-- Outdated Server    /-- High Turnover
       \                       \                    /
--------+-----------------------+------------------+-------------------> [ PROBLEM: High Order
        /                       /                   \                           Defect Rate ]
       /-- Raw Material Flaw   /-- Inaccurate Meter  \-- Conflicting SLAs
      /                       /                        \
  Materials              Measurements               Environment / Policies

Common Categorization Frameworks:

• The 6 Ms (Manufacturing / Operations): Manpower (People), Machinery (Technology), Methods (Process), Materials, Measurements (Metrics), Mother Nature (Environment).
• The 8 Ps (Services / Product Management): Product, Price, Promotion, Place, Process, People, Physical Evidence, Productivity & Quality.
• The 4 Ss (Administration / Service): Surroundings, Suppliers, Systems, Skills.

2. The 5 Whys Technique

The 5 Whys is an iterative interrogative technique used to drill down through layers of symptoms to reach the root cause:

1. Why did the client invoice contain incorrect billing amounts? — Because the automated billing script used outdated tariff rates.
2. Why did the script use outdated tariff rates? — Because the rate table was not updated after the quarterly product price revision.
3. Why was the rate table not updated? — Because the pricing committee sent the price revisions via email rather than logging them in the central product management system.
4. Why did the committee use email? — Because there is no standardized operating procedure or system integration between the pricing committee and the billing operations team.
5. Why is there no standardized operating procedure or system integration? — Root Cause: The enterprise lacks end-to-end governance and cross-departmental data synchronization for product lifecycle changes.

---

Realistic Enterprise Case: OmniPay Financial Services

Context: OmniPay Financial, a digital payment processor, experiences a 42% drop in new merchant account onboarding completion over two quarters. Senior executives assume the user interface (UI) is unappealing and propose a $1.2M front-end redesign.

The BA's Current State Investigation:

1. Process Analysis: The lead BA traces the merchant onboarding value stream. While the front-end application takes only 8 minutes to complete, back-end verification stalls for 11 business days.
2. Root Cause Analysis (Fishbone & 5 Whys): The BA discovers that Know-Your-Customer (KYC) compliance checks require manual cross-referencing across four disconnected legacy government databases due to unintegrated back-office systems.
3. External Context (PESTLE): New anti-money laundering (AML) regulatory mandates doubled the required verification data points, overwhelming the manual compliance operations team.
4. Outcome: The BA reframes the Business Need from "Redesign onboarding UI" to "Automate regulatory KYC data orchestration and integrate back-office compliance APIs." The enterprise saves $1.2M in unnecessary front-end redesign and solves the true operational bottleneck.

---

Key BABOK v3 Techniques for Task 6.1

• Benchmarking and Market Analysis: Comparing internal enterprise performance metrics against industry peers to pinpoint capability gaps.
• Business Capability Analysis: Assessing the maturity, performance, and strategic importance of current business capabilities.
• Document Analysis: Harvesting business rules, system specifications, standard operating procedures, and audit findings.
• Financial Analysis: Evaluating current operating costs, revenue streams, and financial burn rates.
• Process Analysis: Identifying waste, bottlenecks, non-value-added activities, and cycle-time delays in current workflows.
• Root Cause Analysis (Fishbone / 5 Whys): Diagnosing the fundamental underlying causes of organizational problems.
• SWOT Analysis: Synthesizing internal Strengths and Weaknesses with external Opportunities and Threats.

---

Exam Tips & Common Traps for CCBA Candidates

[!IMPORTANT] Inputs and Outputs of Task 6.1:

• Input: Needs (the preliminary, unvalidated problem or opportunity).
• Outputs: Current State Description (the comprehensive baseline of current capabilities, context, and assets) and Business Requirements (the high-level business goals that must be achieved).

Common CCBA Traps:

• ❌ Trap 1: Jumping into solution design during Current State Analysis. If a question describes a BA evaluating vendor software packages or writing user stories before fully defining the business problem, the BA has skipped Task 6.1.
• ❌ Trap 2: Treating symptoms as the root problem. Always look for the foundational systemic or process breakdown rather than superficial operational manifestations.
• ❌ Trap 3: Overlooking external influences. An analysis of current state is incomplete if it only looks internally at software and staff without considering regulatory (PESTLE) and competitive (Porter's Five Forces) constraints.