BSC MANAGEMENT
Navigating Regulatory Disruption & Operational Fragmentation
Navigating Regulatory Disruption & Operational Fragmentation
Most operational problems develop gradually. This one arrived all at once.
In 2019, California’s AB5 legislation fundamentally changed how businesses could classify independent contractors. For BSC Management, which operated a portfolio of nightlife venues across San Francisco built around contractor-driven revenue models, the impact was immediate and structural. Hundreds of individuals would need to transition into traditional employment classifications, bringing new payroll costs, scheduling obligations, and compliance requirements with them. But the regulatory shift did not create BSC’s operational problems. It exposed them. Behind the scenes, communication between corporate departments and location teams had already begun to fragment. Information was moving slowly. Ownership between roles was unclear. Projects were stalling at the seams between departments. The regulatory change simply accelerated the moment when those weaknesses could no longer be ignored. My role was to diagnose where the system had broken down, rebuild the communication infrastructure that would allow the organization to function clearly, and address the location-level operational gaps that had accumulated while no one was looking closely enough.
BSC Management operated a portfolio of eight nightlife venues across San Francisco, each with its own identity, management team, and customer base. Supporting all eight locations were centralized corporate functions covering human resources, marketing, information technology, and vendor management. On paper the structure was logical. In practice it created a persistent operational problem that I recognized the moment I arrived. When centralized departments serve multiple locations simultaneously, ownership becomes ambiguous. A GM assumes corporate is handling a project. Corporate assumes the GM is handling it. Both are partially right and neither is fully accountable. Information moves through the organization but decisions don’t. Projects stall not because anyone is failing but because no one has clearly defined who owns which piece and what needs to happen before the next person can act. Across eight locations with four overlapping support functions, those gaps compounded constantly. GMs and department heads were regularly frustrated with each other over work that each believed was the other’s responsibility. The organization wasn’t broken. It was operating without a governance layer that told anyone where their authority ended and the next person’s began.
San Francisco’s nightlife environment added a layer of complexity that made operational clarity even more critical. The city operates under strict regulatory oversight, high operating costs, and intense competition for both staff and customers. Profit margins in nightlife are highly sensitive to labor structures. Small changes in staffing costs can dramatically alter the financial performance of a venue. When AB5 took effect, BSC’s venues suddenly faced significantly higher labor costs while still needing to maintain the entertainment environments that drove their revenue. At the same time, the communication gaps already present in the organization made it difficult for leadership to understand how each location was responding to these changes. The organization needed more than compliance adjustments. It needed operational clarity and it needed it quickly.
The communication breakdown between departments was visible immediately. Each club operated reasonably well as an individual unit. The problems lived in the space between them and the corporate functions that supported them. HR, marketing, IT, and vendor management were each serving eight locations simultaneously, but without clear ownership lanes defining where corporate responsibility ended and GM responsibility began. Projects would reach a handoff point and stop moving. Both sides believed the other was handling the next step. By the time the gap was identified, time had been lost and frustration had accumulated on both sides. At the location level, a different set of issues emerged. Each club had developed its own operational habits over time. Some were underutilizing available marketing tools. Others had IT infrastructure problems that had gone unresolved long enough to start affecting operations. Inventory ordering practices had drifted from best practices, creating waste and reducing the efficiency of product movement. Labor structures at several locations had developed inconsistencies that were affecting both cost management and service delivery. None of these were catastrophic individually. Together they represented the accumulated cost of operating without consistent oversight. The regulatory shift made addressing them urgent rather than optional.
Stabilizing the organization required working at two levels simultaneously. The first was the governance layer. Before any location-level fixes could hold, the communication infrastructure between corporate departments and GMs needed to be rebuilt around clear ownership. The first step was mapping the limits of each role and understanding exactly what decisions each position was authorized to make independently, what required collaboration, and what required sign-off from leadership before moving forward. Once those boundaries were defined, a project workflow was developed that allowed work to move from conception to completion without stalling at the handoff points between departments. Every project had a clear owner at each stage. Approval thresholds were defined so that individuals knew how much latitude they had before escalation was required. The ambiguity that had been creating friction between GMs and department heads was replaced with a structure that told everyone exactly where they stood. The second level was location-specific. With clearer visibility into how each venue was actually functioning, location-level gaps became addressable. Marketing tool utilization was audited across all eight locations and underutilized capabilities were activated and trained. IT infrastructure issues were identified and resolved, removing friction from daily operations that had become normalized rather than fixed. Inventory ordering practices were restructured to reduce waste and improve product movement efficiency. Labor structures were reviewed and inconsistencies were addressed, improving both cost management and service delivery. Each location required a different combination of interventions. The governance structure built at the corporate level made it possible to deploy those interventions systematically rather than reactively.
Regulatory disruption forces organizations to reconsider how value flows through their businesses. When labor structures change, revenue models often need to evolve alongside them. Rather than simply reacting to the compliance requirements of AB5, I developed The Strategic Opportunity Engine to evaluate how revenue was distributed across operational categories and identify areas where growth opportunities might still exist within the evolving model. Most organizations in a period of regulatory disruption focus entirely on cost containment. The Strategic Opportunity Engine reframed the question. Instead of asking only where costs were increasing, it asked where value was still being created and where operational energy should be directed to protect and grow it. By analyzing category performance and revenue distribution across the portfolio, the engine helped reveal segments of the business that remained strong despite the regulatory shift. These insights allowed leadership to focus operational energy on the areas most capable of sustaining revenue growth rather than attempting to preserve a model that the regulatory environment had already changed.
During periods of rapid change, leadership faces a specific and dangerous problem: too much information arriving simultaneously with too little clarity about what it means. Individual location reports were coming in regularly but synthesizing them into a coherent picture of how the portfolio was responding to the regulatory change was difficult. Decisions were being made against incomplete visibility. The Executive Decision Engine was developed to solve that problem. Rather than relying on isolated metrics from individual locations, the system synthesized revenue performance, efficiency indicators, and category balance data simultaneously across the portfolio. This gave leadership the ability to observe the broader operational patterns shaping the organization rather than reacting to individual location signals in isolation. Instead of asking what is happening at Location A or Location B, leadership could ask what is happening across the system and make decisions about staffing structures, operational adjustments, and strategic priorities from that vantage point. The regulatory change could not be reversed. But the organization’s ability to understand and respond to it could be significantly strengthened.
Despite the scale of the regulatory disruption, BSC was able to transition its operational structure to meet California’s new labor requirements without losing the operational consistency that held the portfolio together. The governance framework built between corporate departments and location teams gave the organization a clarity it had not previously had. Projects moved from conception to completion without stalling. GMs and department heads understood their ownership lanes. Location-level operational gaps across marketing, IT, inventory, and labor were identified and addressed systematically. More importantly, the organization emerged from one of the most disruptive regulatory moments the industry had experienced with stronger operational infrastructure than it had going in. The challenge had exposed weaknesses in the system. Addressing those weaknesses ultimately strengthened it.
This role taught me something I have carried into every engagement since: the most dangerous operational problems are not the ones that announce themselves. They are the ones that have been quietly normalized.
The communication breakdown at BSC had been present long before AB5 arrived. GMs and department heads had developed workarounds. Projects moved slowly but they moved. The friction was real but it was manageable enough that no one had been forced to address it directly. The regulatory shift didn’t create the problem. It removed the conditions that had allowed the organization to tolerate it.
That pattern repeats itself across organizations of every type and size. Systems develop gaps. People adapt to those gaps rather than closing them. Over time the adaptations become the standard operating procedure and the underlying gap becomes invisible. It is only when external pressure removes the ability to adapt that the structural problem finally becomes visible enough to fix.
The second lesson was about the value of governance before intervention. My instinct when I arrived was to start fixing the location-level problems I could see immediately. What I learned was that location-level fixes don’t hold without a governance structure that tells everyone how decisions get made and who owns what. Building that layer first made everything else more effective. The order of operations matters as much as the operations themselves.