The operating playbook that scaled across jurisdictions when most multi-state portfolios fragment under their own complexity.
Hana Group operated twenty-one quick-service franchise units across six states. The units sat inside major host environments: Whole Foods, Walmart, Sam's Club, and Target. California, Nevada, Hawaii, Montana, Wyoming, Texas. Each state had its own regulatory regime. Each host had its own facilities-coordination requirements. Each unit had its own market dynamics, opening-cohort history, and management bench.
I joined as Regional Operations Director. The mandate was to make the portfolio behave as one operating system instead of twenty-one. The mandate underneath that was to do it without disrupting unit-level operating cadence or pushing the existing managers out.
Direct host-environment relationships. Running twenty-one franchise units inside four major retailers meant working directly with the regional operations, facilities, and category management teams at Walmart, Sam's Club, Whole Foods, and Target. Negotiating store-level operating windows. Coordinating compliance documentation against each retailer's specific protocols. Sitting in regional reviews with their leads. Escalating incidents through their chain of command when they crossed the threshold. The host relationships were as much a part of the operating job as the franchise units themselves.
Multi-state portfolio operations look like a scale problem from the outside. They're not. They're a coordination problem. The operators who fail at multi-state treat it as more of the same and try to throw bodies at the variance. The operators who succeed build the systems that make coordination invisible.
When I started, three specific symptoms named the underlying disease. The compliance regimes didn't match. Each state required different inspection protocols, different incident-reporting cadences, different documentation. A high-risk issue in one state had a different escalation path than the same issue in the next state over. The KPIs across units weren't comparable. Unit-level scorecards looked similar but counted different things underneath. A "good" margin number in one unit reflected a different cost structure than the same number in another. The opening cadence varied by jurisdiction. A new unit in California took twice as long to come online as the same unit type in Nevada because the permit work and host-coordination steps weren't standardized across the team.
Underneath all three: the portfolio depended on heroics. Specific people held specific institutional knowledge in their heads. When they were unavailable, the system slowed. That's the operating signature of a portfolio that hasn't been built yet.
Documented the SOPs that the longest-tenured managers carried in their heads. Built the version that didn't depend on any single person knowing the answer. Wrote them in a structure that answered one specific question per page: what does good look like for this part of the work, and how would you know if you were doing it wrong. The first batch was too rigid. The second batch was too vague. The third batch shipped.
The first job of multi-unit operations isn't growth. It's making the units comparable apples to apples so the real signal is visible. We normalized the scorecard so the same number meant the same thing in California and Texas. KPI variance dropped fifteen percent inside a year. Two units we'd been treating as "underperformers" turned out to be top quartile when adjusted for market type and unit age. Two units we'd been celebrating as "top performers" were actually average. We redirected operating attention based on the corrected view.
The six-state regulatory variance was the operational risk that looked smallest and was actually largest. One mishandled compliance escalation could have shut down units, drawn fines, and damaged the host relationships that the entire portfolio depended on. I built the incident-classification framework, the escalation paths by state, and the corrective-action playbook. Six critical incidents per quarter handled with zero penalties on record. Across all six states. For the entire four-year tenure.
Twelve-plus new stores opened in a single year. The number sounds aggressive. The point is that none of those openings disrupted the existing units. The playbook for new-store launch was standardized: the permit work, the host-coordination steps, the local hiring sequence, the SOP rollout, the first-thirty-days operating review. New units came online without pulling the regional ops team away from the operating cadence of the existing portfolio.
Standardized frameworks reduced KPI variance fifteen percent inside a year. Unit-level profitability rose seven percent under the standardized operating model. Sustained ninety-eight percent regulatory compliance across the portfolio. Six critical incidents per quarter resolved with zero penalties on record. Twelve-plus new stores opened in a single year without disrupting the operating cadence of the existing units.
Three things stayed with me from the Hana years. Standardization before scale. Twenty-one units don't behave as one operating system unless you make them. The unsexy compounding work of variance reduction is what lets the obvious growth moves work. Variance is the signal. Once KPIs are comparable, you find out which units are actually operating well and which ones are coasting on market dynamics. That diagnostic is impossible until the data is normalized. Compliance is operating leverage, not operating cost. Six states, zero penalties, six critical incidents per quarter handled cleanly. That track record is what kept the host relationships and the franchise license intact across the entire portfolio.
The playbook that worked across six states inside four major retailers is the same playbook I would deploy in the next multi-unit operating role. Different industry, different jurisdictions, same operating rule.
The lessons section on the homepage pulls patterns from this engagement and four others. The Zareen's case study covers the hospitality reset that ran in parallel. The full story page tells how this chapter fits into sixteen years.
To talk about operating roles where this playbook applies, start the conversation.