2.2 Current State Analysis & Existing System Evaluation

2.2 Current State Analysis & Existing System Evaluation

Designing a high-performing future state without an accurate understanding of the current state is one of the quickest routes to enterprise software failure. In Salesforce implementations, the "Current State" (the As-Is environment) encompasses both business processes—how human beings actually accomplish their daily work—and the technical ecosystem—the existing Salesforce configuration, integrated legacy applications, databases, and spreadsheets.

A thorough current-state evaluation enables the Salesforce Business Analyst to identify root-cause inefficiencies, catalog technical debt, and discover platform consolidation opportunities that deliver substantial return on investment.

---

The Imperative of "As-Is" Process Discovery

Organizations often believe their operations follow the documented standard operating procedures (SOPs) written in employee handbooks. In reality, daily operations deviate significantly from official documentation. Over time, employees encounter software limitations, missing integrations, or cumbersome approval gates, prompting them to invent informal shortcuts.

Uncovering Shadow IT and Spreadsheet Sprawl

One of the BA's primary objectives during current-state analysis is uncovering Shadow IT and Spreadsheet Sprawl.

• Shadow IT: Hardware, software, cloud services, or browser extensions utilized by employees without organizational IT approval or oversight (e.g., a sales team using an unsanctioned third-party e-signature app or personal Google Drive folders to share contracts).
• Spreadsheet Sprawl: The proliferation of offline, manual Microsoft Excel or Google Sheets files used to track mission-critical operational data that should reside in the core CRM (e.g., pricing calculators, customer commission ledgers, post-sale project trackers).

The BA Insight: Shadow spreadsheets are not signs of employee defiance; they are symptoms of system neglect. When a sales rep tracks renewals in an Excel sheet rather than Salesforce, it indicates that the current Salesforce renewal process is too slow, too rigid, or fails to provide the calculations the rep needs to do their job. Finding these spreadsheets reveals the exact functional requirements the future-state Salesforce design must satisfy.

Gathering and Analyzing As-Is Artifacts

To construct an authentic picture of the current state, the BA must gather and cross-examine a diverse portfolio of operational artifacts:

1. Existing SOPs and Process Maps: Review official documentation to establish baseline institutional expectations.
2. Current Shadow Workbooks and Templates: Collect actual copies of the Excel models, calculators, and trackers actively used by operational teams.
3. Training Materials and Onboarding Guides: Inspect what new hires are taught versus what tenured staff actually do.
4. Historical Report Exports: Analyze the custom reports management currently pulls from Salesforce or legacy databases to understand what metrics drive leadership decisions.
5. Audit Logs and System Error Reports: Review login histories, apex exception emails, and user error tickets logged with the internal IT help desk.

---

Evaluating Salesforce Technical Debt & Org Health

When a project involves an existing Salesforce environment (rather than a greenfield implementation), the BA must evaluate the health of the org. Over years of operation, orgs accumulate technical debt—the implied cost of future rework caused by choosing quick, suboptimal solutions over robust architectural designs.

The Automation Pile-Up: Multi-Engine Conflicts

Before Salesforce unified declarative automation under Salesforce Flow, administrators and developers used a combination of Workflow Rules, Process Builders, and Apex Triggers. Mature orgs frequently suffer from an "automation pile-up," where all three engines operate simultaneously on the same object (e.g., the Opportunity object).

[Record Saved] 
   ├── 1. Workflow Rules fire (Field updates force re-save)
   ├── 2. Process Builders fire (Multiple independent processes)
   ├── 3. Apex Before/After Triggers execute
   └── 4. Record-Triggered Flows execute
       └── Result: Non-deterministic order of execution, CPU timeouts, and lock errors!

The Danger of Multi-Engine Architecture:

• Non-Deterministic Execution Order: When multiple workflow rules, process builders, and flows trigger on the same event, Salesforce does not guarantee which one executes first (except across broad engine categories). A Process Builder may overwrite a value that a Workflow Rule just updated, triggering unexpected recursive updates.
• Apex Governor Limit Breaches: Recursive saves consume SOQL query limits (100 synchronous / 200 asynchronous) and CPU time limits (10,000 milliseconds synchronous), causing fatal unhandled exceptions during bulk data updates.
• Modernization Mandate: The BA must identify legacy Workflow Rules and Process Builders so the technical team can budget their refactoring into unified, well-architected Record-Triggered Flows adhering to the one-flow-per-object-per-type design pattern (or subflow orchestration frameworks).

Customization Bloat and Schema Degradation

Technical debt also corrupts the Salesforce data model:

• Field Limit Saturation: Enterprise Edition orgs allow up to 800 custom fields per object. Organizations that never conduct current-state audits often find objects like Account or Case sitting at 750+ fields, preventing the creation of new features.
• Dormant Fields (Low Data Utilization): Audits frequently reveal that 30% to 50% of custom fields have a 0% data population rate across records created in the last 12 months.
• Redundant Custom Objects: Legacy teams may have created custom objects that duplicate standard Salesforce capabilities (e.g., creating a custom Invoice_Item__c object instead of using standard Opportunity Products or Order Line Items).

Org Health Diagnostic Tools

The BA does not have to analyze technical debt manually. Salesforce provides built-in diagnostic tools that generate objective data:

• Salesforce Optimizer: An automated utility that inspects the org and generates an interactive report highlighting inactive automations, unused custom fields, unassigned page layouts, sharing rule complexity, and custom code lacking test coverage.
• Salesforce Health Check: Evaluates the org’s security baseline against Salesforce-recommended standards, identifying vulnerable session settings, password policies, and excessive administrative permissions.
• Storage Usage Analyzer: Under Setup, displays total data storage and file storage consumption by object, identifying data archiving needs.

Org Health Audit Checklist

---

Mapping the Enterprise Application Landscape

Modern enterprise Salesforce implementations do not exist in isolation. Salesforce serves as a hub within an integrated ecosystem of enterprise applications. A primary BA deliverable during current-state analysis is an Enterprise Application Landscape Map that catalogs every interacting system, data boundary, and integration dependency.

Systems of Record vs. Systems of Engagement

To prevent architectural chaos, the BA must clarify the role of each system:

• System of Record (SoR): The authoritative data source for a specific data entity. There must be only one System of Record for any given data attribute.
  • Example: An Enterprise Resource Planning (ERP) platform like SAP or NetSuite is the System of Record for financial invoices, general ledger entries, and final inventory levels. Salesforce must not attempt to act as the SoR for accounting ledgers.
• System of Engagement (SoE): The primary software interface where end users interact with data, collaborate, and execute their day-to-day workflow.
  • Example: Salesforce Sales Cloud is the System of Engagement for account executives managing customer interactions, opportunities, and quotes, even if final customer billing records reside in the ERP.
• System of Reference (SoRef): A secondary system that stores a replicated copy of data from the System of Record for display, reporting, or local context.

Integration Profiles: Latency and Directionality

When evaluating current-state integrations, the BA must document four critical parameters for every system touchpoint:

1. Data Entities Exchanged: Exactly which records and fields move between systems (e.g., Accounts, Contacts, Orders, Line Items)?
2. Directionality:
   • Unidirectional (Inbound or Outbound): Simpler, lower risk of data collisions (e.g., Marketing Cloud synchronizes campaign engagement metrics one-way into Salesforce Tasks).
   • Bidirectional: High complexity; requires strict master data management (MDM) rules and timestamp conflict resolution to prevent infinite sync loops.
3. Integration Timing and Latency:
   • Real-Time / Synchronous (REST/SOAP API): Data transfers immediately during user interaction (e.g., real-time credit check on an account before quote submission).
   • Near-Real-Time (Platform Events / Change Data Capture): Asynchronous event messaging that decouples systems while updating within seconds.
   • Batch / Scheduled ETL (Bulk API / MuleSoft / Informatica): Large volume data synchronizations executed at off-peak hours (e.g., nightly sync of ERP billing history).
4. Integration Protocol & Middleware: Document whether systems connect via enterprise middleware (e.g., MuleSoft, Boomi), native AppExchange connectors, or custom point-to-point web services.

---

Documenting Gaps & Modernization Opportunities

The culmination of current-state analysis is translating discovered pain points and technical limitations into a structured Gap Analysis Matrix. This document bridges the discovery phase to the future-state architecture, serving as the business justification for platform modernization and consolidation.

The Gap Analysis Framework

For each operational domain, the BA records:

• As-Is Process: The current workflow, including workarounds and manual handoffs.
• Current Operational Pain: The measurable cost, delay, or risk imposed on the organization.
• To-Be Vision: The desired future-state operating model.
• Identified Gap: The specific technological or operational missing link.
• Salesforce Modernization Opportunity: The platform capability that resolves the gap.

Worked Gap Analysis Matrix: Apex Industrial Supplies