P2 Sphere: Decoupling Enterprise Construction Finance at Scale

01. The Problem Space: Institutional Technical Debt

Comcast’s Next Generation Access Network (NGAN) powers national broadband infrastructure builds. For years, the complex financial orchestration behind this work—tracking physical fiber builds, managing contractor purchase orders, reconciling invoices, and auditing multi-million-dollar regional capital allocations—relied on deeply customized legacy Salesforce instances.

Over time, each operating division (Northeast, Central, and West) had introduced localized customizations. This created extreme structural divergence: identical financial reconciliation tasks required entirely different procedures depending on which regional team was executing them.

The operational friction was severe. When financial controllers or network project managers sat down to review or approve an infrastructure batch, they routinely worked across 10 to 15 open browser tabs simultaneously. They were manually copying job codes from legacy tracking screens, pasting them into accounting views, cross-checking vendor line items, and manually calculating variances on secondary desk monitors. Beyond the recurring licensing overhead of keeping 115,000+ users inside proprietary third-party software, the cognitive fatigue led to high error rates in job costing and multi-week training overhead for incoming personnel.

02. Field Inquiry: Shadowing The Ground Reality

In enterprise software, leadership documentation almost never reflects the reality of daily work. The documented workflow was a linear three-step process; the actual workflow was an improvised workaround built out of sticky notes, keyboard macros, and secondary spreadsheets.

To establish empirical baselines before proposing architecture, I conducted immersive field shadowing across all three operating divisions. I sat beside national project coordinators, construction estimators, and regional finance directors, observing them through peak billing cycles:

• Click-Depth & Latency Audits: Documented that standard work-order authorizations required an average of 24 distinct screen transitions and context switches across disparate systems.
• Information Architecture Mapping: Audited 300+ legacy database fields to isolate which data points users actually used to make critical financial decisions versus data that had been passively accumulated over years of system patches.
• Failure Mode Taxonomy: Categorized points of user drop-off and error propagation, discovering that 80% of reconciliation discrepancies stemmed from asynchronous tab reloads that failed to sync state updates back to the parent record.

03. Triad Alignment Across 30+ Cross-Functional Leads

The greatest risk in enterprise software overhauls is political friction: different regional stakeholders resist losing customizations they spent years advocating for.

To build consensus across more than 30 regional directors, senior engineers, and department heads, I established a structured Rapid Triad Cadence:

• Subject Matter Expert (SME) Focus Groups: Weekly working sessions bringing together regional representatives to openly negotiate standardized data fields and deprecate redundant division-specific workflows.
• Design / Engineering / QA Triads: Bi-weekly technical reviews where IA models and interactive workflows were audited directly alongside front-end and back-end leads to ensure database scalability and zero latency spikes.
• Transparent Governance: Publishing every IA decision, state logic diagram, and taxonomy change to an open cross-functional repository, replacing back-channel resistance with collaborative ownership.

04. The Solution: Single-Pane Architecture & Storybook Tokens

P2 Sphere resolved the core fragmentation problem by introducing a unified Single-Pane Workspace Architecture. Instead of forcing users to traverse disconnected platforms, we restructured the platform around consolidated task execution:

Context-Preserving Workspaces

We replaced the multi-tab paradigm with nested, asynchronous slide-out drawers, persistent financial balance cards, and context-aware master-detail tables. Users could inspect purchase order line items, adjust contractor cost allocations, and verify real-time network milestones without ever losing their primary filter state or navigating away from their parent review queue.

Multi-Brand Tokenized Design System

To ensure design integrity survived rapid development cycles across 3 distinct NGAN applications, I architected and governed an enterprise-wide design system built on semantic tokens and atomic components in Storybook:

• Semantic Design Tokens: Decoupled core visual attributes (color, typography, spatial density) from hardcoded CSS, establishing shared tokens consumed directly by production code repositories.
• Data-Dense Enterprise Components: Engineered specialized high-density tables with keyboard-first navigation, sticky header hierarchies, multi-column sorting, and inline cell editing optimized for financial power users.
• WCAG 2.1 AA Governance: Embedded accessibility standards into every component state (focus rings, contrast ratios, assistive screen-reader landmarks), ensuring the platform was accessible across national enterprise divisions.

Azure Access Management (UAM)

Managing compliance for 115,000+ users required enterprise-grade access governance. I solo designed and developed an Azure-integrated User Access Management Dashboard, establishing role-based access control (RBAC), SSO authentication, and automated audit trails governing ~10,000+ monthly logins.

05. Measurable Outcomes & Long-Term Enterprise ROI

The transition from fragmented vendor instances to P2 Sphere represents a benchmark in enterprise digital transformation:

• Massive Operational Scale: Seamlessly scaled to 115,000+ active enterprise users across the Northeast, Central, and West divisions without systemic downtime.
• License Cost Decoupling: Saved millions annually in recurring per-seat vendor licensing fees by repatriating core construction finance into an owned in-house platform.
• Cycle Time Compression: Slashed click depth and context-switching overhead, driving down average work-order reconciliation time from over 20 minutes to under 4 minutes.
• Unified Technical Ecosystem: Unified 3 separate engineering applications under a single Storybook component library, cutting front-end development cycle time in half and virtually eliminating design-to-code regression.