The first time I ran twenty units I ran them like I ran one. I put myself on the schedule at the two that were hurting the most, drove between them, sat in on shift changes, and wrote the schedule myself when the general managers were late. It felt like leadership. It was actually a bottleneck with a suit on.
The lesson took me two quarters to hear, and I did not learn it from a book. I learned it from the fifteen units I was not visiting getting quietly worse while I was rescuing the five I was. That is what running twenty units teaches you, if you let it. The job is not the work you did at one unit repeated twenty times. It is a different job.
What changes when the unit count crosses ten
The math changes before the job changes, and most operators feel the math a full quarter before they name it. At one unit you have roughly forty direct decisions in a week that only you can make. At twenty units, if you try to be the decision maker for each one, you have eight hundred. Nobody has eight hundred decisions in them in a week. You will short circuit, and the units furthest from your seat will pay first.
At Hana Group I inherited 21 franchise units across 6 states, embedded inside Walmart, Sam's Club, Whole Foods, and Target footprints. The P&L was $36M. I never wrote a single unit's schedule at Hana. Not once. If I had, the other twenty schedules would have been written by nobody, and twenty schedules written by nobody is what a bleeding region looks like.
Information latency doubles, then doubles again
At one unit you see the problem live. At three units you hear about the problem by end of shift. At ten you hear about it the next morning. At twenty you hear about it in the weekly report, if it made the report. That latency is not a communication problem. It is a physics problem. The job is to build the standing rhythm that shortens the latency without asking any general manager to text you at 11 p.m.
The average P&L stops telling the truth
A regional number that reads "labor 28 percent" hides a unit at 24 and a unit at 34. The average is calming. The spread is honest. When you take over a region, the first useful thing you can do is build a view that ranks every unit on every key line, worst to best. The number you are managing at the regional level is not the mean. It is the distance between the worst quartile and the median.
Fig. 1 · The job re-shapes itself as the unit count grows.
Three tools that stop working past six units
Here is the operator's grief. The tools that made you good at single-unit work were the same tools that got you promoted. You are being asked to give them up, and the giving up feels like getting worse at your job. Three specifically:
Personal presence
At one unit, being there is most of the job. At twenty, being there in one place means being absent from nineteen. Presence has to be replaced with signal: a good weekly report, a shared dashboard, a general manager who calls you before you call them because they know what the standing agenda expects. Presence becomes a scarce resource you spend on purpose, not a default state.
Personal taste
At one unit, your taste is the standard. The plate looks right because you decided it looks right. At twenty units, your taste has to be written down and taught, or it lives only inside your head, which means it lives at only one of the twenty units. Brand standards, plating photos, tasting rituals: those exist so the standard is portable when you are not there.
Personal fix-it energy
This is the hardest one to let go. Every operator who scaled to a regional seat got there by being the person who could fix anything. At twenty units, if you fix things personally, you are the ceiling. The fix has to move from a thing you do to a thing you teach a general manager to do the next time it happens. The first time is a rescue. The second time is a failure of teaching.
The best regional operators I know are the ones who can name the exact moment they stopped doing the work and started teaching the work. It is always a specific day, and it always felt uncomfortable.
What the twenty-unit job actually is
If it is not doing the work, what is it? Three things, in this order:
Sequencing
You have twenty units, four are on fire, two are excellent, fourteen are somewhere in the middle. You do not have the bandwidth to attack all twenty this quarter. The regional job is choosing which two you attack, in what order, with which tools, and telling the other eighteen why you are not on their site. That is a leadership act, not a scheduling one. Get the sequence wrong and you will be busy but not effective.
Pattern recognition
The same complaint appearing at three units in the same week is not three separate complaints. It is one problem with the same root cause in three places. The regional operator's job is to see that pattern before the district manager does and before the units themselves do, because the district manager is thinking one unit at a time and the units are thinking one shift at a time. Only the regional seat can see the pattern.
Cadence design
Every meeting, every dashboard, every report you create either compounds or decays. The best regional operators design a rhythm that is boring on purpose. Same day. Same time. Same agenda. Same seven metrics. Boring is what scales. Novelty is what breaks under load.
The moment you know the job has changed
There is a specific moment, and you will feel it. It is the first Wednesday you cannot tell your director what happened at every unit yesterday. At three units you could. At six you could. At eleven you probably could not. At twenty you definitely cannot. The first time it happens, it feels like you are failing. It is not failure. It is the shape of the job.
What replaces the "I know what happened at every unit yesterday" is a different kind of knowledge: "I know which unit is drifting on which cost line, I know which general manager needs a conversation this week, and I know what the pattern is across the region." That is regional knowledge. It is a different resolution than unit knowledge. You do not have both at twenty units. Trying to have both is how you burn out.
What I would tell an operator taking their first multi-unit seat
Three things. I wish someone had said them to me.
- Stop writing schedules on day one. Even at the unit that is worst. Your job is not to write the schedule. Your job is to teach the general manager how to write it well, and then to hold them accountable to it. If you write it, you own it, and if you own it you cannot leave.
- Build the standing rhythm in your first thirty days. Weekly one-on-ones with every general manager, same day, same time. Monthly regional operating review with all of them in one room. Quarterly market review with your director. Put the calendar in place before you fix anything, because the calendar is what makes the fix hold.
- Learn to sit still. The urge to be in a truck between units is real. Resist it. The best regional operators I know spend two days a week at a desk reading numbers and one day a week in each of two units. They are not less committed than the operators who live in the truck. They are more effective.
What changes about the P&L conversation
At one unit the P&L conversation is granular. You know why food cost was high last Tuesday. You know which shift had the labor spike. You can walk back through the day and reconstruct the story. At twenty units, that granularity dies. You cannot know why Tuesday was bad at unit fourteen, and you should not try to know. If you try, you will spend your whole week reconstructing days you were not in the room for.
What replaces it is a different conversation. You look at the region as a portfolio. You ask what percentage of your units missed labor by more than two points this week. You ask which cost line moved most across the region. You ask which four units are drifting in the same direction, and what that pattern is telling you about a system change, a vendor change, or a seasonal shift you missed. The unit-level answer is the district manager's job. The pattern-level answer is yours.
At Zareen's during the turnaround, this shift was the hardest one for me personally. I came from a background of knowing every plate on every menu. I had to stop asking about specific plates and start asking about menu mix as a whole. I lost some texture. I gained a view I could not have had from the plate level. Both are true. Neither is the wrong lens. They are the lens the seat requires.
How the day changes
The single-unit day is reactive by design. You show up, the shift tells you what it needs, you make it happen. That is a good day. At twenty units, a reactive day is a failure. If you spent your day responding to whatever came in through the phone, you allowed the region to set your agenda. The regional seat runs a proactive day. You decide, on Monday, what the week is about. You spend the week doing that, and you handle the reactive load in narrow, contained windows.
My working structure at Hana looked like this. Monday and Tuesday were one-on-ones, back-to-back. Wednesday was field. Thursday was reading, writing, thinking. Friday was catering and enterprise relationships. That is the shape of a week that compounds. When I deviated, when I let a fire on Wednesday consume Thursday's reading time, the following week I paid for it. The pattern-recognition work does not get done in fifteen-minute gaps. It needs a real reading day.
The point
Twenty units is not one unit repeated twenty times. It is a different job with a different set of tools, a different resolution of information, and a different definition of what "being on top of it" means. The operators who make the leap are the ones who let go of the tools that got them promoted and pick up the tools that will get their whole region moving in the same direction.
You will feel less useful for a while. That feeling is the sign that the transition is working. The regional seat is a coaching seat, not a labor seat, and coaching is quiet by design.