Run The Region

The Regional Versus Corporate Tension and How to Sit In It

The regional director is the diaphragm between corporate policy and field reality. Sitting in the middle is not a career weakness. It is the job. Here is how to translate both directions without losing either side, and the times I picked the wrong side.

Kiyong (Eric) Lee·Operations Executive·August 2026·9 min read

The short version

Corporate sees brand economics, capital constraints, and competitive dynamics. The field sees the store, the cook, and the guest. Both views are partial.
The regional director's job is to translate both directions with the same rigor. Not to pick a side. Sitting in the middle IS the seat.
Push back on corporate when a specific failure mechanism is visible from your seat and invisible from theirs. Bring the mechanism, not the frustration.
Defend corporate to the field when the field is asking for a shortcut that costs the brand more than it saves the unit.
The two times I picked the wrong side: once I fought a pricing change I should have implemented, and once I implemented a labor policy I should have escalated.

The first year I sat in a regional seat I thought my job was to represent the field. Field problems came up to me, I carried them to corporate, corporate said yes or no, I carried the answer back. Straightforward. Also wrong.

What I learned by the end of that year was that the regional seat is not a courier seat. It is a translation seat, and the translation goes both ways. Corporate needs to understand what the field is actually seeing, not just what the field is asking for. The field needs to understand what corporate is actually optimizing, not just what corporate is telling them to do. And nobody else in the org chart is positioned to do that translation. The store manager cannot see the aggregate. The corporate director cannot see the store. The regional director is the one seat that sits close enough to both to be a real interpreter.

That interpretation job is uncomfortable by design. If you are doing it well, you will spend a portion of every week defending decisions to people who trusted you to fight them, and pushing back on decisions from people who expected you to salute. If that discomfort is missing, you have quietly picked a side, and the org is no longer being served by the seat.

What corporate can see that the field cannot

Start here because most operators who moved from a GM seat to a regional seat sympathize more naturally with the field. I did. The counterweight has to come from consciously naming what corporate is actually looking at.

Brand economics across the whole system

Corporate sees the cost curve of running 100 units, not the cost curve of running one. A menu change that saves 30 seconds per ticket sounds trivial at a single unit. Across 100 units doing 400 tickets a day, that is 12,000 minutes a day of labor recovery, which is roughly 200 hours a day, which is roughly 15 full-time labor equivalents in aggregate. The field sees the 30 seconds. Corporate sees the 15 FTEs. Both numbers are true. Only one is visible from the store floor.

Capital constraints and where the next dollar goes

The field sees the broken piece of equipment at their unit. Corporate sees the twelve broken pieces of equipment across twelve units and the capital budget that can fund four of them this year. When a GM says "I need $40K to fix my hood," they are correct on the specifics. When corporate says "not this quarter," they are correct on the aggregate. The regional director's job is to hold both, not to translate one as a rejection of the other.

Competitive dynamics and category positioning

Field operators see their guests. Corporate sees the market. When corporate holds a price point steady while the field is losing individual comps to a competitor, corporate is often looking at what happens to the brand if the price point moves. The field sees a lost check. Corporate sees a re-priced category. The regional operator translates both.

Fig. 1 · The regional seat is where the two views become one picture.

What the field can see that corporate cannot

Now flip it. The reason a corporate directive can look reasonable on a slide and fail at the store is that the slide is drawn without the physics of the store on it.

The physical reality of running a shift

Corporate rolls out a new prep procedure. The procedure is sound in the test kitchen. At the store, the prep sink is six feet from the walk-in and the new procedure needs three trips per batch instead of one. Now the prep cook is spending 25 percent more time walking, which cascades into a late lunch prep, which cascades into a slower service, which cascades into a labor variance nobody can explain from a corporate deck. The field sees the physical reality. Corporate cannot.

Morale, and what a policy change costs the person doing the work

An eight-year cook watches the recipe change for the third time in a year. Corporate sees a menu optimization. The cook sees a message about whether their institutional knowledge matters. That message shows up two months later in a resignation, and the resignation shows up six months later in a food cost the corporate team cannot account for, because the new cook does not know how the fryer that reads 350 actually runs at 375. The morale cost is invisible on a slide. It is visible on the line, if you are on the line.

Guest sentiment before it hits the survey

The guest survey is a lagging indicator. A shift lead at the door notices the tone shift in a regular guest three weeks before it shows up in a score. The GM notices the same shift a week later. Corporate notices it in the next monthly report, at which point the guest has already decided. The field sees the sentiment inflection in real time. Corporate sees the score.

Neither side is wrong. Both are looking at the same business through different windows. The regional director is the one seat that can see both windows at once, which is exactly why the seat exists.

When to push back on corporate

The push back has to be earned, and the currency to spend on it is finite. Push back when three conditions are met:

You can name the specific failure mechanism. Not "the field will hate it." That is not a mechanism. "The new procedure adds a third trip to the walk-in and pushes lunch prep late by 20 minutes, which cascades into a labor variance of roughly 1.2 points across the region on Saturdays" is a mechanism. Corporate can act on that. They cannot act on frustration.
The failure is visible from your seat and invisible from theirs. If the corporate team has already looked at the mechanism you are raising, you are not adding information, you are adding volume. Only push back with signal that only the regional seat can generate.
You have thought through what you are asking for instead. A push back without an alternative is a complaint. A push back with a proposed modification, sequenced and scoped, is a partnership. Bring the modification.

When to defend corporate to the field

This is the harder half of the job because it will make you unpopular with the people you spend most of your time with. Defend corporate when:

The field is asking for a shortcut that costs the brand more than it saves the unit. A GM asking to drop a brand standard is not lying about how it slows their service. They are just not accounting for the twenty other units where that standard is what keeps guests loyal. Your job is to defend the standard and to translate why in a way that respects the GM.
The complaint is really about change fatigue, not about the decision. Sometimes the field is exhausted from the pace of change and wants to reject the next thing because it is the next thing. That is a real problem, but the fix is not to reverse the decision. The fix is to slow down the next four decisions and to name that you heard the fatigue.
The push back is happening two levels down and has not been aired at the GM level. If a shift lead is complaining and their GM has not raised it, the escalation is wrong before the content is wrong. Route it back through the GM.

When to escalate

Escalation is a currency. Spend it carefully. Escalate when:

The issue is bigger than your region can absorb.
The same problem is showing up at multiple units, which means the root cause is systemic, not local.
The fix requires a change in policy, capital, or org structure that is not within your authority.

Do not escalate a single-unit issue that you have not already tried to solve locally. Do not escalate to punish corporate for a previous decision. Do not escalate because you want the political cover of having asked. Every escalation is a claim on the corporate team's calendar. Spend the claim carefully or you will not have it when it actually matters.

The times I picked the wrong side

Two specifically. Both taught me something I would not have learned any other way.

The pricing change I fought and should have implemented

Early in my time at a multi-unit group, corporate raised the price on a signature dish by roughly 12 percent. The field pushback was immediate and loud. Guests would notice. Comps would drop. I sided with the field and pushed hard to soften the increase.

Corporate held the line. Comps dropped for six weeks. Then they recovered, then exceeded prior levels because the price point was better aligned with the guest's perception of the dish's value. What I had missed was that corporate had done the elasticity modeling across the category. I had done my modeling across three loud GMs. I mistook local intensity for aggregate truth. I should have held the field's concerns without campaigning against the decision.

The labor policy I implemented and should have escalated

Later, at a different group, corporate rolled out a scheduling policy that in practice created a two-hour daily gap in dish coverage at units with certain shift patterns. I could see the mechanism. Corporate could not. Instead of escalating with the specific failure mode, I implemented the policy and asked GMs to work around it. Six weeks later a compliance review found the workarounds, and the GMs took the heat for a policy they had told me would not work.

I owed them the escalation. I did not spend the currency because I did not want to look like the difficult regional director. That is the wrong reason to withhold an escalation. The field paid the cost of my caution, and I lost trust with three GMs I did not fully rebuild for a year.

The two failures were opposite in shape and identical in cause. Both times I picked the side I thought would be easier, and easier is not a real criterion for the regional seat.

How to sit in the middle without breaking

The regional seat is emotionally demanding because you are being asked to hold two loyalties that pull in opposite directions. A few practices that helped me.

Never sandbag either direction

If you are carrying a corporate decision to the field, deliver it fully. Do not add your own eye-roll. Do not signal to the GMs that you personally disagree. If you disagreed, you should have said so upstream. Once the decision is made, you deliver it clean or you deliver it back for another round. The version where you deliver it and privately trash it in the parking lot is the version that breaks trust in both directions.

Always bring signal upward, never volume

When you push back on corporate, bring the mechanism, the numbers, and the proposed alternative. Never bring "the GMs are unhappy." Unhappy GMs are not a problem statement. They are a symptom you are supposed to diagnose before you send it up.

Keep a written record of both sides

I kept a simple two-column document. Left: corporate decisions I was carrying to the field this quarter. Right: field signals I was carrying to corporate this quarter. Reviewed monthly. When one column consistently outweighed the other, I knew which direction I was drifting and spent more time on the other side. The written record kept me honest.

Book the sit-down with leadership every quarter

Regularly, and on the calendar, sit with your executive leadership for 90 minutes just to talk. Not a review. Not a report. A conversation. That is the venue where you carry the field signal that does not fit in a monthly deck, and where they carry the brand signal that does not fit in an email. If you do not book it, it does not happen, and both sides lose the translation.

The point

Sitting between corporate and the field is not a weakness of the regional seat. It is the job. If you always represent the field, you are a shop steward. If you always defend corporate, you are a messenger. The seat exists because both partial views need a translator, and translation is uncomfortable by design.

Do the translation with the same rigor in both directions. Bring the mechanism, not the frustration, when you push up. Deliver the decision cleanly, not passively, when you carry down. Spend escalation currency carefully. And when you pick the wrong side, name it fast, because the seat only works if both directions can trust the signal you send.

The middle is not a compromise. It is a viewpoint. Own it.

Working the corporate-field seam right now?

I work with regional operators navigating friction between corporate policy and field reality, and with corporate teams trying to hear the signal their regional layer is sending. If you are trying to figure out where you actually sit, I am happy to compare notes.

Get in touch

Questions people ask

What is the regional versus corporate tension?

It is the structural gap between what corporate can see from the home office and what the field can see from the store floor. Corporate sees brand economics, capital constraints, competitive positioning, and the cost of running 100 units at once. The field sees the physical reality of a store, the cook who has been there eight years, the guest who noticed the recipe changed. Both sides are looking at the same business through different windows. The regional director is the person who can see both windows at once, which is why the seat exists.

When should a regional director push back on a corporate directive?

When the directive will break something in the field that corporate cannot see. Not because the directive is inconvenient, and not because the GMs are complaining. Push back when the specific mechanism by which the policy will fail is visible to you from your seat and invisible from corporate's. Bring the mechanism, not the frustration. A specific failure mode with a specific cost is a real escalation. A general complaint is not.

When should a regional director defend a corporate decision to the field?

When the field is asking for a shortcut that would cost the brand more than it would save the unit. Field pushback is often correct on the specific unit and wrong on the aggregate. A GM asking to skip a brand standard because it slows service is not lying about the slowdown. They are just not accounting for the twenty other units where the same standard is what keeps guests coming back. Your job at that moment is to defend the decision and to translate why, in language that respects the GM.

How do you know when to escalate an issue to corporate?

Escalate when the issue is bigger than your region can absorb, when the same problem is showing up at multiple units, or when the fix requires a change in policy, capital, or org structure that you do not have authority over. Do not escalate a single-unit problem or a problem you have not tried to solve locally first. Every escalation you make is an ask on the corporate team's calendar. Spend the currency carefully or you will not be able to spend it when it matters.

What does corporate not see about the field?

The physical reality of a store on a rough Saturday. The morale of a cook who has watched three policy changes in a quarter. The specific way a guest's tone shifted when the recipe changed. The equipment that has been failing for six weeks that finally broke on the worst possible night. Corporate sees aggregates. The field lives in specifics. The regional director translates the specifics into the aggregate signal corporate needs, without losing what made the specific meaningful in the first place.

What does the field not see about corporate?

Brand economics, capital constraints, competitive dynamics, and the cost of running the whole system. The field sees their unit. Corporate sees the deck the CFO showed the board and the number the CEO promised the shareholders. Neither view is wrong. Both are partial. The GM who wants a $40K equipment upgrade at their unit is not accounting for the twelve other GMs asking for the same upgrade. The regional director's job is to hold that broader picture without belittling the specific one.

Is sitting in the middle of corporate and field a leadership weakness?

No. It is the job. If a regional director always sides with corporate, they are a corporate messenger with a field title, and the field learns to route around them. If they always side with the field, they are a shop steward with a corporate paycheck, and corporate stops trusting the signal they send up. Sitting in the middle without flinching, translating both directions with the same rigor, is what the seat is for. Anyone who tells you otherwise has not held the seat.