The Rescue Job

When to Fire the General Manager, and When Not To

The default answer is "not yet." Here is the sequence that tells you when the default is wrong.

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

The short version

The default answer during a turnaround is not yet. Firing early teaches the region to hide.
Separate system failure from person failure before you make a call. Four to one, it is the system.
Fix the system around the general manager first. Give it six weeks of running clean.
Three signals overrule the wait: safety, integrity, and behavior toward the team.
When the answer is honest, move fast. Slow walking a clear decision costs the whole region.

Every operator I know has fired a general manager they wish they had kept, and kept one they wish they had fired. The mistake goes in both directions, and the cost is symmetrical: a region that stops trusting the operator's judgment. What follows is the framework I use now, after 16 years of multi-unit work and enough of my own errors to have a strong point of view about which mistake is which.

The short version is that firing is a downstream decision. It sits at the end of a diagnostic sequence, not at the start. If you get to firing without walking the sequence, the odds are high that you are firing the wrong person for the wrong reason, and that whoever replaces them will fail the same way inside the same broken system.

Let me walk you through the frame, then the four quadrants that fall out of it, then the six-week window that is doing the actual decision work.

Two axes, four quadrants, one decision

Any underperforming general manager sits somewhere on two axes. First axis: is the system around them fixed or broken. Second axis: is the person capable of running the fixed version of the system. Four quadrants. Four different decisions. Most operators skip the axes and jump straight to the decision, which is why the decision is so often wrong.

Fig. 1 · Four quadrants. Only one of them is a firing call.

Most operators live too much of their time in quadrants one and three, treating them as if they were quadrant four. That is where the wrong fires happen. The reverse mistake, staying in quadrant four for six months hoping the person will come back, is also common and just as expensive.

What system failure actually looks like

Before you can locate the general manager on the axis, you have to know what a broken system looks like from the inside. It is remarkably consistent across the underperforming multi-unit groups I have walked into.

Responsibility without decision rights. The general manager owns the P&L on paper. They cannot approve a $200 vendor swap without a phone call. They cannot comp a $40 ticket without an email. They cannot flex a schedule without corporate sign off. They are being asked to hit numbers they have no operational levers to move.
No dashboard they actually open. A weekly PDF from finance three days late, and a quarterly rollup no one reads. The general manager knows how last night went by looking at the tips their servers took home, not by looking at labor as a percent of sales.
No cadence. No standing weekly meeting with the area director. No monthly regional operating review. No place where the numbers get looked at with them, in the same room, on a predictable clock.
Tools that do not work. The POS is old, the scheduling system has three logins nobody remembers, and the inventory app was rolled out in 2022 and no one has done training since.
Peer isolation. The general manager has never met the general managers of the other units in the group. They are the only person in their building who has their job. They do not have anyone to compare notes with.

Any three of those together is a system failure. Two of them is a coaching problem. Five of them and you are looking at an underperforming general manager who has been positioned to fail, and the correct move is not to fire them. The correct move is to fix the system and give them six weeks in the fixed version.

The six-week window that does the decision work

Once the system is fixed, you wait. This is the piece that most operators skip because it feels like inaction and inaction feels dangerous. It is not inaction. It is measurement.

Six weeks is the window. Not four. Not eight. Six weeks is long enough for a capable person to demonstrate they can hold new decision rights, use a new dashboard, and run inside a new cadence. It is short enough that if the person cannot do those things, you have not wasted a quarter on a wait that had a knowable answer at week two.

The first time I ran this play, I gave a general manager three weeks and moved. He was starting to open up in week four. I fired someone who was about to work. That mistake bought me the six-week rule.

Inside those six weeks, you are watching for three signals. All three of them matter more than any single number on the P&L.

Are they hiding or opening up

A capable general manager in a fixed system starts telling you things they did not tell you before. Small things at first. A guest complaint they mishandled. A schedule they built wrong. A cook they should have coached out sooner. That flow of small confessions is the single strongest signal that the person can grow into the seat, because they only start opening up when they trust that opening up will not get them fired.

If instead the general manager becomes quieter through week three, if the answers get shorter, if they stop asking for help, that is the opposite signal. They are already gone in their head. The numbers may not have moved yet, but the person has decided.

Are the shifts calmer

Walk the unit at Friday dinner in week four. Compare it to week one. A general manager growing into a fixed system runs calmer shifts because they are making decisions earlier in the day and delegating them properly. A general manager who cannot grow into the seat runs the same chaotic shift as before, or a worse one, because they are being asked to make more decisions than they used to and they cannot.

Are the numbers moving in the right direction

Not moving to target. Moving. Labor variance narrowing by half a point. Food cost dropping by three quarters of a point. Comps and voids getting logged in real time instead of at end of week. You are not looking for the finish line at six weeks. You are looking for direction. Direction is enough to justify another six weeks. Absence of direction, with all three of the above going in the wrong way, is the call.

The three signals that overrule the wait

Three things do not get a six-week window. They get a same-day meeting.

Safety violations. Not one honest mistake. Repeated safety failures, or one that put staff or guests at real risk. This is not a turnaround decision. It is a protection decision, and it runs on a different clock.
Integrity failures. Theft, falsified inventory, altered timecards, kickbacks from vendors, comped meals for family that never got logged. If the general manager is stealing from the P&L or the guests, no amount of system fixing changes the answer.
Behavior toward the team. Hostility, discrimination, retaliation against staff who report problems, predatory behavior of any kind. The team has to see that these things get answered fast, or they will stop reporting them, and you will lose the region.

Outside of those three, the six-week rule holds. Inside of those three, the six-week rule does not exist.

What I got wrong the first two times

I have made both mistakes, and I have made them at scale. In one of my early regional roles I fired a general manager in month two who I later realized had been operating without any of the decision rights the job required. He went on to run a competitor's location four blocks away and outperform us. He was not the wrong person. I was the wrong operator, because I had not built the system he needed and I let my frustration override my sequence.

The reverse mistake was worse. In a Bay Area group I was fractionally leading through a $4.9M turnaround across three underperforming locations, I kept a general manager in quadrant four for four months after I knew the answer. I told myself I was being humane. What I was actually doing was avoiding a hard meeting. The team knew. The other general managers knew. My credibility with the region dropped one point every week I did not act. When I finally moved, three of my strongest shift leads had already found other jobs because they had stopped believing I would make hard calls. That cost more than the turnaround itself.

Slow walking a decision after the answer is clear does more damage than making the decision fast and doing it with respect. The team is not judging you on the outcome. They are judging you on your timing.

What the actual firing meeting looks like

If you reach quadrant four with a clear read, the meeting itself is short and simple. In person, on a Monday morning, before service. Not at end of day, not on a Friday, never over the phone unless there is no alternative. You bring HR if the company has HR. You have the paperwork ready. You have severance ready where warranted. You have a decision for the location that starts that same day, whether that is an interim general manager pulled from another unit or a shift lead you have quietly been developing.

You say the decision, you say the reason in one sentence, and you stop talking. You do not defend the decision, you do not walk them through the last six weeks, you do not litigate the past. That is what the previous conversations were for. This conversation is about respect and speed. The person on the other side of the table already knows.

Then you walk the floor. You do not send an email. You tell each shift lead, each key cook, each senior server, in person, that the general manager is no longer with the company, that you are grateful for the person's contribution, and that here is who is running the unit until further notice. The team will judge the way you did it more than the fact that you did it.

The point

Firing a general manager is a downstream decision. If it feels like the first move, it is the wrong move. Fix the system around them. Give it six weeks of clean running. Watch the three signals. Move only when the answer is honest. Overrule the wait only for safety, integrity, or behavior toward the team.

Do that and you will fire less often, keep more of your capable people, and build a region that trusts your judgment. Skip it and you will spend your career hiring the same general manager into the same broken system, wondering why every one of them fails.

Every hasty firing sends two messages you did not intend to send. To the region, it teaches that problems are the person, not the process, which trains everyone left to hide problems. To the person you replaced, it closes a door that might have opened for you again in three years when they became the operator they were on their way to being. Both costs are quiet, both compound.

The default answer is not yet. Learn to hear when the default is wrong.

Wrestling with a general manager call?

I take on a small number of multi-unit turnaround engagements each year, mostly restaurant and hospitality groups in the $10M to $60M revenue range. If you are staring at a general manager decision and want a second read on the sequence, I am happy to trade notes.

Get in touch

Questions people ask

When should you fire a general manager during a turnaround?

Almost never in the first 90 days. The default answer is not yet. Firing early teaches the rest of the region to hide problems, and hidden problems are the ones you cannot fix. The exceptions are safety violations, integrity failures like theft or falsified records, and behavior that puts the team at risk. Outside those exceptions, fix the system around the general manager first, then read the signal at six weeks.

How do you tell a system failure from a person failure?

A system failure looks like decisions that never got made, tools that were never installed, and cadence that never got built. A person failure looks like the same mistake being repeated inside a working system after coaching. Most underperforming general managers are inside a broken system. Very few are actually the wrong person. The ratio in my experience is roughly four to one system, one to one person.

How long should you wait before deciding a GM cannot grow into the seat?

Six weeks of running inside a fixed system. That means real decision rights, a working dashboard, and a standing operating rhythm. If after six weeks the numbers are not moving, the general manager is still hiding rather than opening up, and the shifts have not gotten calmer, you have the answer. Any less time and you are firing on the old system's data, not the new one.

What signals mean you have to move now, not later?

Three signals overrule the wait. Safety violations that put staff or guests at risk. Integrity failures such as theft, falsified inventory, or manipulated timecards. Behavior toward the team that is hostile, discriminatory, or predatory. These are not turnaround decisions. They are protection decisions and they run on their own clock.

How do you fire a general manager without breaking the rest of the team?

Do it in person, on a Monday, with severance where warranted, and with a plan for the location that starts the same day. The team will judge you on how you treat the person you are letting go, not on whether the decision was correct. Slow walking a decision after it is clear does more damage to the team than making it fast and doing it with respect.

What are the most common mistakes when replacing a general manager?

Three common mistakes. Firing before the system is fixed, which teaches the region to hide. Waiting too long after the answer is clear, which erodes trust in leadership. Replacing with an outside hire when there is a strong internal candidate you have not seen because you never built the bench. Each of these is fixable, but each of them costs a full quarter to recover from.

Should the area director or the operator make the firing decision?

The area director recommends. The regional or the operator decides. The general manager works for the area director day to day, but a termination decision touches the whole region and needs to be made by whoever owns the region's numbers. Splitting recommendation from decision keeps the day to day relationship honest and puts the accountability where it belongs.