5.1 Analyze Current State
Key Takeaways
- Analyzing current state evaluates the existing operational, technical, and architectural capabilities of an enterprise to establish a realistic baseline for change.
- The Business Need serves as the primary driver for strategy analysis, originating from top-down strategic goals, bottom-up operational pain points, or external regulatory/market pressures.
- Strategic analysis frameworks like SWOT, PESTLE, and Porter's Five Forces evaluate internal strengths/weaknesses alongside macro-environmental and industry competitive dynamics.
- Root cause analysis techniques—such as the 5 Whys, Ishikawa (Fishbone) diagrams, and Pareto charts—prevent business analysts from misdiagnosing surface symptoms as fundamental business problems.
- In the Business Analysis Core Concept Model (BACCM), analyzing the current state requires understanding how the current Context shapes Stakeholder perceptions of Value and unmet Needs.
5.1 Analyze Current State
Purpose and Role of Current State Analysis in BABOK v3
The primary purpose of Analyze Current State (BABOK Guide v3 Task 6.1) is to understand the business need and how an enterprise currently operates today. Before an organization can define where it wants to go or select a solution, it must build a rigorous, objective understanding of why change is required, what capabilities currently exist, and what baseline constraints shape the operating environment.
Current state analysis provides the foundational context for all subsequent Strategy Analysis tasks. Without a thorough baseline evaluation, enterprise transformations risk building solutions that address superficial symptoms rather than root causes, duplicate existing capability investments, or fail due to unacknowledged organizational cultural barriers.
Deconstructing the Business Need
The Business Need is the initial trigger for business analysis work. It defines the problem or opportunity facing the enterprise that necessitates change. According to BABOK v3, business needs can originate from multiple levels within and outside the organization:
- Top-Down Strategic Drivers: Executive leaders establish strategic goals (e.g., expanding into international markets, increasing customer retention by 15%, or transitioning to a SaaS business model) that require internal operational realignment.
- Bottom-Up Operational Drivers: Frontline staff, process owners, or IT units identify internal inefficiencies, legacy system bottlenecks, high defect rates, or manual workarounds that erode profitability.
- External Environment Drivers: External pressures—such as new compliance mandates, shifting macroeconomic conditions, technological disruptions, or aggressive competitor actions—force the enterprise to adapt.
A critical responsibility of the CBAP practitioner is to critically evaluate business needs rather than accepting initial stakeholder requests at face value. Business needs must be articulated in terms of the business problem to be solved or the strategic opportunity to be realized, independent of any specific technical solution.
Enterprise Architecture & Current Capability Assessment
To evaluate how an organization fulfills its current mission, the business analyst must inspect the enterprise architecture across four primary domains:
| Architecture Domain | Current State Analysis Focus | Key Artifacts & Elicitation Targets |
|---|---|---|
| Business Architecture | Core business functions, process models, organizational structures, roles, and decision-making governance. | Value stream maps, business capability maps, organizational charts, RACI matrices. |
| Data & Information Architecture | How data is captured, stored, transformed, governed, and distributed across the enterprise. | Conceptual data models, data dictionaries, entity-relationship diagrams (ERDs), data lineage maps. |
| Applications Architecture | Software applications, legacy systems, integrations, API endpoints, and technical debt. | Application inventory lists, interface control documents, software dependency diagrams. |
| Technology Architecture | Infrastructure, cloud environments, hardware networks, security protocols, and operational facilities. | Infrastructure topology diagrams, deployment models, hardware lifecycle schedules. |
Analyzing Business Capabilities—the enterprise's ability to execute a specific activity to achieve a business outcome—helps identify capability gaps, redundancies, and performance bottlenecks. Capability assessments evaluate not just tools, but the holistic alignment of people, processes, information, and infrastructure.
Internal and External Environmental Assessment Frameworks
To understand the context surrounding the enterprise, senior business analysts employ structured strategic frameworks:
1. PESTLE Analysis (External Macro-Environment)
PESTLE categorizes macro-environmental factors that influence enterprise strategy:
- Political: Government policies, trade tariffs, tax reform, election cycles.
- Economic: Inflation rates, exchange rates, interest rate trajectories, consumer spending power.
- Socio-cultural: Demographic shifts, cultural values, lifestyle trends, workforce expectations.
- Technological: Artificial intelligence adoption, cloud migration, cybersecurity threats, automation.
- Legal/Regulatory: Data privacy legislation (e.g., GDPR, CCPA), industry compliance, labor laws.
- Environmental: Sustainability targets, carbon footprint regulations, climate risk resilience.
2. Porter's Five Forces (Industry Competitive Structure)
Porter's model evaluates the competitive intensity and profitability potential of an industry:
- Threat of New Entrants: Barriers to entry, capital requirements, brand loyalty.
- Bargaining Power of Buyers: Customer price sensitivity, switching costs, buyer concentration.
- Bargaining Power of Suppliers: Supplier concentration, uniqueness of inputs, switching costs.
- Threat of Substitutes: Availability of alternative products or services fulfilling the same core need.
- Competitive Rivalry: Number and capability of direct market competitors, industry growth rate.
3. SWOT Analysis (Internal & External Synthesis)
SWOT synthesizes internal capabilities with external market conditions:
- Strengths (Internal): Unique enterprise capabilities, proprietary IP, strong brand equity, financial reserves.
- Weaknesses (Internal): Legacy technical debt, siloed organization, skill gaps, inefficient processes.
- Opportunities (External): Emerging market segments, unserved customer niches, strategic partnerships.
- Threats (External): Aggressive competitor pricing, shifting regulatory mandates, economic downturns.
Root Cause Analysis: Distinguishing Symptoms from Root Problems
A common pitfall in strategy analysis is treating surface-level symptoms while leaving underlying systemic causes untouched. The CBAP practitioner uses formal root cause analysis techniques to isolate primary failure points:
- 5 Whys Technique: Iterative interrogative technique asking "Why?" repeatedly (typically five times) to drill down through layers of operational symptoms to the root cause.
- Ishikawa (Fishbone) Diagram: Visual diagram categorizing potential causes of a problem into standard categories such as People, Process, Technology, Materials, Measurement, and Environment.
- Pareto Analysis (80/20 Rule): Statistical technique demonstrating that approximately 80% of business problems or defects stem from 20% of causes. Business analysts use Pareto charts to prioritize high-impact root causes for remediation.
BACCM Connection: Current State Analysis
Under the Business Analysis Core Concept Model (BACCM), analyzing current state establishes baseline relationships:
- Context: The external and internal environment shaping enterprise operations.
- Need: The unsatisfied business problem or unexploited opportunity in the current state.
- Solution: Existing operational tools and workflows (which may be underperforming).
- Stakeholder: Persons impacted by current operational inefficiencies.
- Value: The current baseline value delivered versus potential value lost due to operational gaps.
- Change: The delta required to move from the current baseline to an enhanced state.
CBAP Exam Tips & Strategic Guidance
- Exam Strategy: When faced with a case study scenario where stakeholders demand an immediate software platform replacement, the correct BABOK response is always to perform a current state analysis and root cause investigation first before committing to solution options.
- Inputs to Task 6.1: Remember that Elicitation Results (confirmed) and Needs are primary inputs to Analyze Current State. The key output is Current State Description.
An executive vice president claims that customer drop-off on an e-commerce platform is caused by poor user interface design. A senior business analyst conducts a structured investigation and discovers that order processing database locks cause 15-second transaction delays, driving user abandonment. Which technique did the business analyst apply?
A global financial institution must evaluate how upcoming international data privacy laws, shifting exchange rates, and emerging cloud AI security mandates will affect its long-term strategy. Which analytical framework is most appropriate?
When assessing enterprise capabilities during current state analysis, a business analyst notes that while modern software tools are installed, operational staff lack standardized procedures and data definitions are inconsistent across business units. What BABOK principle does this highlight?
An enterprise logistics department discovers that 80% of customer billing adjustments stem from errors made in 20% of manual entry fields on shipping manifests. Which tool visually demonstrates this distribution?