7.4 Assess Enterprise Limitations

7.4 Assess Enterprise Limitations

Purpose of Task 29

The primary objective of Task 29: Assess Enterprise Limitations is to identify factors external to the solution component itself that prevent the enterprise from realizing the full value of an operational solution. Even a technically perfect solution with zero software defects will fail if organizational culture, broken business processes, improper reporting structures, skill gaps, or governance hurdles block effective adoption.

Task 29 broadens the business analyst's diagnostic focus from software and technology artifacts to the surrounding organizational ecosystem, ensuring that enterprise barriers are recognized and addressed.

---

Inputs, Outputs, and BACCM Relationships

Assessing enterprise limitations evaluates the dynamic interaction between the operational solution and the broader organizational system.

Mapping to the Business Analysis Core Concept Model (BACCM)

• Context: Analyzes organizational culture, political dynamics, regulatory constraints, and market pressures surrounding the solution.
• Need: Evaluates whether enterprise alignment is lacking to support the operational need.
• Solution: Assesses how well the operational solution integrates with surrounding enterprise business processes and human workflows.
• Stakeholder: Examines stakeholder resistance, change management gaps, skills deficits, and mismatched performance incentives.
• Value: Identifies enterprise factors blocking financial ROI and operational benefit realization.
• Change: Assesses organizational capacity to adapt to new operating models required by the solution.

---

Taxonomy of Enterprise Limitations

Enterprise limitations are categorized across four major organizational dimensions:

                            ENTERPRISE LIMITATION TAXONOMY
 ┌───────────────────────────┬───────────────────────────┬───────────────────────────┐
 │   CULTURE & ADOPTION      │ OPERATIONAL & PROCESS     │ STRUCTURE & GOVERNANCE    │
 ├───────────────────────────┼───────────────────────────┼───────────────────────────┤
 │ • Stakeholder Resistance  │ • Outdated SOPs / Manual  │ • Siloed Departmental     │
 │ • Cultural Misalignment   │   Parallel Workarounds    │   Boundaries              │
 │ • Mismatched Incentives   │ • Inadequate Training     │ • Unclear Governance      │
 │ • Change Fatigue          │ • Staffing / Skill Gaps   │   Decision Authority      │
 └───────────────────────────┴───────────────────────────┴───────────────────────────┘

1. Cultural and Stakeholder Readiness Barriers

• Stakeholder Resistance: Active or passive refusal by operational staff to adopt new solution workflows due to fear of job displacement or loss of status.
• Mismatched Compensation Incentives: Sales or operations metrics that reward legacy behaviors rather than solution utilization (e.g., rewarding agents for phone calls while trying to promote a self-service portal).
• Cultural Drift: Organizational norms that clash with solution assumptions (e.g., deploying an agile collaboration tool in a rigid command-and-control hierarchy).

2. Operational and Process Alignment Barriers

• Legacy Parallel Processes: Operational teams continuing manual paper workarounds alongside automated software solutions out of habit or lack of trust.
• Skill and Competency Gaps: Inadequate end-user training programs leaving staff unable to operate advanced solution features effectively.
• Resource Constraints: Understaffed operational teams lacking capacity to process solution outputs or handle exceptions.

3. Organizational Structure and Governance Barriers

• Siloed Departmental Boundaries: Inter-departmental friction or conflicting goals preventing end-to-end process execution across software interfaces.
• Governance Bottlenecks: Onerous multi-tiered approval chains that negate automated software speed advantages.

---

Assessment Frameworks: Force Field Analysis and Cultural Assessment

Senior BAs leverage specialized enterprise evaluation tools during Task 29:

---

Solution Limitations vs. Enterprise Limitations: The CBAP Comparison Matrix

Mastering the distinction between Task 28 and Task 29 is critical for CBAP success:

---

Practical Example: Enterprise Assessment of an Omnichannel Retail CRM Rollout

A global retail corporation deployed an automated Customer Relationship Management (CRM) platform intended to unify online and in-store customer profiles.

1. Observed Performance Gap: In-store associates logged customer interactions in only 18% of store transactions, failing the 85% business target.
2. Investigation Findings:
   • Technical inspection showed the CRM software was fast, bug-free, and mobile-optimized (No Solution Limitation).
   • Enterprise assessment revealed that store associate bonuses were based strictly on checkout line throughput speed, not customer data capture. Logging CRM notes increased checkout time by 30 seconds, directly reducing associate bonuses.
3. Identification of Limitation: The BA identified an Enterprise Limitation: mismatched operational compensation incentives and conflicting performance metrics preventing solution value realization.

---

CBAP Exam Strategy & Distractor Analysis

• Identify the Root Locus: Read scenario details carefully to locate where the barrier lives. If the solution software is working exactly as specified, but people aren't using it due to culture, training, or incentives, select Enterprise Limitation (Task 29).
• Watch for Combined Scenarios: Exam scenarios may present a situation with both technical defects and organizational barriers. Distinguish between software refactoring requirements (Task 28) and change management interventions (Task 29).
• Force Field Analysis Application: Remember that Force Field Analysis explicitly measures Driving Forces vs Restraining Forces in the enterprise environment.